I recently got well rid of the closed source ActiveState release of perl for the reassuringly open StrawberryPerl version. One of the things I prefer is the excellent CLI CPAN client to download/upgrade any modules you are interested in. In my opinion this is hugely superior to the GUI thing in the ActiveState distribution - not least because it gives access to every module on CPAN.

However, I have been running in to some issues when I try to upgrade the modules I have already installed. After starting the CPAN client, I type for instance:

upgrade

and all seems to go well at first. Several modules are downloaded, compiled and replace their earlier versions. However, in my specific case errors start to appear when the automatic 'make test' is run on Compress::BZip2. The actual returns are too copious to reproduce here in entirety, but the following line is typical:

Malformed UTF-8 character (unexpected end of string) in read at t/026-compfile.t line 32.

and the overall summary:

Files=31, Tests=569, 13 wallclock secs (0.20 usr + 0.06 sys = 0.27 CPU)
Result: FAIL
Failed 11/31 test programs. 13/569 subtests failed.

This is only one of several modules that fail in the same way.

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. 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. 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?

"Aure Entuluva!" - Hurin Thalion at the Nirnaeth Arnoediad.

In reply to CPAN client upgrade issues by morelenmir

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.