Bug#609209: apache2.2-common: update to 2.2.9-10+lenny9 breaks libapache2-mod-php5
On Friday 07 January 2011, Matej Susta wrote:
> Yesterday, my automatic update script on one of my servers
> installed latest security update to apache, version
> 2.2.9-10+lenny9. This somehow caused automatic uninstallation of
> libapache2-mod-php5. At that moment I just downgraded to
> 2.2.9-10+lenny8 and manually installed back mod-php, because I
> couldn't allow any more downtime on that server. At least one
> other person on internet hit this too (
> http://sourceforge.net/projects/webadmin/forums/forum/600155/topic
> /4040746 ) on his server and states that even manual installation
> of mod-php to updated system won't work and apache is still
> broken.
It worked for me. But since the apache2 update contains a changed
config file and a NEWS entry, it seems likely that your automatic
update script does not handle one of these conditions correctly (which
are rather rare in security updates). Either it gets confused by apt-
listchanges displaying the NEWS entry (if you have apt-listchanges
installed) or dpkg tries to ask what to do with the changed config
file and then fails due your script.
Without the full output of apt-get or aptitude, it is impossible to
tell what the problem is.
Reply to: