Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 555496 - FTBFS perl-DBI-Dumper-2.01-8.fc12
Summary: FTBFS perl-DBI-Dumper-2.01-8.fc12
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-DBI-Dumper
Version: 13
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Iain Arnell
QA Contact: Fedora Extras Quality Assurance
URL: http://linux.dell.com/files/fedora/Fi...
Whiteboard:
Depends On: 557015 614980
Blocks: F13FTBFS
TreeView+ depends on / blocked
 
Reported: 2010-01-14 17:34 UTC by FTBFS
Modified: 2010-07-25 08:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-25 08:17:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
root.log (56.38 KB, text/plain)
2010-01-14 17:34 UTC, FTBFS 		no flags Details
build.log (9.55 KB, text/plain)
2010-01-14 17:34 UTC, FTBFS 		no flags Details
mock.log (980 bytes, text/plain)
2010-01-14 17:34 UTC, FTBFS 		no flags Details
root.log (65.15 KB, text/plain)
2010-01-14 17:34 UTC, FTBFS 		no flags Details
build.log (9.64 KB, text/plain)
2010-01-14 17:34 UTC, FTBFS 		no flags Details
mock.log (988 bytes, text/plain)
2010-01-14 17:34 UTC, FTBFS 		no flags Details
View All

Description FTBFS 2010-01-14 17:34:19 UTC 
perl-DBI-Dumper-2.01-8.fc12.src.rpm Failed To Build From Source against the rawhide tree.  See http://fedoraproject.org/wiki/FTBFS for more information.
If you believe this is actually a bug in another package, do NOT change the component in this bug or close this bug.  Instead, add the appropriate bug number from the other package to the "Depends on" line in this bug.  If the other package does not yet have a bug created that you think matches, please create one.  Doing so helps us properly track bugs and their dependencies, just as we track package dependencies.  (If you close this bug, and the other package is not fixed before the next FTBFS run, a new bug will get created.  Please follow the above advice to avoid such duplication.)
Comment 1 FTBFS 2010-01-14 17:34:22 UTC 
Created attachment 384246 [details]
root.log

root.log for i386
Comment 2 FTBFS 2010-01-14 17:34:23 UTC 
Created attachment 384247 [details]
build.log

build.log for i386
Comment 3 FTBFS 2010-01-14 17:34:24 UTC 
Created attachment 384248 [details]
mock.log

mock.log for i386
Comment 4 FTBFS 2010-01-14 17:34:26 UTC 
Created attachment 384249 [details]
root.log

root.log for x86_64
Comment 5 FTBFS 2010-01-14 17:34:27 UTC 
Created attachment 384250 [details]
build.log

build.log for x86_64
Comment 6 FTBFS 2010-01-14 17:34:28 UTC 
Created attachment 384251 [details]
mock.log

mock.log for x86_64
Comment 7 Marcela Mašláňová 2010-02-05 12:14:41 UTC 
I wonder if this problem with C.so could be caused by our patch of perl core package. We removed rpath which could lead to problems with linking (maybe). See in perl/devel perl-USE_MM_LD_RUN_PATH.patch
Comment 8 Bug Zapper 2010-03-15 13:58:41 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 9 Ralf Corsepius 2010-06-29 23:03:47 UTC 
I would propose this package to be retired.

Upstream appears dead, the CPAN build matrix looks frightening.
Also, AFAICT this package is not used by any package in Fedora.
Comment 10 Iain Arnell 2010-07-25 08:17:34 UTC 
This seems to be due to EU::MM changes detailed in bug #557015. As it's not using Module::Install, using DESTDIR doesn't help, but I've simply added an rm -rf to the spec to clean up the confused installation (and modernized the spec while I was at it).

http://koji.fedoraproject.org/koji/buildinfo?buildID=186350
Note You need to log in before you can comment on or make changes to this bug.