Your message dated Sun, 10 Apr 2011 23:36:21 +0200
with message-id <[email protected]>
and subject line Bug#367393: libapache{,2}-mod-php5: gratuitous conflicts with
libapache{,2}-mod-php4 ?
has caused the Debian Bug report #367393,
regarding why does libapache2-mod-php5 conflict with libapache2-mod-php4
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 [email protected]
immediately.)
--
367393: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=367393
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libapache2-mod-php5
Severity: minor
Hi,
libapache2-mod-php4 conflicts with libapache2-mod-php5. I don't see
any compelling reason for this conflicts. Both packages don't share
common file names, and the problem that might arise if both php
modules are loaded at once can be fixed with trivial scripting in the
postinst of php4 and php5: Just don't enable the own module if the
other one is already enabled.
The changelog entry:
* Bring back some concflicts that went missing (libapache-mod-php5 needs
to conflict with libapache-mod-php4 and older versions of php4, while
the two libapache2-mod-php[45] modules also need to conflict).
doesn't answer the question why the conflict is actually needed.
I'm willing to deliver patches to php4 and php5 which implement the
checks outlines above.
Greetings
Marc
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.6-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
--- End Message ---
--- Begin Message ---
php4 is not part of any debian release. Closing the bug as obsolete.
O.
--
Ondřej Surý <[email protected]>
--- End Message ---
