atom feed15 messages in org.freebsd.freebsd-questionsRe: CPAN hanging on ExtUtils::MakeMak...
FromSent OnAttachments
Jaime KikpoleFeb 21, 2012 4:33 pm 
Matthew SeamanFeb 22, 2012 1:26 am 
Jaime KikpoleFeb 22, 2012 4:48 am 
Matthew SeamanFeb 22, 2012 6:07 am 
Alejandro ImassFeb 22, 2012 7:53 am 
Alejandro ImassFeb 22, 2012 8:35 am 
Matthew SeamanFeb 22, 2012 8:35 am 
Matthew SeamanFeb 22, 2012 8:40 am 
Alejandro ImassFeb 22, 2012 8:40 am 
Alejandro ImassFeb 22, 2012 8:55 am 
Jaime KikpoleFeb 22, 2012 10:48 am 
Chuck SwigerFeb 22, 2012 11:34 am 
Matthew SeamanFeb 22, 2012 12:24 pm 
Ireneusz PlutaFeb 23, 2012 8:22 am 
Jaime KikpoleFeb 24, 2012 10:30 am 
Subject:Re: CPAN hanging on ExtUtils::MakeMaker even if installed
From:Matthew Seaman (m.se@infracaninophile.co.uk)
Date:Feb 22, 2012 8:35:59 am
List:org.freebsd.freebsd-questions

On 22/02/2012 15:54, Alejandro Imass wrote:

On Tue, Feb 21, 2012 at 7:34 PM, Jaime Kikpole <jkik@cairodurham.org> wrote:

I'm attempting to upgrade Request Tracker manually. (I know that there is a port, but I'd like to preserve my data, thus I'm doing this "the old fashioned way." :) )

When I run the "make fixdeps" step described in the directions, it attempts to load ExtUtil::MakeMaker from CPAN -- even though its already installed. This wouldn't be so bad, but it actually hangs and uses 100% of CPU time (according to "top") like its in an infinite loop. This is the output just before it hangs:

Your post makes me very happy to know I wasn't crazy:

http://www.perlmonks.org/?node_id=918414

This is a pain in the ass and I don't know if it's a FBSD CPAN problem or a CPAN dependency problem but it does happen, and it's really annoying. I don't have a fix but a workaround. It will always hang on the same test, so just ^C and "look" into the module. remove the test and go back to the cpan shell. It won't bother you again for the whole CPAN session.

Actually, the problem as highlighted in that Perlmonks article was with BSDPAN::ExtUtils::Packlist. A fix has been applied to the perl5.10, perl5.12 and perl5.14 ports.

Anyone still using perl5.8 should take this as a broad hint that it might be time to upgrade...

Cheers,

Matthew