On Thu, 2013-05-23 at 13:13 +0200, Arno Töll wrote: > we are ready to upload Apache2 2.4 to Debian Sid now. This means the > transition is effectively starting now, and going to break your modules.
I have been working on getting mod_python into shape (somewhat). I have cleaned up the packaging (switch to dh_python2, dh sequencer, quilt 3.0 source format, etc. I also tried to clean up a little (removing code for upgrades from ancient versions, etc.). As a last step I've upgraded to the code to build using Apache 2.4 and switch the maintainer scripts to use apache2-maintscript-helper (actually using dh_apache2 resulted in the removal of all maintainer scripts). In the patch (20_apach24.patch) I only made the absolute minimal number of changes to allow mod_python to be buildable and loadable by Apache (breaking some functionality in the process, see the patch). This is far from a nice solution. I only did minimal testing (that the module loads). I've uploaded the updated package to experimental. I don't know yet if I'm 100% comfortable with uploading this to unstable. If someone can do more thorough testing, that would be very welcome. I don't think I can upload the package to unstable in a specific time slot. Packages is in DPMT repository: Vcs-Svn: svn://anonscm.debian.org/python-modules/packages/libapache2-mod-python/trunk/ Vcs-Browser: http://anonscm.debian.org/viewvc/python-modules/packages/libapache2-mod-python/trunk/ In any case, if no-one steps up, removing mod_python from testing to get Apache 2.4 in is probably the best option. The number of users of mod_python should be limited (everyone should be using mod_wsgi). -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
