Bug 1105997 - bcfg2: FTBFS in rawhide
Summary: bcfg2: FTBFS in rawhide
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: bcfg2
Version: 22
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F21FTBFS
TreeView+ depends on / blocked
 
Reported: 2014-06-09 02:14 UTC by Dennis Gilmore
Modified: 2016-07-14 13:20 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-14 13:20:41 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
build.log (373.94 KB, text/plain)
2014-06-09 02:14 UTC, Dennis Gilmore 		no flags Details
root.log (97.69 KB, text/plain)
2014-06-09 02:14 UTC, Dennis Gilmore 		no flags Details
state.log (1.06 KB, text/plain)
2014-06-09 02:14 UTC, Dennis Gilmore 		no flags Details
View All

Description Dennis Gilmore 2014-06-09 02:14:52 UTC 
Your package bcfg2 failed to build from source in current rawhide.

http://koji.fedoraproject.org/koji/taskinfo?taskID=6938978

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
Comment 1 Dennis Gilmore 2014-06-09 02:14:56 UTC 
Created attachment 903585 [details]
build.log
Comment 2 Dennis Gilmore 2014-06-09 02:14:58 UTC 
Created attachment 903586 [details]
root.log
Comment 3 Dennis Gilmore 2014-06-09 02:14:59 UTC 
Created attachment 903587 [details]
state.log
Comment 4 Jaroslav Reznik 2015-03-03 15:53:31 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 5 Fedora Admin XMLRPC Client 2016-07-14 13:18:15 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 6 Fabian Affolter 2016-07-14 13:20:41 UTC 
Package is retired.
Note You need to log in before you can comment on or make changes to this bug.