Bug 457534 - perl-Catalyst-Manual does not provide perl(Catalyst::Manual)
Summary: perl-Catalyst-Manual does not provide perl(Catalyst::Manual)
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-Catalyst-Manual
Version: 9
Hardware: All
OS: All
low
medium
Target Milestone: ---
Assignee: Chris Weyl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-08-01 11:57 UTC by Emmanuel Seyman
Modified: 2008-08-27 01:10 UTC (History)
1 user (show)

Fixed In Version: 1.07-2.fc9
Clone Of:
Environment:
Last Closed: 2008-08-27 01:10:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Emmanuel Seyman 2008-08-01 11:57:56 UTC
Description of problem:
I'm hitting an error trying to update my system on which the perl-Catalyst-*
modules are installed.

It looks like the perl-Catalyst-Manual rpm doesn't actually provide
perl(Catalyst::Manual) and this is causing yum to fail.

[manu@orient ~]$ LANG=C sudo yum provides "perl(Catalyst::Manual)"
perl-Catalyst-Manual-5.700701-3.fc9.noarch : Catalyst web framework manual
Matched from:
Other       : perl(Catalyst::Manual)

[manu@orient ~]$ LANG=C sudo yum info perl-Catalyst-Manual
Available Packages
Name       : perl-Catalyst-Manual
Arch       : noarch
Epoch      : 1
Version    : 5.7013
Release    : 1.fc9

Note the difference between the version numbers.

Version-Release number of selected component (if applicable):
5.7013-1.fc9

How reproducible:


Steps to Reproduce:
1. Run the command "yum update"
2. yum fails, unable to update perl-Catalyst-Devel due to a missing dependency

  
Actual results:
The yum transaction aborts because it cannot find "perl(Catalyst::Manual)"

Expected results:
All rpms on the system should be updated.

Comment 1 Fedora Update System 2008-08-07 23:51:49 UTC
perl-Catalyst-Devel-1.07-2.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.