CentOS 5.7 install/upgrade fails because YAML not used in lib/CPAN.pm

RESOLVED INVALID

Status

()

RESOLVED INVALID
7 years ago
7 years ago

People

(Reporter: rkl, Unassigned)

Tracking

4.0.4
x86_64
Linux

Details

(Reporter)

Description

7 years ago
I was doing an upgrade of Bugzilla from 4.0.2 to 4.0.4 on a 64-bit CentOS 5.7 system and it refused to proceed correctly (complaining about YAML). Further investigation showed that lib/CPAN.pm fails to use the YAML module and the whole install falls over because of that.

The fix was to add a "use YAML;" statement to lib/CPAN.pm around about line 60 (e.g. just after the "use Text::Wrap ();" statement:

use Text::Wrap ();
use YAML;

Assuming this doesn't break non-CentOS 5 systems, it may be a candidate fix to be included in a future Bugzilla release.

Comment 1

7 years ago
(In reply to Richard Lloyd from comment #0)
> Further investigation showed that lib/CPAN.pm fails to use the YAML module

Which lib/CPAN.pm file are you talking about? What's the full path to it?
(Reporter)

Comment 2

7 years ago
It may well be a CPAN.pm that is from a CPAN installation on the CentOS 5.7 system - it was on the system as <webtree>/lib/CPAN.pm - there are also a lot of other Perl modules in <webtree>/lib including YAML. I suspect these came from a "./checksetup.pl" and then a "/usr/bin/perl install-module.pl --all" to add missing Perl modules.

Perl in CentOS 5.7 is version 5.8.8 - I don't know if that causes issues with the YAML module (e.g. maybe CPAN assumes that YAML support is standard in later perl versions and hence why "use YAML;" wasn't present in <webtree>/lib/CPAN.pm?). Could one workaround be to put "use YAML;" in one or more of the shipped Bugzilla scripts - e.g. in install-module.pl - though you'd have to check it's installed first I guess.

Comment 3

7 years ago
lib/CPAN.pm is a file that was installed by Bugzilla from CPAN when you did install-module.pl --all. It may perhaps have a bug in it, but it's unfortunately not our bug and so we can't fix it.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.