Bug 175146 - php.ini for i386 RPM has bad extension_dir
php.ini for i386 RPM has bad extension_dir
Product: Fedora
Classification: Fedora
Component: php (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Joe Orton
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2005-12-06 18:00 EST by Paul W. Frields
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-12-06 18:03:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul W. Frields 2005-12-06 18:00:00 EST
Description of problem:
The /etc/php.ini file for php-5.0.4-10.5.i386

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Upgrade to php-5.0.4-10.5
2. Test web app relying on, e.g., php-mysql and /usr/lib/php/modules/mysql.so

Actual results:
Breakage, debugging indicates dl() looks for /usr/lib64/php4; /etc/php.ini
contains the answer.

Expected results:
Happiness as always.

Additional info:
I'm not a Web server or PHP expert, just a user.  If this entry is ignorant,
please hit reporter with cluestick.
Comment 1 Joe Orton 2005-12-06 18:03:40 EST
Not as shipped otherwise this would work for nobody.  

Run "rpm -V php" to see whether /etc/php.ini is modified from the shipped copy.

Do you have an /etc/php.ini.rpmnew?  If so rename it over /etc/php.ini.

I'd suggest a "yum erase php" then a re-install of everything removed.

Comment 2 Paul W. Frields 2005-12-06 18:06:19 EST
You're right, of course 2 min. after I filed the bug I found the same problem. 
My abject apologies for a rather stupid bug filing.  :-(  But there was no sign
of customization -- i.e. no /etc/php.ini.rpmnew as expected for
%config(noreplace).  I saw a bug filed about that, but never made the connection
until I downloaded the package, did an rpm2cpio | cpio -i and looked at the
contents.  Sorry to have wasted your time, thanks for not hitting me too hard. ;-)

Note You need to log in before you can comment on or make changes to this bug.