Couldn't them both depend on the same module, that was damaged by File::BOM and so affecting the functionality of WWW::Mechanize ?
That is possible (that's why I was investigating it), but based on my findings and experience I just thought it to be really unlikely, or rather, that other explanations (the two problems are unrelated) are much more likely. If an installation somehow got broken by a failed install of File::BOM, I would expect failures in other modules to be more loud than a silently failing file download. Plus, your logs seemed to be showing that the installation failed even before any files from the modules got to the target directories, meaning the chance that the Perl installation was affected by the install failures is small.
I'm sure about this completely new problem with WWW::Mechanize having something to do with the attempt to download/install File::BOM
I'm not sure what makes you so sure, you did write this post after updating the root node with the solution, or not? There is also a way to test this theory separately as well: You can try installing the modules without using cpan, and instead by downloading the tarball yourself and using the usual perl Makefile.PL; make; make test; make install commands (Update: see A Guide to Installing Modules). If that works, then the failure is coming from the cpan tool.
I have no idea what CPAN clients are, but I'll read about it.
cpan, what you've been using, is a CPAN client, I was suggesting that instead of cpan, you try cpanm, a different CPAN client that has basically the same functionality (it downloads and installs modules and their dependences).
In reply to Re^3: SOS: Ability to GET got BOMed (updated)
by haukex
in thread SOS: Ability to GET got BOMed (resolved)
by palkia
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |