Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 61782 - Upgrade to PHP 5 fails to completely uninstall PHP4 (apache/conf/modules.d/70_mod_php4.conf remains)
Summary: Upgrade to PHP 5 fails to completely uninstall PHP4 (apache/conf/modules.d/70...
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: PHP Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-26 03:33 UTC by Benjamin Richter
Modified: 2004-08-26 03:54 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Richter 2004-08-26 03:33:44 UTC
When upgrading to PHP 5 (e.g. by using emerge -u world) the old modules.d/70_mod_php.conf file remains in /etc/apache/conf/modules.d/ directory generating Apache error when trying to start Apache(2).

Furthermore notice should be displayed after mod_php5 install pointing out that conf.d/apache define "-D PHP4" is replaced (or enhanced) by "-D PHP5"

Reproducible: Always
Steps to Reproduce:
1. emerge mod_php 4.x
2. emerge -u mod_php to version 5.x
3. try to start apache


Actual Results:  
Apache complains about non-existent module libphp4.so.

Expected Results:  
Start Apache webserver.
Comment 1 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-08-26 03:41:31 UTC
We had the message for Apache2, but not for apache1, i've added it now.
/etc/apache/conf/modules.d/70_mod_php.conf remains because of config-protect.

could you elaborate on what errors you are getting when -D PHP4 is NOT in your conf.d/apache  ?
Comment 2 Benjamin Richter 2004-08-26 03:48:29 UTC
If "-D PHP4" is NOT in conf.d/apache everything runs fine.

PHP 5 runs fine when "-D PHP5" is set in conf.d/apache, as expected.
Comment 3 Robin Johnson archtester Gentoo Infrastructure gentoo-dev Security 2004-08-26 03:51:34 UTC
then it's user error caused by config-protect NOT removing the old 70_mod_php config, as it may have user customizations in it.
Comment 4 Benjamin Richter 2004-08-26 03:54:22 UTC
Right. At least showing a message with Apache 1.x was something worth mentioning.