Bug 453564 - perl-Digest-Nilsimsa not built for perl 5.10.0
Summary: perl-Digest-Nilsimsa not built for perl 5.10.0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Digest-Nilsimsa
Version: 9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Warren Togami
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F9_5.10_REBUILD
TreeView+ depends on / blocked
 
Reported: 2008-07-01 11:10 UTC by Paul Howarth
Modified: 2008-07-07 10:31 UTC (History)
1 user (show)

Fixed In Version: 0.06-10.fc9
Clone Of:
Environment:
Last Closed: 2008-07-06 06:12:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Paul Howarth 2008-07-01 11:10:55 UTC
The F-9 package of perl-Digest-Nilsimsa has modules in "perl 5.8.8" paths,
which are not found by F-9's perl 5.10.0. The package therefore needs rebuilding
for perl 5.10.0.

There was a mass rebuild of perl packages late in the F-9 development period but
this package missed out on it, possibly because it is missing a perl version
"module compat" dependency and hence didn't have broken deps when perl was
upgraded to 5.10.0.

Since the ACLs are open for this package, I'll go ahead and fix it myself.

Comment 1 Fedora Update System 2008-07-01 12:41:01 UTC
perl-Digest-Nilsimsa-0.06-10.fc9 has been submitted as an update for Fedora 9

Comment 2 Fedora Update System 2008-07-02 06:32:20 UTC
perl-Digest-Nilsimsa-0.06-10.fc9 has been pushed to the Fedora 9 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update perl-Digest-Nilsimsa'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-5936

Comment 3 Fedora Update System 2008-07-06 06:12:11 UTC
perl-Digest-Nilsimsa-0.06-10.fc9 has been pushed to the Fedora 9 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.