Will the next release support Debian Wheezy? -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F
Do you mean Jessy? Philippe Blouin, Responsable du développement informatique Tél. : (888) 604-2627 philippe.blouin@inLibro.com <mailto:philippe.blouin@inLibro.com> inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com> On 03/08/2016 01:13 PM, Tomas Cohen Arazi wrote:
Will the next release support Debian Wheezy?
-- Tomás Cohen Arazi Theke Solutions (http://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
Hi, On Tue, Mar 8, 2016 at 1:13 PM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
Will the next release support Debian Wheezy?
We'll have to see based on what the net new dependencies end up being. Wheezy is set to be in LTS from 26th of April 2016 to 31st of May 2018, so there would be some value in not forcing a mandatory major Debian upgrade on users in order to use Koha 3.24, but I don't think that need be a firm commitment on our parts. At present, of course, you'll need Jessie to get Apache 2.4 and Plack support; Jessie thus remains the minimum _recommended_ Debian version. [1] https://wiki.debian.org/LTS/ Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
2016-03-08 18:00 GMT-03:00 Galen Charlton <gmc@esilibrary.com>:
Hi,
On Tue, Mar 8, 2016 at 1:13 PM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
Will the next release support Debian Wheezy?
Answer for Philipe: I meant to say "drop support for Debian Wheezy". Sorry for the confusion.
We'll have to see based on what the net new dependencies end up being. Wheezy is set to be in LTS from 26th of April 2016 to 31st of May 2018, so there would be some value in not forcing a mandatory major Debian upgrade on users in order to use Koha 3.24, but I don't think that need be a firm commitment on our parts.
I asked mainly because I was not sure about the status of Wheezy (being an LTS release or not) and...
At present, of course, you'll need Jessie to get Apache 2.4 and Plack support; Jessie thus remains the minimum _recommended_ Debian version.
exactly that. I'm working on a couple scripts that deal with apache configuration files, and the use of Define directives (core feature in 2.4) would make things really easier (thinking on the upgrade path). As Galen said, we already need apache 2.4 for Plack. The Plack configuration is actually wrapped like this: <IfVersion >= 2.4.8> ... ProxyPass /cgi-bin/koha "unix:/var/run/koha/${instance}/plack.sock| http://localhost/intranet" The important part is the ${instance} variable, defined in the top-level virtualhost definition file like this: Define instance "__KOHASITE__" If we could make use of this directive, we could patch the end-user's apache configuration files on upgrade. It is clearer with an example: If we introduced a sitemap generation wrapper script around sitemap.pl to make it work the-packages-way (what I worked on this morning), it would be great to just patch the apache-shared-opac.conf file, including either the configuration for the sitemap files, or an include for an extra file that deals with it. As we need generate sitemaps for each instance, we need a way to point it to the instance-specific sitemap directory. It would use a placeholder for the instance name so it works for already created instances. Right now, we need to let the users know how to patch their files. That's the main reason I asked. I can do it the same way we did for Plack, wrapping the include inside the <IfVersion >= 2.4.8> condition anyway. Just asking. Regards Tomas
[1] Thanks, Galen -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F
Hi, On Tue, Mar 8, 2016 at 4:55 PM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
If we introduced a sitemap generation wrapper script around sitemap.pl to make it work the-packages-way (what I worked on this morning), it would be great to just patch the apache-shared-opac.conf file, including either the configuration for the sitemap files, or an include for an extra file that deals with it. As we need generate sitemaps for each instance, we need a way to point it to the instance-specific sitemap directory. It would use a placeholder for the instance name so it works for already created instances. Right now, we need to let the users know how to patch their files.
That's the main reason I asked. I can do it the same way we did for Plack, wrapping the include inside the <IfVersion >= 2.4.8> condition anyway. Just asking.
Thanks for the example. I'm not necessarily attached to the notion of maintaining Wheezy support to the very end of its LTS period, but I don't think that this specific case is worth abruptly de-supporting Wheezy (although yes, Define sure will be handy). Consequently, unless some other new dependency forces the issue, I suggest that we consider doing the following: - announce a deprecation of Wheezy support (or perhaps more precisely, support for Apache < 2.4) with the release of 3.24 - officially de-support Wheezy in new releases starting with 3.26 In the long run, I'm willing to carve out a new repository slot to keep 3.24 going for Wheezy for as long as there is an RMaint willing to at least handle security patches. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
Galen, I missed this email on my inbox. I agree with your proposal, and also with not abruptly ending support for Wheezy. The patches I wrote for integrating the sitemap feature on the packages (bug 16016) were written with the IfVersion wrapper already. 2016-03-08 19:25 GMT-03:00 Galen Charlton <gmc@esilibrary.com>:
Hi,
On Tue, Mar 8, 2016 at 4:55 PM, Tomas Cohen Arazi <tomascohen@gmail.com> wrote:
If we introduced a sitemap generation wrapper script around sitemap.pl to make it work the-packages-way (what I worked on this morning), it would be great to just patch the apache-shared-opac.conf file, including either the configuration for the sitemap files, or an include for an extra file that deals with it. As we need generate sitemaps for each instance, we need a way to point it to the instance-specific sitemap directory. It would use a placeholder for the instance name so it works for already created instances. Right now, we need to let the users know how to patch their files.
That's the main reason I asked. I can do it the same way we did for Plack, wrapping the include inside the <IfVersion >= 2.4.8> condition anyway. Just asking.
Thanks for the example. I'm not necessarily attached to the notion of maintaining Wheezy support to the very end of its LTS period, but I don't think that this specific case is worth abruptly de-supporting Wheezy (although yes, Define sure will be handy).
Consequently, unless some other new dependency forces the issue, I suggest that we consider doing the following:
- announce a deprecation of Wheezy support (or perhaps more precisely, support for Apache < 2.4) with the release of 3.24 - officially de-support Wheezy in new releases starting with 3.26
In the long run, I'm willing to carve out a new repository slot to keep 3.24 going for Wheezy for as long as there is an RMaint willing to at least handle security patches.
Regards,
Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
-- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F
participants (3)
-
Galen Charlton -
Philippe Blouin -
Tomas Cohen Arazi