Bug 1106006

Summary: bitbake: FTBFS in rawhide
Product: [Fedora] Fedora Reporter: Dennis Gilmore <dennis>
Component: bitbakeAssignee: Christopher Meng <i>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: andreas, mjuszkie
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: bitbake-1.17.0-1.fc21 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-03 13:39:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1105908    
Attachments:
Description Flags
build.log
none
root.log
none
state.log none

Description Dennis Gilmore 2014-06-09 02:15:50 UTC 
Your package bitbake failed to build from source in current rawhide.

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

For details on mass rebuild see https://fedoraproject.org/wiki/Fedora_21_Mass_Rebuild
Comment 1 Dennis Gilmore 2014-06-09 02:15:52 UTC 
Created attachment 903609 [details]
build.log
Comment 2 Dennis Gilmore 2014-06-09 02:15:54 UTC 
Created attachment 903610 [details]
root.log
Comment 3 Dennis Gilmore 2014-06-09 02:15:55 UTC 
Created attachment 903611 [details]
state.log
Comment 4 Marcin Juszkiewicz 2014-06-17 12:27:00 UTC 
BitBake 1.18 is few years old. if no one noticed that so far then this package looks like perfect candidate for removal.

And few years old does not mean "but still can be used". It is developed (at 1.23.1 now) and is in constant use by OpenEmbedded related projects.
Comment 5 Fedora Admin XMLRPC Client 2014-07-02 19:48:02 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 6 Christopher Meng 2014-07-03 13:39:13 UTC 
I will build 1.17 first, if upstream can tag the new version via gittags again I'd be happy to build a new one.