Closed Bug 559718 Opened 15 years ago Closed 15 years ago

Bugzilla fails to install modules because of "Can't call method "cpan_version" on an undefined value"

Categories

(Bugzilla :: Installation & Upgrading, defect)

defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mozilla.bugs, Unassigned)

Details

Can't call method "cpan_version" on an undefined value at [Path to Bugzilla]/Bugzilla/Install/CPAN.pm line 96" I get this whenever I try to install a new module using /usr/bin/perl install-module.pl [Module name] on Bugzilla 3.6 after using CVS to upgrade from 3.4.latest. I didn't see this on Bugzilla 3.4.x. I am using Ubuntu 9.04 with Perl v5.10.0. This error is not restricted to any specific perl module, that I try to install.
Summary: Bugzilla fails to install modules because of "Can't call method "cpan_method" on an undefined value" → Bugzilla fails to install modules because of "Can't call method "cpan_version" on an undefined value"
Okay. What was the CVS command you used to do the cvs update? Were there any conflicts?
It didn't mention any conflicts, I just used the instructions in http://www.bugzilla.org/download/#cvs and ran $ cvs update -rBugzilla_Stable -dP I have edited one file in my local install, but it didn't have any conflicts merging (and the file is the Bugzilla index page template, which shouldn't affect CPAN.pm). There are no privilege or ownership issues which would have caused merge problems.
Okay. Have you used CPAN since you last used install-module.pl? When was the last time this worked for you?
I'm not sure--though it was recent, but I would guess this has something specifically to do with JSON::RPC and Test::Taint, which CPAN says it has installed and compiled, but I have no proof of that, and Bugzilla doesn't detect them. The other modules installed correctly some time ago, and I am at the current version of CPAN. I will investigate this more in the morning.
Okay. I suspect that your CPAN home directory got messed up--you might want to try rm -rf ~/.cpan/
That would be my guess too, since it has downloaded the code and keeps running make and saying it was successful even though nothing happens. That approach has fixed similar issues several times already on this box for me--it has a tendency to do that.
Okay, I'm going to say WORKSFORME on this one, for now, then. If you discover that it's actually a problem with Bugzilla itself, let me know.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.