Bug 854577

Summary: APP::Cpan bundled with perl-Test-Harness
Product: [Fedora] Fedora Reporter: Paul Howarth <paul>
Component: perlAssignee: Petr Pisar <ppisar>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: cweyl, iarnell, kasal, lkundrak, perl-devel, ppisar, rc040203, tcallawa
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: perl-5.16.1-232.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-17 22:26:24 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paul Howarth 2012-09-05 11:10:43 UTC
The perl-Test-Harness package includes App-Cpan, which is distributed separately upstream and should I think have its own sub-package. This is not a result of  App-Cpan being split out of Test-Harness at some time in the past, but because the globbing in the perl spec file isn't specific enough to include App::Prove but exclude App::Cpan.

The effect of bundling App-Cpan with Test-Harness is quite a large number of additional dependencies.

Comment 1 Petr Pisar 2012-09-05 13:22:33 UTC
I compared files from perl with App-Cpan and with CPAN and both App::Cpan and bin/cpan come from CPAN. So I conclude the only mis-packaged App/Cpan.pm should be moved from perl-Test-Harness to perl-CPAN (both are perl subpackages).

Comment 2 Petr Pisar 2012-09-05 13:25:48 UTC
In other words, there is nothing to go into new perl-App-Cpan subpackage.

(Of course we could split perl-App-Cpan from perl-CPAN to allow dual-lived replacement of App::Cpan from App-Cpan which currently provides the latest bits, but that's different story.)

Comment 3 Paul Howarth 2012-09-05 13:51:45 UTC
I'm happy with App/Cpan.pm moving to perl-CPAN so that perl-Test-Harness doesn't pull in perl-CPAN and all of its dependencies.

Comment 4 Petr Pisar 2012-09-05 14:04:52 UTC
All Fedoras are affected.

Comment 5 Fedora Update System 2012-09-05 15:27:12 UTC
perl-5.14.2-213.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/perl-5.14.2-213.fc17

Comment 6 Fedora Update System 2012-09-05 15:29:33 UTC
perl-5.14.2-199.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/perl-5.14.2-199.fc16

Comment 7 Fedora Update System 2012-09-05 15:39:07 UTC
perl-5.16.1-229.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/perl-5.16.1-229.fc18

Comment 8 Fedora Update System 2012-09-07 11:26:15 UTC
Package perl-5.14.2-199.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing perl-5.14.2-199.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-13421/perl-5.14.2-199.fc16
then log in and leave karma (feedback).

Comment 9 Fedora Update System 2012-09-11 16:53:53 UTC
perl-5.14.2-214.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/perl-5.14.2-214.fc17

Comment 10 Fedora Update System 2012-09-11 17:03:30 UTC
perl-5.14.2-200.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/perl-5.14.2-200.fc16

Comment 11 Fedora Update System 2012-09-14 12:17:44 UTC
perl-5.14.2-215.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/perl-5.14.2-215.fc17

Comment 12 Fedora Update System 2012-09-14 12:18:58 UTC
perl-5.14.2-201.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/perl-5.14.2-201.fc16

Comment 13 Fedora Update System 2012-09-17 22:26:24 UTC
perl-5.16.1-229.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.