On Sun, Nov 16, 2003 at 11:32:30PM +0100, Fabio Massimo Di Nitto wrote: > > > reassign 221133 apache-common > > Bug#221133: php4: unstable - Configuration hangs after restarting apache > > Bug reassigned from package `php4' to `apache-common'. > before reassigning do you mind to check if the bug is there for real and > what is causing it??? Just the fact that modules-config handles the > restart means nothing (remember the db_stop problem??). > Fetched 778kB in 0s (6899kB/s) > Preconfiguring packages ... > Selecting previously deselected package php4. > (Reading database ... 92332 files and directories currently installed.) > Unpacking php4 (from .../php4_4%3a4.3.3-3_i386.deb) ... > Setting up php4 (4.3.3-3) ... > Restarting apache. > gundam:~# > and no problems here. Since apache like all the other modules work just > fine and this problem is showing up only and constantly with php4 i start > to doubt that this is an apache fault. The last lines in the current php4 postinst are: for i in apache apache-ssl apache-perl; do if [ -d /etc/$i ]; then modules-config $i enable mod_php4 fi done exit 0 It is my understanding that this is the documented interface for enabling Apache modules at install time. If it is not, then I submit that the interface is insufficiently documented. If it is, then I submit that this interface is broken, because it's incompatible with packages which need to use debconf for their own purposes. Now, maybe this is actually a debconf bug -- that wouldn't really surprise me -- but that doesn't remove the need for an interface that's compatible with debconf-using packages. It appears that, at present, php4 is the only package in unstable that depends on both apache-common and debconf, which would explain why this bug only surfaces when installing php4. If you insist that this makes it a php4 bug and not a modules-config bug, I see no choice but to remove the modules-config call from the php4 postinst. I'd *like* to comply with the long-standing wishlist request for auto-enabling of php4 on install, but we *need* a package that can be installed reliably. Currently, modules-config is preventing that. As for whether this bug really exists, I can at least tell you that yes, php4 fails to install correctly when more than one apache flavor is installed, but works fine for me when only one apache flavor is installed. It also works if I comment out the use of debconf in the postinst. -- Steve Langasek postmodern programmer
Attachment:
pgpPGHDa36vWk.pgp
Description: PGP signature