Bug 9989 - CPANPLUS fails with an error
Summary: CPANPLUS fails with an error
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Jerome Quelin
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-05-05 10:32 CEST by Shlomi Fish
Modified: 2013-05-07 12:47 CEST (History)
0 users

See Also:
Source RPM: perl-5.16.3-1.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Shlomi Fish 2013-05-05 10:32:26 CEST
Description of problem:

When I invoke CPANPLUS And it rebuilds the module tree, I get this error:

[root@telaviv1 ~]# c Dist::Zilla::Plugin::ProgCriticTests
[MSG] Checking if source files are up to date
[MSG] Updating source file '01mailrc.txt.gz'
[MSG] Trying to get 'http://biocourse.weizmann.ac.il/CPAN/authors/01mailrc.txt.g
z'
[MSG] Updating source file '03modlist.data.gz'
[MSG] Trying to get 'http://biocourse.weizmann.ac.il/CPAN/modules/03modlist.data
.gz'
[MSG] Updating source file '02packages.details.txt.gz'
[MSG] Trying to get 'http://biocourse.weizmann.ac.il/CPAN/modules/02packages.det
ails.txt.gz'
[MSG] No '/root/.cpanplus/custom-sources' dir, skipping custom sources
[MSG] Rebuilding author tree, this might take a while
        0%.....20%.....40%.....60%.....80%.....100%
[MSG] Rebuilding module tree, this might take a while
Can't use an undefined value as an ARRAY reference at /usr/lib/perl5/5.16.3/CPAN
PLUS/Internals/Source.pm line 898.
[root@telaviv1 ~]# perl -V


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-05-05 12:02:01 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => jquelin

Comment 1 Jerome Quelin 2013-05-07 09:48:28 CEST
Shlomi, I saw that you requested a freeze push to fix the problem. Is it fixed now?
Comment 2 Shlomi Fish 2013-05-07 12:47:39 CEST
Hi Jerome,

(In reply to Jerome Quelin from comment #1)
> Shlomi, I saw that you requested a freeze push to fix the problem. Is it
> fixed now?

Yes, it is. Closing. Thanks!

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.