Menu

#173 XMLRPC::Transport::TCP version causes circular upgrades

0.71
open
Parsing (10)
5
2009-11-26
2009-11-26
No

Summary: A spelling error in the version of XMLRPC::Transport::TCP causes CPAN or CPANPLUS to chase themselves in an endless circle of upgrading SOAP::Lite.

With SOAP::Lite version 0.710.10 installed, CPAN and CPANPLUS both want to "upgrade" XMLRPC::Transport::TCP to version 0.60 because the version number in XMLRPC::Transport::TCP 0.710.10 is unparsable. Since the only way to do that is to install BYRNE/SOAP/SOAP-Lite-0.60a.tar.gz, the distribution gets downgraded.

After that, CPAN and CPANPLUS both correctly determine that SOAP::Lite is out of date and want to upgrade it. (CPAN displays SOAP::Lite as needing upgrade; CPANPLUS says it's Apache::SOAP.) After the upgrade, they detect the unparsable version in XMLRPC::Transport::TCP again, and round and round we go.

Here is the current version code from TCP.pm. Note that 'XMLRPC' is mispelled in '$XMLPRC::Lite::VERSION'.

use vars qw($VERSION);
use XMLRPC::Lite; $VERSION = $XMLPRC::Lite::VERSION;

On my system, correcting 'XMLPRC' to 'XMLRPC' fixes the problem.

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.