Bug 815367 - Build-require perl(Test::Kwalitee) on Fedora or EPEL 6 only
Summary: Build-require perl(Test::Kwalitee) on Fedora or EPEL 6 only
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Package-DeprecationManager
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Paul Howarth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 814744
TreeView+ depends on / blocked
 
Reported: 2012-04-23 13:34 UTC by Petr Pisar
Modified: 2012-05-02 04:38 UTC (History)
2 users (show)

Fixed In Version: perl-Package-DeprecationManager-0.13-2.fc17
Clone Of:
Environment:
Last Closed: 2012-05-02 04:38:26 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Constrain Test::Kwalitee to EPEL 6 (1.69 KB, patch)
2012-04-23 13:34 UTC, Petr Pisar 		no flags Details | Diff
View All

Description Petr Pisar 2012-04-23 13:34:02 UTC 
Created attachment 579539 [details]
Constrain Test::Kwalitee to EPEL 6

Please apply attached patch which removes dependency on Test::Kwalitee on EPEL > 6.
Comment 1 Fedora Update System 2012-04-23 14:26:58 UTC 
perl-Package-DeprecationManager-0.13-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/perl-Package-DeprecationManager-0.13-2.fc17
Comment 2 Fedora Update System 2012-04-24 03:17:20 UTC 
Package perl-Package-DeprecationManager-0.13-2.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing perl-Package-DeprecationManager-0.13-2.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-6459/perl-Package-DeprecationManager-0.13-2.fc17
then log in and leave karma (feedback).
Comment 3 Fedora Update System 2012-05-02 04:38:26 UTC 
perl-Package-DeprecationManager-0.13-2.fc17 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.