Description: ------------ Hello, In Command/Remote.php: Command 'list-all' does not return the channel name from which the package is. The 'headline' of list-all also only returns 3 values, while there are 5 values to provide a headline for. Next to that, I've adapted the output a bit, to behave more like 'list-upgrades': when outputting the local and remote latest version, it now outputs <number> (<state>) You can find a patch attached.

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. I'm adding the channel to the headline, but the other changes are a BC break (API change), and will have to wait for 2.0

I closed too soon - if you implement this as --verbose, then we can add the new functionality. Can you make a patch against current CVS with this change?

This bugreport is actually a double feature request, I'm fixing it in 2 times: 1) I've created a non-intrusive patch that is backward compatible with the current PEAR, it just adds 'channel' = $channel to the header of the $data array. It does this for all relevant commands in Registry.php and Remote.php. Attached is also a patch that updates the tests to handle this. 2) When this patch gets in CVS I'll create a patch to add the more specific behaviour that the webfrontend needs with a --verbose option or something similar like you suggested.

I've implemented the channel-aware output with the option '--channelinfo (-i)'. The attached patch (channelinfo_listall) is fully BC. Note that this patch requires the 'Command_channels_BC' patch from this bugreport.

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. I've committed this with slight improvements. In the future, please use the "obsoletes patches" feature so that I can be certain I'm using the right patch. In addition, please check out the changes to Remote.xml which were missing from your patch