Strawberry Perl (5.10.0.1) problem

numberwhun

Ok, I recently installed Strawberry Perl 5.10.0.1 on my work laptop, here at my new job. (mind you by recently, I mean about a month ago). At my last job, I was running Strawberry Perl 5.8.8 and it was working fine, no issues.

Well, I installed the product fine, went through the CPAN initial setup and configuration and even ran Bundle::CPAN without issue. I tried to install a module yesterday and I was thrown the following error:

I did some looking and couldn't find anything on this, so I re-installed Perl, but to no avail. I still get this same error. Does anyone have any clue as to what it is going on? I have not changed anything in the setup, I have only been coding and running Perl scripts. I am a little bewildered and curious as to why I am getting this error.

Thank you in advance for any help.

Best regards,

Jeff

Jun 3 '08 #1

eWish

What module was it? I am using 5.10.0.1 as well. I could see if it will install for me on my machine.

--Kevin

Jun 3 '08 #2

numberwhun

What module was it? I am using 5.10.0.1 as well. I could see if it will install for me on my machine.

--Kevin

I tried it on Expect and to re-generate the error today for this post, I ran "install Bundle::CPAN".

It doesn't matter what module I try, I get the error all the time when trying to do a module installation. Rather a pain if you ask me.

Jun 3 '08 #3

eWish

You might browse the mailing list and see if there is a know problem with this and see if there is a fix. Other than that not sure what else to suggest.

--Kevin

Jun 3 '08 #4

KevinADC

I have no idea Jeff.

Jun 3 '08 #5

numberwhun

You might browse the mailing list and see if there is a know problem with this and see if there is a fix. Other than that not sure what else to suggest.

--Kevin

Well, seeing as how I have work to do and did not really want to fuss around with an installation that was refusing to work, I removed Perl completely from my system. I went so far as to remove the directories after uninstall, including the .cpan directory. Basically, there was no trace of it left on my system.

I took the latest build from the Strawberry Perl website and installed it. Right now, I am installing Bundle::CPAN and it seems to be going fine. I don't really know, nor could I fathom what happened, but thanks anyway!

Regards,

Jeff

Jun 3 '08 #6

numberwhun

Ok, so I THOUGHT this issue was put to bed, but now I see that it isn't.

I downloaded an install script for Catalyst last night (the web Framework for Perl) and ran it to do the installation. In the script, there are a mess of "ppm" statements. I checked the bin directory for strawberry perl and there is a ppm executable in there. So, I ran it. Wouldn't you know it but it BOMBED with the original error? I did an install of WWW::Mechanize right before this and it finished fine. I am wondering if the ppm piece is messing this all up. Not sure why, but it seems to be. Here is what happens now when I try to do an install:

If nobody here has any idea, I may take this to the man himself who made Strawberry Perl and see if he has seen it happen.

Regards,

Jeff


***Update: Just so you know, I have emailed Adam Kennedy, the developer of Strawberry Perl. I think that this issue might be a bug and that he should know about it.

Jun 4 '08 #7

numberwhun

Ok, here is an update for anyone interested.

I emailed Adam Kennedy, the creator and maintainer of Strawberry Perl, and he believes that the PPM part of the script I was running might have installed a different, untested version of one of the necessary packages for Strawberry Perl (basically, IO::Uncompress).

So, his advice is to again, uninstall and reinstall, then DO NOT use the PPM script/executable. So, if you have Strawberry Perl installed, avoid the PPM script/executable at all costs.

Regards,

Jeff

Jun 4 '08 #8

eWish

Maybe you should make an article about this in case someone else has this problem.

Thanks for the update!

--Kevin

Jun 5 '08 #9

numberwhun

Maybe you should make an article about this in case someone else has this problem.

Thanks for the update!

--Kevin

True, I will have to do that. Thanks for the idea.

Jun 5 '08 #10