Package home | Report new bug | New search | Development Roadmap Status: Open | Feedback | All | Closed Since Version 1.10.15
Request #10515 list-upgrades with channel information
Submitted: 2007-03-26 19:09 UTC
From: tias Assigned: tias
Status: Closed Package: PEAR (version 1.5.1)
PHP Version: Irrelevant OS:
Roadmaps: 1.6.0    
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 : 11 + 4 = ?

 
 [2007-03-26 19:09 UTC] tias (Tias Guns)
Description: ------------ Of course, this one too. In Command/Remote.php: The command 'list-upgrades' returns the upgrades available for 1 channel. It outputs channel information for each individual package, but not for the channel in a whole. The attached patch suplies the channel name as one of the base information, alongside 'caption' and 'headlines'. It also returns the message '(no upgrades available)' as data for the command, instead of just outputData. This way, frontends can handle this more inteligently. Please also consider implementing an 'allchannels' option, like for the 'list' command. g,T

Comments

 [2007-03-26 20:25 UTC] tias (Tias Guns)
(forget the last comment about 'allchannels', list-upgrades iterates over all channels by default)
 [2007-05-20 00:09 UTC] cellog (Greg Beaver)
could you update hte patch to implement this with a new option --verbose? This way we can preserve BC
 [2007-05-28 20:55 UTC] tias (Tias Guns)
I've implemented the channel-aware output with the option '--channelinfo (-i)'. The attached patch is fully BC. Note that this patch requires the 'Command_channels_BC' patch from request #10495
 [2007-05-29 14:54 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.