Andreas J. Koenig wrote:
I cannot understand what's the history of this tester's perl. But it has
happened on more than one setup that test on a module yield a FAIL due
to some dependency chain combined with some history of this perl
installation (or so it seems).
http://nntp.x.perl.org/group/perl.cpan.testers/5691464
http://nntp.x.perl.org/group/perl.cpan.testers/5671218
http://nntp.x.perl.org/group/perl.cpan.testers/5669841
We don't know which version of Moose was running there because Moose is
not declared prereq thus not reported. But we know that this Moose had a
prereq of Class::MOP 0.94 and nonetheless Class::MOP 0.88 was installed.
How come?
Just took a look at my environment. Class::MOP is 0.88 and Moose is 0.92.
I suppose it may be a problem with CPAN::Reporter::Smoker's "install" feature.
When Moose 0.92 is tested by CPAN, it loads Class::MOP 0.94 to PERL5LIB, then (I suggest, didn't check it myself!)
Moose gets installed while Class::MOP stays in cpan/build directory.
Just a suggestion. If Dan uses 'start("install" => 1)' too, it can be a reason
for this strange behaviour.
Will take a closer look at it when time permitted.
> Your intuition appreciated. I have seen dozens reports with this failure
> mode and they all look bogus to me and I cannot pin down what goes
> wrong.
--
Serguei Trouchelle
