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 539048 - FTBFS k3d-0.7.11.0-1.fc12
Summary: FTBFS k3d-0.7.11.0-1.fc12
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: k3d
Version: rawhide
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL: http://linux.dell.com/files/fedora/Fi...
Whiteboard:
Depends On:
Blocks: F13FTBFS
TreeView+ depends on / blocked
 
Reported: 2009-11-19 16:35 UTC by FTBFS
Modified: 2010-03-02 00:58 UTC (History)
1 user (show)

Fixed In Version: k3d-0.7.11.0-6.fc12
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-02 00:57:08 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
root.log (1.15 MB, text/plain)
2009-11-19 16:35 UTC, FTBFS
no flags Details
build.log (6.60 KB, text/plain)
2009-11-19 16:35 UTC, FTBFS
no flags Details
mock.log (947 bytes, text/plain)
2009-11-19 16:35 UTC, FTBFS
no flags Details
root.log (1.69 MB, text/plain)
2009-11-19 16:35 UTC, FTBFS
no flags Details
build.log (6.54 KB, text/plain)
2009-11-19 16:35 UTC, FTBFS
no flags Details
mock.log (955 bytes, text/plain)
2009-11-19 16:35 UTC, FTBFS
no flags Details

Description FTBFS 2009-11-19 16:35:08 UTC
k3d-0.7.11.0-1.fc12.src.rpm Failed To Build From Source against the rawhide tree.  See http://fedoraproject.org/wiki/FTBFS for more information.

Comment 1 FTBFS 2009-11-19 16:35:12 UTC
Setting to ASSIGNED per Fedora Bug Triage workflow.  https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow

Comment 2 FTBFS 2009-11-19 16:35:16 UTC
Created attachment 371333 [details]
root.log

root.log for i386

Comment 3 FTBFS 2009-11-19 16:35:18 UTC
Created attachment 371334 [details]
build.log

build.log for i386

Comment 4 FTBFS 2009-11-19 16:35:20 UTC
Created attachment 371335 [details]
mock.log

mock.log for i386

Comment 5 FTBFS 2009-11-19 16:35:22 UTC
Created attachment 371336 [details]
root.log

root.log for x86_64

Comment 6 FTBFS 2009-11-19 16:35:24 UTC
Created attachment 371337 [details]
build.log

build.log for x86_64

Comment 7 FTBFS 2009-11-19 16:35:25 UTC
Created attachment 371338 [details]
mock.log

mock.log for x86_64

Comment 8 Fedora Update System 2010-02-10 14:42:14 UTC
k3d-0.7.11.0-6.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/k3d-0.7.11.0-6.fc12

Comment 9 Fedora Update System 2010-02-10 14:42:48 UTC
k3d-0.7.11.0-6.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/k3d-0.7.11.0-6.fc11

Comment 10 Fedora Update System 2010-02-11 14:34:51 UTC
k3d-0.7.11.0-6.fc11 has been pushed to the Fedora 11 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 k3d'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-1700

Comment 11 Fedora Update System 2010-02-11 14:49:08 UTC
k3d-0.7.11.0-6.fc12 has been pushed to the Fedora 12 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 k3d'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1730

Comment 12 Fedora Update System 2010-03-02 00:56:58 UTC
k3d-0.7.11.0-6.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 13 Fedora Update System 2010-03-02 00:58:49 UTC
k3d-0.7.11.0-6.fc12 has been pushed to the Fedora 12 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.