in reply to CPAN bundle versions

I can't say I've ever seen this problem. Are you using the latest version of the CPAN.pm module? Does the module info command give you any hints? Does it help if you blow away your .cpan directory?

-sam

Replies are listed 'Best First'.
Re^2: CPAN bundle versions
by kgoess (Beadle) on Mar 16, 2005 at 20:41 UTC
    > Are you using the latest version of the CPAN.pm module?

    Yep, 1.76.

    > Does the module info command give you any hints?

    It says it sees new version, and acknowledges that the installed version is old,

    Bundle id = Bundle::Mercury
        CPAN_VERSION 0.08
        CPAN_FILE    ALL/Bundle-Mercury-0.08.tar.gz
        MANPAGE      Bundle::Mercury - Modules required for mercury application
        CONTAINS     Term::ReadKey ...<snip>
        INST_FILE    /home/kgoess/.cpan/Bundle/Mercury.pm
        INST_VERSION 0.07
    
    but immediately after running that command, running "install Bundle::Mercury" pulls in the old module list from v0.07.

    > Does it help if you blow away your .cpan directory?

    Yes, in fact all we need to do is delete .cpan/Bundle/Mercury.pm and it pulls in the new bundle and module list.

    Running the process through the debugger suggests that it's a bug/feature in CPAN.pm, first it gets the bundle information from the network version, then a few lines later it gets the bundle information from the local file.

      Well it certainly doesn't sound like a feature to me! I think you should report it to the author of CPAN.pm as a bug. The module seems to be updated quite frequently which implies that bugs are being fixed regularly.

      -sam