Re^2: perlbrew clone-modules fails to install lots of modules

Thank you Corion.

> How does perlbrew clone-modules fail for these modules?

I don't know cause after the first few modules succeeded I didn't monitor the output of clone-modules nor did I scroll back looking for errors. It was a long process that I assumed had worked. It probably failed the same way shown on that github page:

! Finding Acme::Tools on cpanmetadb failed.
! Finding Acme::Tools () on mirror http://www.cpan.org failed.
! Couldn't find module or a distribution Acme::Tools

> Also, if a module like File::Fingerprint does not exist, how did it end up in your Perl installation?

Because it used to exist on CPAN but now only lives on github.com/briandfoy/file-fingerprint

> You are the only person to investigate that.

I doubt that. The github page says it's broken since 2021! Maybe others don't complain? :)

> You also don't tell us from what Perl version you are trying to clone the modules.

Sorry I didn't think it was relevant: 5.38.2

> My guess is that some of the modules fail because their prerequisites cannot be cloned...

I don't think so because I have the prerequisites. For example Acme::Tools only has few common dependencies. Also Imager itself did get cloned it was only a few image format modules that failed. It's on the same box so I have the SSL stuff that works with 5.38.2.

Comment on Re^2: perlbrew clone-modules fails to install lots of modules

Replies are listed 'Best First'.
Re^3: perlbrew clone-modules fails to install lots of modules by Corion (Patriarch) on Jan 10, 2026 at 11:11 UTC
I don't know cause after the first few modules succeeded I didn't monitor the output of clone-modules nor did I scroll back looking for errors. Then go back and do it again, and this time keep the output for inspection. Maybe simply installing one of the "unclonable" modules already fails in a way that allows you to diagnose the problem. Other people likely solved their problem that way. My guess is that some of the modules fail because their prerequisites cannot be cloned... I don't think so because I have the prerequisites. For example Acme::Tools only has few common dependencies. Also Imager itself did get cloned it was only a few image format modules that failed. It's on the same box so I have the SSL stuff that works with 5.38.2. Imager has no external non-Perl libraries dependencies it needs for installation. Imager::File::PNG needs (for example) the `libpng-dev` or `libpng-headers` package installed. Similarly things hold for the SSL libraries. Now it's time for you to get your hands dirty and check if you can install those libraries using `cpanm` (for example), and see if/how they fail there.	[reply] [d/l] [select]
Re^3: perlbrew clone-modules fails to install lots of modules by Anonymous Monk on Jan 10, 2026 at 15:21 UTC
> I don't think so because I have the prerequisites. Despite your assertion to the contrary, in many cases your "unclonable" modules are missing prerequisites. I am the author of Astro-SpaccTrack, and I can guarantee you it will not install without LWP-Protocol-https, which is also among your "unclonable" modules. My experience is that installing Net-SSLeay tends to fail because of fragile tests against informational output. Once you have force-installed (yukk!) `Net::SSLeay`, you should be able to install `Astro::SpaceTrack` without forcing it. This probably also applies to the other SSL-using modules such as SOAP-Lite. In general, when any Perl module fails to install, the first thing to do is to check whether (or not) all its prerequisites installed. If they did not (as in this case), you need to work your way back along the dependency chain and see what module(s) started the failure cascade. When you get there, you will need to provide the actual failure to get useful help, whether you go to a public forum or contact the author of the module.	[reply] [d/l] [select]