Geek Answers Handbook

An attempt to install Moose-2.000 through PPM / Activestate 5.12 on Win32 - 404 was not found

This is an unusual error that has not occurred before. I use PPM on Windows to install modules for Perl. Works great with tons of modules. But it looks like there is nothing wrong with the Moose-2.000 package, and I don’t know how to fix it.

To duplicate the error:

Install the latest version of Activestate on a Windows PPM machine in cmd look for "moose" tick Moose to install

He says:

Moose marked for install Installing package ... Downloading Moose-2.0000 ... not found Installing package failed ERROR: 404 Not Found

I added almost all the repositions I could find, but it seems to come from activestate's.

Forgive me, but I really have no idea how to install the module manually (without a simple GUI). I downloaded the tar file, unpacked it, and ran makefile.pl. I copied the lib files to the / perl / site / lib folder.

Unfortunately, PPM expects a PPD shell (or something else), so I can’t do the command line installation, for example, "ppm install URL-of-package".

Can someone try this and let me know if you are lucky? If not, provide a step-by-step guide on how to install this particular package. I would be grateful because many other things (such as the Twitter package) depend on this!

thanks

UDPATE:

ok it looks like v2.000 just does not exist for Win32. so I was able to install v1.25 in the following workaround explained in bugtracker activestate (see comments).

Workaround:

1) Find the latest version for your platform here:

http://ppm4.activestate.com/idx/MOO...MY.html

Click on the icons in the PPMX column to see the target platform and the Perl version.

2) Copy the URL of the .ppmx file

3) Use the URL as an argument to "ppm install". For example, for 5.12 Win x86:

 ppm install

http://ppm4.activestate.com/MSWin32-x86/5.12/1200/D/DR/DROLSKY/Moose-1.25.ppmx

+4
source share
1 answer

I see the same problem - it looks like a quirk on the ActiveState side. Only 1.25 is still available in their package index . Maybe only the changes are not yet directed towards the mirrors.

Change I recently upgraded to Moose 2.0001, which seems to be fixed. However, I had a conflict with Class-MOP , which comes with ActivePerl 5.12. It turned out that Class :: MOP and Moose are combined. The solution was to remove both Class-MOP and Moose before installation:

 ppm rem Class::MOP --force ppm rem Class::MOP --area perl --force ppm rem Moose --area perl --force ppm inst Moose
+1
source

More articles:


All Articles