Created attachment 947809 [details] Perl test script Description of problem: When executing script which uses the WWW::Mechanize module, the following error is thrown: LWP::UserAgent version 5.827 required--this is only version 2.033 at /usr/share/perl5/vendor_perl/WWW/Mechanize.pm line 132. BEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/WWW/Mechanize.pm line 132. Version-Release number of selected component (if applicable): perl-WWW-Mechanize-1.72-6.fc20.noarch perl-libwww-perl-6.05-3.fc20.noarch How reproducible: #!/usr/bin/perl -w use 5.10.1; use strict; use warnings; use WWW::Mechanize; Steps to Reproduce: 1. Create a test script with content above 2. Run it 3. Actual results: LWP::UserAgent version 5.827 required--this is only version 2.033 at /usr/share/perl5/vendor_perl/WWW/Mechanize.pm line 132. BEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/WWW/Mechanize.pm line 132. Expected results: Script runs without errors Additional info: Fedora 20 x86_64 with latest updates
I cannot reproduce it. I suspect you have an old LWP::UserAgent installed in a path that precedes vendor path. Try this command to identify the LWP::UserAgent, you use: $ perl -e 'require LWP::UserAgent; print qq{$INC{q{LWP/UserAgent.pm}} $LWP::UserAgent::VERSION\n}' /usr/share/perl5/LWP/UserAgent.pm 6.05
Thanks, here comes the result: $ perl -e 'require LWP::UserAgent; print qq{$INC{q{LWP/UserAgent.pm}} > $LWP::UserAgent::VERSION\n}' /usr/lib64/perl5/LWP/UserAgent.pm 2.033 # yum whatprovides /usr/lib64/perl5/LWP/UserAgent.pm Loaded plugins: fastestmirror, langpacks, ps, refresh-packagekit, verify, versionlock Loading mirror speeds from cached hostfile * fedora: ftp.nluug.nl * rpmfusion-free: ftp.nluug.nl * rpmfusion-free-updates: ftp.nluug.nl * rpmfusion-nonfree: ftp.nluug.nl * rpmfusion-nonfree-updates: ftp.nluug.nl * updates: ftp.nluug.nl No matches found I tried to check the file timestamp and found some odd VMware Perl SDK installation stuff, which I removed. And it works now. I feel a bit stupid, I could checked this first :-( However, this works now, so the bug may be closed...