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

Bug #11420 warning on pecl (un)install with --register-only option
Submitted: 2007-06-24 11:42 UTC
From: remicollet Assigned: cellog
Status: Closed Package: PEAR (version 1.6.1)
PHP Version: 5.2.3 OS: Fedora
Roadmaps: 1.6.2    
Subscription  


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:
MUST BE VALID
Solve the problem : 10 + 28 = ?

 
 [2007-06-24 11:42 UTC] remicollet (Remi Collet)
Description: ------------ Hi, I'm working on registering PECL extensions during RPM post scriplet as we used to do for PEAR extensions. Using --register-only produce Notice and Warning With (very simple) patch proposed, all works fine. Note, there is no need to (un)register the extension in the php.ini, as this is done in the RPM stuff. Regards Test script: --------------- # pecl install --nodeps --soft --force --register-only --nobuild package.xml Notice: Undefined variable: binaries in PEAR/Command/Install.php on line 703 Warning: Invalid argument supplied for foreach() in PEAR/Command/Install.php on line 703 Warning: Invalid argument supplied for foreach() in /usr/share/pear/PEAR/Command/Install.php on line 703 install ok: channel://pecl.php.net/APC-3.0.14 # pecl uninstall --nodeps --ignore-errors --register-only APC Notice: Undefined variable: binaries in PEAR/Command/Install.php on line 944 Warning: Invalid argument supplied for foreach() in PEAR/Command/Install.php on line 944 Warning: Invalid argument supplied for foreach() in /usr/share/pear/PEAR/Command/Install.php on line 944 uninstall ok: channel://pecl.php.net/APC-3.0.14 Expected result: ---------------- No warning or notice.

Comments

 [2007-09-03 03:07 UTC] cellog (Greg Beaver)
This bug has been fixed in CVS. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net 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.