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

Bug#392380: marked as done (apache2-common: Upgrad issues with libapache2-mod-php4 installed)

Your message dated Tue, 6 May 2008 00:18:18 +0200
with message-id <200805060018.19230.sf@sfritsch.de>
and subject line #392380 apache2-common: Upgrad issues with libapache2-mod-php4 installed
has caused the Debian Bug report #392380,
regarding apache2-common: Upgrad issues with libapache2-mod-php4 installed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
392380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392380
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: apache2-common
Version: 2.0.55-4.2
Severity: important

Upgrading to apache2.2 in unstable brought my system into a stuck state.
apache2-common prerm failed with:
Entferne apache2-common ...
 * Stopping apache 2.0 web server... Syntax error on line 1 of /etc/apache2/mods-enabled/php4.load:
API module structure `php4_module' in file /usr/lib/apache2/modules/libphp4.so is garbled - perhaps this is not an Apache module DSO?
                                                                         [fail]
invoke-rc.d: initscript apache2, action "stop" failed.
dpkg: Fehler beim Bearbeiten von apache2-common (--remove):

Apache was not running at this point anymore; however the prerm would still
fail at trying to stop (non-running) apache.

Shortcutting the apache2-common.prerm with an "exit 0" made the upgrade
work again. Maybe the prerm script could be modified to not fail if apache
wasn't running in first place, desipte the ABI issues.

--- End Message ---
--- Begin Message --- 
Version: 2.2.3-3

This was fixed in 2.2.3-3

--- End Message ---
Reply to: