On Sat, 21 Apr 2012 12:07:58 +0000 a...@debian.org wrote:%0A> Package: gitweb%0A> Severity: important%0A> User: debian-apa...@lists.debian.org%0A> Usertags: apache24webapptransition%0A> %0A> Dear maintainer,%0A> %0A> your package gitweb is a web application which supports the Apache2%0A> web server. We're upgrading Apache to the new upstream version 2.4 [1]%0A> (tracked as transition bug #661958). This requires some changes in your%0A> package about how to interface to our package. You can test your package%0A> against our package available in experimental [2] which is soon to be%0A> uploaded to Sid. Please note, chances are that for the time being, third%0A> party modules (e.g. mod_php, mod_perl and such) are not yet available in%0A> a version capable to run with the Apache 2.4 web server. You can use%0A> their (Fast-)CGI counter parts, e.g. php5-fpm to test your packages. You%0A> can see an up to date state of modules being in the transition to%0A> Apache2 2.4 at [3]. We have written packaging guidelines for our reverse%0A> dependencies [4]. Please read this document carefully, it should be able%0A> to answer most of your questions. Do also look at dh_apache2 (available%0A> through the dh-apache2 package) which can simplify shipping of Apache2%0A> configuration files. %0A> %0A> In short, we want to highlight these changes you need to be aware of:%0A> %0A> * Do NOT declare a strong relation against apache2.2-common (or%0A> apache2-common as its natural successor). Instead recommend "apache2 |%0A> httpd" in your package relationships. %0A> %0A> * Do NOT install any files to /etc/apache2/conf.d/. This directory is%0A> obsolete. Its successor is /etc/apache2/conf-available/ which can be%0A> interfaced through a2enconf/a2disconf%0A> %0A> * Do NOT call a2enconf/a2disconf in your maintainer scripts. Use our%0A> apache2-maintscript-helper [4] instead. This is required to get a%0A> uniform and stateful handling of all web applications interfacing with%0A> Apache2.%0A> %0A> * Please use the new authentication and authorization directives of%0A> Apache 2.4 [6]. While the old style directives are in principle still%0A> supported using mod_access_compat, mixing old and new style directives%0A> can cause problems. Moreover, the compatibility mode may be removed in%0A> a future release.%0A> %0A> %0A> You can look at our Apache 2.4 packaging hints [7] for hands-on%0A> tutorials.%0A> %0A> %0A> %0A> [1] https://lists.debian.org/debian-devel-announce/2012/03/msg00013.html%0A> [2] http://packages.debian.org/search?keywords=apache2&searchon=sourcenames&exact=1&suite=all§ion=all%0A> [3] http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=apache24transition;users=debian-apa...@lists.debian.org%0A> [4] http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next%0A> [5] http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html%0A> [6] http://httpd.apache.org/docs/2.4/upgrading.html#run-time%0A> [7] http://wiki.debian.org/Apache/PackagingFor24%0A> %0A> %0A> %0A
