Bug 529067 - Can we get bitbake bumped up to 1.8.12?
Summary: Can we get bitbake bumped up to 1.8.12?
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: bitbake
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Andreas Thienemann
QA Contact: Fedora Extras Quality Assurance
URL: http://prdownload.berlios.de/bitbake/...
Whiteboard:
: 503226 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-14 20:10 UTC by Robert P. J. Day
Modified: 2009-11-21 17:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-11-21 17:33:01 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robert P. J. Day 2009-10-14 20:10:46 UTC
Version 1.8.12 seems to have been out for a while, can we get it packaged for Rawhide and F12?

Comment 1 Robert P. J. Day 2009-11-04 06:05:51 UTC
If I can amend this report, bitbake 1.14 is now out: http://prdownload.berlios.de/bitbake/bitbake-1.8.14.tar.gz.  Could we get that packaged and added to Fedora 12 at some point?

Comment 2 Robert P. J. Day 2009-11-04 08:27:19 UTC
Yet another addendum, there appears to be a 1.8.16 release.

Comment 3 Bug Zapper 2009-11-16 13:41:40 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 4 Michal Ingeli 2009-11-20 15:23:49 UTC
Any progress on this? There is 1.8.18 out already. Current release in Fedora is 1.8.10 and its useless with current python and OpenEmbedeed. 

Pinging maintainer on freenode (again) right now and sending (first) notification mail.

Comment 5 Lubomir Rintel 2009-11-21 17:33:01 UTC
Thank you for your bug report.
The package was updated to 1.8.18 for Fedora 13.

Comment 6 Lubomir Rintel 2009-11-21 17:33:27 UTC
*** Bug 503226 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.