Bug 453411 - perl-mogilefs-server not built for perl 5.10.0
perl-mogilefs-server not built for perl 5.10.0
Status: CLOSED NEXTRELEASE
Product: Fedora
Classification: Fedora
Component: perl-MogileFS-Server (Show other bugs)
9
All Linux
low Severity low
: ---
: ---
Assigned To: Ruben Kerkhof
Fedora Extras Quality Assurance
:
Depends On:
Blocks: F9_5.10_REBUILD
  Show dependency treegraph
 
Reported: 2008-06-30 09:50 EDT by Paul Howarth
Modified: 2008-09-10 08:20 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-09-10 08:20:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Patch to add perl(:MODULE_COMPAT... dependencies to subpackages (1.78 KB, patch)
2008-06-30 09:50 EDT, Paul Howarth
no flags Details | Diff

  None (edit)
Description Paul Howarth 2008-06-30 09:50:23 EDT
The F-9 packages of perl-mogilefs-server have 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 some perl version
"module compat" dependencies (the main package has one but the subpackages,
which also install into versioned perl module directories don't) and hence
didn't have broken deps when perl was upgraded to 5.10.0.

Also, the bugzilla component for this package is perl-MogileFS-Server but the
package in cvs is perl-mogilefs-server, which seems a bit odd.
Comment 1 Paul Howarth 2008-06-30 09:50:23 EDT
Created attachment 310587 [details]
Patch to add perl(:MODULE_COMPAT... dependencies to subpackages
Comment 2 Ruben Kerkhof 2008-07-02 05:44:32 EDT
Thanks for noticing this Paul.
I'll have a look later this week.
Comment 3 Ruben Kerkhof 2008-09-10 08:20:03 EDT
Fixed in 2.17-6

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