Hi, just an ACK. I am aware of the transition and will make necessary steps to fix PHP 5.4 when apache 2.4 reaches unstable (php5_5.4.1~rc1 already includes upstream support for Apache 2.4).
Heads up on the upload to unstable would be nice, but not mandatory. O. On Sun, Apr 1, 2012 at 23:15, <[email protected]> wrote: > Package: php5 > Severity: important > User: [email protected] > Usertags: apache24transition > > Dear maintainer, > > your package php5 is provding an Apache2 web server module. > We're upgrading Apache to the new upstream version 2.4 [1] (tracked > as transition bug #661958). This requires all modules to be rebuilt > due to ABI changes. Thus, you need to rebuild and reupload your > Apache2 module package in a version compatible to our new package > available in experimental [2]. Please note it is not enough to > simply rebuild the module - it needs some adaptions in the module > package metadata. We have written packaging guidelines for our > reverse dependencies [3]. Please read it carefully, it should be able > to answer most of your questions. Do also look at dh_apache2 > (available through the dh-apache2 package) which can simplify > packaging Apache2 modules. In short, we want to highlight these > changes you need to be aware of. > > * APIs changed for some cases [3]. Chances are your module needs some > adaptions, please get in touch with upstream or us if you need help > to port your module to Apache 2.4. > > * MPM packages are gone. You cannot depend or conflict with a > particular MPM anymore. If your module does not work with a > particular module, make sure to make it abort with an error if > loaded together with an incompatible MPM. You can use our > apache2-maintscript-helper [4] to switch to the MPM of your choice > in your maintainer scripts. > > * Do not build-depend on apache2-threaded-dev or apache2-prefork-dev > anymore. Just like MPMs are gone, are our MPM -dev packages as > well. All modules need to simply build-depend on apache2-dev. > > * Do NOT depend on apache2, apache2-common or any other real apache2 > package in your binary module package. Depend on our virtual > apache2-api-20120211 package only! > > * Do NOT call a2enmod/a2dismod in your maintainer scripts. Use our > apache2-maintscript-helper [3] instead. This is required to get a > uniform and stateful handling of all Apache2 modules. > > > You can look at our Apache 2.4 packaging hints [5] for hands-on > tutorials. Please note: This bug is filed as "important" for now. As > the time goes by we plan make it a release critical severity. In the > consequences your module either needs an update or is going to be > removed from Wheezy. For the time being please tag the bug as pending > as soon as you have a package ready. We strongly recommend that at > least maintainers of complex module packages make an upload to > experimental as well. Of course, uploading simple modules to > experimental is welcome, too. > > [1] https://lists.debian.org/debian-devel-announce/2012/03/msg00013.html > [2] > http://packages.debian.org/search?keywords=apache2&searchon=sourcenames&exact=1&suite=all§ion=all > [3] > http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/PACKAGING;hb=next > [4] http://httpd.apache.org/docs/2.4/developer/new_api_2_4.html > [5] http://wiki.debian.org/Apache/PackagingFor24 > > > > > > _______________________________________________ > pkg-php-maint mailing list > [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-php-maint -- Ondřej Surý <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/CALjhHG9bbBb=n=bkghnpk0t1g2ggfwordfohs7msxh4xi0v...@mail.gmail.com
