pear v154 install/upgrade of phpunit v310b4 fails w/ incorrect version AND failure to upgrade

Hello, In response to a suggestion @ #pear/efnet, "could you send a mail to pear-general@lists.php.net so that the responsible people see this error and can decide whose fault this is?" My current version of pear: PEAR Version: 1.5.4 PHP Version: 5.2.3-dev An install of phpunit v310b4, following instructions: Installing PHPUnit http://www.phpunit.de/pocket_guide/3.1/en/installation.html Doing: pear channel-discover pear.phpunit.de pear config-set preferred_state beta pear install phpunit/PHPUnit Seems to incorrectly install an old version of phpunit, v1.3.3: pear info phpunit/phpunit ABOUT PEAR.PHPUNIT.DE/PHPUNIT-1.3.3 ===================================

   Release Type          PEAR-style PHP-based Package
   Name                  PHPUnit
   Channel               pear.phpunit.de
   Summary               Regression testing framework for unit tests.
   Description           PHPUnit is a regression testing framework used
                         by the developer who implements unit tests in
                         PHP. This is the version to be used with PHP 4.
   Maintainers           Sebastian Bergmann <sb@sebastian-bergmann.de>
                         (lead)
   Release Date          2007-05-13 10:11:17
   Release Version       1.3.3 (stable)
   API Version           1.3 (stable)
   License               BSD License
   Release Notes         http://www.phpunit.de/wiki/ChangeLog

Required Dependencies PHP version 4.1.0

                         PEAR installer version 1.4.0b1 or newer

Optional Dependencies Package pear.php.net/PHP_Compat package.xml version 2.0

   Last Modified         2007-05-16 19:56
   Previous Installed    - None -

Version Then, @ "pear upgrade-all": Will upgrade channel://pear.phpunit.de/phpunit phpunit/phpunit is already installed and is newer than detected release version 1.3.3 Cannot initialize 'channel://pear.phpunit.de/phpunit', invalid or missing package file" Is this a pkg or pear problem? In either case, what's the fix/workaround? -- RB