Description: ------------ Hi. Using pear upgrade-all to upgrade Archive_Tar 1.3.3 to Archive_Tar 1.3.4 is producing an error due to the incompatibility between the two. Whilst that is an issue, my error does not relate to that, but rather the output for the error (See the Actual Results below). The issue is that PEAR_Frontend_CLI (that's all I've looked into) is using ... isset($data['key']) where $data is a string. See http://svn.php.net/viewvc/pear/pear-core/trunk/PEAR/Frontend/CLI.php?view=markup#l399 as an example. And so this will always evaluate to true (though not for PHPV5.0.0 - V5.0.2 it seems). In my testing, the actual value of $data is ... string(18) "upgrade-all failed" So, $data['release_warnings'] === 'u' which is clearly wrong. As I see it, $data must be cast to an array at the beginning of the method and use array_key_exists() rather than isset(). I don't know who will read this, but my last bug report (with patch) hasn't been processed. Though it really is the same error as this one - incorrect assumption that $data is an array when it is actually a string. Regards, Richard. Test script: --------------- pear upgrade-all Expected result: ---------------- Will upgrade channel://pear.php.net/archive_tar pear/pear dependency package "pear/Archive_Tar" installed version 1.3.4 is not the recommended version 1.3.3, but may be compatible, use --force to install pear/Archive_Tar cannot be installed, conflicts with installed packages No valid packages found RELEASE WARNINGS ================ upgrade-all failed Actual result: -------------- Will upgrade channel://pear.php.net/archive_tar pear/pear dependency package "pear/Archive_Tar" installed version 1.3.4 is not the recommended version 1.3.3, but may be compatible, use --force to install pear/Archive_Tar cannot be installed, conflicts with installed packages No valid packages found RELEASE WARNINGS ================ u u