Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.9.2

Bug #11489 Configuration file warning
Submitted: 2007-07-01 07:10 UTC
From: cweiske Assigned: farell
Status: Closed Package: PEAR_Info (version 1.7.0RC1)
PHP Version: Irrelevant OS:
Roadmaps: 1.7.0RC2    
Comments Add Comment Add patch

Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know! Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
Solve the problem : 17 + 11 = ?

 [2007-07-01 07:10 UTC] cweiske (Christian Weiske)
Description: ------------ Beginning with PEAR_INFO 1.7.0RC1 released some hours ago, it does not find my pear config files anymore. I get the warning: Warning: PEAR configuration file '/.pearrc' does not exist in /usr/lib/php5/share/pear/PEAR/Info.php on line 211 This worked fine in all previous versions. I have config files in /root/.pearrc and /etc/pear.conf


 [2007-07-01 15:56 UTC] farell (Laurent Laville)
Christian, I'm surprised to see such warning message displayed. If the file does not exist, you should have : Warning: PEAR configuration file '/root/.pearrc' does not exist in /usr/lib/php5/share/pear/PEAR/Info.php on line 211 The file is not fully qualified ! Related to your PEAR install User Configuration File Filename /root/.pearrc System Configuration File Filename /etc/pear.conf Could you give me more info : PEAR version, PHP version, OS version, test script used and all you think important. Thanks in advance
 [2007-07-02 05:38 UTC] cweiske (Christian Weiske)
Laurent, I use the pear_info.php script from the examples directory. Further, my webserver does not run as root but as a differernt user, thus has no access to /root/.pearrc. But it should at least detect /etc/pear.conf which it does not do.
 [2007-07-02 19:57 UTC] farell (Laurent Laville)
I've finally understood what was wrong when I tested it on my unix platform.
 [2007-07-02 20:34 UTC] farell (Laurent Laville)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on by the end of next Sunday (CET). If this was a problem with the website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.