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

Bug #6692 Optional feature install message needs channel name
Submitted: 2006-02-04 15:11 UTC
From: saltybeagle Assigned: cellog
Status: Closed Package: PEAR (version 1.4.6)
PHP Version: Irrelevant OS: Irrelevent
Roadmaps: (Not assigned)    
Subscription  
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:
MUST BE VALID
Solve the problem : 35 - 33 = ?

 
 [2006-02-04 15:11 UTC] saltybeagle
Description: ------------ When a package has optional features a message similar to the following is shown: Chiara_PEAR_Server: Optional feature pearweb available (Public frontend for users to browse channel packages) To install use "pear install Chiara_PEAR_Server#featurename" When I run the command given I get: $ pear install Chiara_PEAR_Server#featurename No releases available for package "pear.php.net/Chiara_PEAR_Server" ... The channel name or alias needs to be included in the optional feature install message. --- To install use "pear install chiara/Chiara_PEAR_Server#featurename" --- Closely related to (fixed) bug 3677.

Comments

 [2006-02-04 15:15 UTC] saltybeagle
Example given results in same error, but instead of $ pear install Chiara_PEAR_Server#featurename I meant: $ pear install Chiara_PEAR_Server#pearweb of course.
 [2006-02-05 15:27 UTC] saltybeagle
PEAR/Command/Install.php line 539: --- $param->getPackage() . '#featurename"'; --- --- $reg->parsedPackageNameToString(array('channel' =>$param->getChannel(), 'package' => $param->getPackage()), true) . '#featurename"'; ---
 [2006-02-06 00:36 UTC] cellog
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.