in reply to CPAN client upgrade issues

Going from the data I guess there is a unicode/1252 translation issue and something to do with a module that was written for a UNIX environment not enjoying the Windows world.

Nope, not a chance

The specifics do not matter - I am more than willing for a few modules to prove incompatible in return for access to the whole CPAN archive.

Cool, lets not speak of them again :)

However, what IS annoying is that any single module that fails to compile stops the whole upgrade progress. Is there any way around this happening?

Sure,

cpan-outdated | xargs cpan -i

cpan-outdated | cpanm

cpan-outdated -p | cpanm

You can also skip tests and force installs, works for install Module , so would probably work for upgrade (not gonna try it)

cpan[2]> force notest upgrade

  • Comment on Re: CPAN client upgrade issues ( keep upgrading if some modules fail tests, cpan-outdated -p | cpanm )( cpan[1]> force notest upgrade )
  • Download Code

Replies are listed 'Best First'.
Re^2: CPAN client upgrade issues ( keep upgrading if some modules fail tests, cpan-outdated -p | cpanm )( cpan[1]> force notest upgrade )
by morelenmir (Beadle) on Jan 10, 2014 at 02:00 UTC
    I can't upvote you anonymous_monk - but I would if I could! WERE we to speak of it again, what do you think is causing the UTF issue?
    "Aure Entuluva!" - Hurin Thalion at the Nirnaeth Arnoediad.

      WERE we to speak of it again, what do you think is causing the UTF issue?

      Funky defaults/envvars which like LANG and LC_ALL and perl specific ones like PERLIO , PERL5OPT which would be shown by perl -V