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 538993 - FTBFS kdepim-4.3.3-1.fc13
Summary: FTBFS kdepim-4.3.3-1.fc13
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: rawhide
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Than Ngo
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:21 UTC by FTBFS
Modified: 2010-01-22 09:31 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-22 09:31:06 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
root.log (1.52 MB, text/plain)
2009-11-19 16:21 UTC, FTBFS 		no flags Details
build.log (4.81 MB, text/plain)
2009-11-19 16:21 UTC, FTBFS 		no flags Details
mock.log (960 bytes, text/plain)
2009-11-19 16:21 UTC, FTBFS 		no flags Details
View All

Description FTBFS 2009-11-19 16:21:18 UTC 
kdepim-4.3.3-1.fc13.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:21:23 UTC 
Setting to ASSIGNED per Fedora Bug Triage workflow.  https://fedoraproject.org/wiki/BugZappers/BugStatusWorkFlow
Comment 2 FTBFS 2009-11-19 16:21:26 UTC 
Created attachment 371029 [details]
root.log

root.log for x86_64
Comment 3 FTBFS 2009-11-19 16:21:32 UTC 
Created attachment 371030 [details]
build.log

build.log for x86_64
Comment 4 FTBFS 2009-11-19 16:21:34 UTC 
Created attachment 371031 [details]
mock.log

mock.log for x86_64
Comment 5 Kevin Kofler 2010-01-22 09:31:06 UTC 
There have been many successful kdepim builds since that.
Note You need to log in before you can comment on or make changes to this bug.