[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#416231: apache2: fails to start after upgrade from Sarge



reassign 416231 libapache2-mod-perl2
thanks

[Frans Pop]
> > Can you send the error.log from apache?
> 
> Attached. I've also attached a new version of the upgrade log as I
> noticed I missed a few probably relevant lines at the end.

[First of all, the cosmetic issue ("You may still have some apache2
processes running") is something we can't really fix, because it is
printed by the sarge init script (invoked from the sarge prerm, the
sarge postrm and the etch preinst).  I could try to make the etch init
script more robust against throwing that error unnecessarily, but it
_is_ mostly cosmetic and we _are_ near the etch release.]

The real bug here is that, at the time apache2.2-common is configured,
libapache2-mod-perl2 has not yet been configured.  As a result, the
conffile /etc/apache2/mods-available/perl.conf has has not yet been
upgraded, and the old version of the conffile does not allow the new
version of apache2 to start.

As discussed with Steve L on IRC, the best solution is probably for
libapache2-mod-perl2 to _stop_ shipping the (now empty) conffile
/etc/apache2/mods-available/perl.conf, and edit out the offending line
in its prerm, in case the user has a modified copy (or, if not, just
removing the file and its symlink in mods-enabled).

Peter

Attachment: signature.asc
Description: Digital signature


Reply to: