Thank you very much for letting me know about this. A broken
distribution is "Critical" if anything is.
Unfortunately, I have not been able to duplicate your problem. Let me
detail my situation and what I have done, and maybe something will
suggest itself. If you like, skip to the last 3 or 4 paragraphs, and
read the intervening stuff only if you want the gory details.
I use CPAN::Mini to keep a local repository (mirrored from
cpan.pair.com), and I tend to inject my modules into this rather than
waiting for them to propagate through the CPAN mirror system, so it's
possible something happened during the PAUSE upload or during mirror
propagation.
You do not say (that I saw!) what CPAN client you used. I use cpan
(rather than cpanp or cpanm), and your output looked familiar, so that's
what I tested with.
I tried changing my CPAN mirror to
http://cpan.pair.com/ and
http://www.cpan.org/. In each I did a 'cpan> look' followed by a build
and test. Both succeeded.
Next I did an
$ lwp-request -m GET
'
http://www.cpan.org/authors/id/W/WY/WYANT/PPIx-Regexp-0.030.tar.gz'
Show quoted text>PPIx-Regexp-0.030.tar.gz
and expanded, built, and tested the resultant tarball. This also worked.
Next I did
$ wget '
http://www.cpan.org/authors/id/W/WY/WYANT/PPIx-Regexp-0.030.tar.gz'
and expanded, built and tested the resultant tarball. This also worked.
Next, I looked at the CPAN testers web site:
http://www.cpantesters.org/distro/P/PPIx-Regexp.html#PPIx-Regexp-0.030
This is more equivocal. The summary shows pass results for 0.030, but no
individual tests results have appeared yet. Even if they did, it would
not prove that every tester was able to access the distribution.
All of this is not intended to be beating you over the head -- it's
intended more to make credible the statement "I can't duplicate your
problem, and I _did_ try."
So what now?
It used to be that if you used
http://www.cpan.org/ as your CPAN
repository, you got a redirect, and if you tried to fetch a new
distribution from a mirror it had not yet propagated to, strange things
happened. But at least one of the tools involved (wget? curl?) displayed
redirect messages when this happened, and neither your log nor my
testing turned up any. More than that, I successfully downloaded with
wget using --max-redirect=0.
I have two thoughts at this point:
* Try again, maybe with another mirror. This is per the redirect
hypothesis. It may not be correct, but it's easy enough to try.
* Compare configurations to see if the comparison suggests something. I'm:
Mac OS 10.8.2 Mountain Lion;
Perl 5.16.2;
CPAN 1.9800;
LWP::UserAgent 6.04;
Behind a NAT router, but not a proxy firewall;
Using Comcast as my ISP.