Bitbake 1.8.2 released!
Bitbake 1.8.2 has been released.
http://prdownload.berlios.de/bitbake/bitbake-1.8.2.tar.gz
This release is primarily a bugfix release. It contains several bugfixes and minor improvements over the 1.8.0 release and should be used instead of 1.8.0 in all cases. Specifically, it addresses several dependency problems that were identified in the 1.8.0 release. See the Changelog in the release for a more comprehensive list of changes.
Thanks to Holger for the release guide once again.
Cheers,
Richard
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Richard Purdie schreef:
Quoted 3 lines
Bitbake 1.8.2 has been released.
Do we have a concrete date for the 1.8 changeover already?
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGMLa8MkyGM64RGpERAsy2AKCfDmV3v3sXedO3LK5TISL0vauergCeL7dn lGqgLhzuhGP09xuLd4+FQMs=
=AxNj
-----END PGP SIGNATURE-----
Quoted 6 lines · Koen Kooi
Richard Purdie schreef:
Quoted 3 lines
Bitbake 1.8.2 has been released.
Do we have a concrete date for the 1.8 changeover already?
Not that I'm aware of. The release was the first step. I'll wait a few more days and see what other bugs appear (if any) and then I guess we run with the two month changeover.
In fact looking at the date, 1st July could be good...
Cheers,
Richard
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Richard Purdie schreef:
Quoted 10 lines · Koen Kooi
Quoted 5 lines
Richard Purdie schreef:
Quoted 3 lines
Bitbake 1.8.2 has been released.
Do we have a concrete date for the 1.8 changeover already?
Not that I'm aware of. The release was the first step. I'll wait a few more days and see what other bugs appear (if any) and then I guess we run with the two month changeover.
Everytime I say "works fine over here" someone on IRC pops up with a 1.8 problem, so I'd better stay quiet :)
Quoted 1 line
In fact looking at the date, 1st July could be good...
I thought we counted the 2 months since the initial idea (e.g. last month).
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGNjn/MkyGM64RGpERAmRQAJ4zpSg2n4/A44Gn6qORsk7Hyl1TJgCfZI3o 8oThUp+brDRROedYzTE04xw=
=QsdB
-----END PGP SIGNATURE-----
3 weeks left till requiring bitbake 1.8.x (was Re: Bitbake 1.8.2 released!)
In reply to Richard Purdie-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Richard Purdie schreef:
Quoted 12 lines · Koen Kooi
Quoted 5 lines
Richard Purdie schreef:
Quoted 3 lines
Bitbake 1.8.2 has been released.
Do we have a concrete date for the 1.8 changeover already?
Not that I'm aware of. The release was the first step. I'll wait a few more days and see what other bugs appear (if any) and then I guess we run with the two month changeover.
In fact looking at the date, 1st July could be good...
Reminder: 3 weeks left, please continue reporting any bugs with 1.8.x.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGaZSAMkyGM64RGpERAq0FAJ93KfEIYg7w3KXnbSbz+EtzE8yPjwCgvauh 1nSzGDt4isWci/+YcDg4Mhg=
=ZAse
-----END PGP SIGNATURE-----
Re: 3 weeks left till requiring bitbake 1.8.x (was Re: Bitbake 1.8.2 released!)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Koen Kooi schreef:
Quoted 12 lines
Richard Purdie schreef:
Quoted 11 lines · Koen Kooi
Quoted 5 lines
Richard Purdie schreef:
Quoted 3 lines
Bitbake 1.8.2 has been released.
Do we have a concrete date for the 1.8 changeover already?
Not that I'm aware of. The release was the first step. I'll wait a few more days and see what other bugs appear (if any) and then I guess we run with the two month changeover.
In fact looking at the date, 1st July could be good...
Done, bitbake 1.8.5 or newer is required now.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGh2fVMkyGM64RGpERAhO7AJ9ZFK0MwjJYbgW8KNHEBz+ORuVTZwCgnx7D F8kjjq2DMicsjm/191Emomc=
=jVxk
-----END PGP SIGNATURE-----
Re: 3 weeks left till requiring bitbake 1.8.x (was Re: Bitbake 1.8.2 released!)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Am 01.07.2007 um 10:37 schrieb Koen Kooi:
Quoted 2 lines
Done, bitbake 1.8.5 or newer is required now.
1.8.6 is tagged and I have a tarball but berlios.de was down yesterday...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFGh457GckbdURWU2oRAhJOAJ4rCybKgYNuu1fcPSgzuZj6fFvh4ACfSp4q vuX+eQVdmhxp4yHEufGr8cc=
=w9/A
-----END PGP SIGNATURE-----
requiring bitbake >= 1.8.5
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Holger Freyther schreef:
Quoted 6 lines
Am 01.07.2007 um 10:37 schrieb Koen Kooi:
Quoted 1 line
Done, bitbake 1.8.5 or newer is required now.
1.8.6 is tagged and I have a tarball
great news!
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGh8igMkyGM64RGpERApIHAKCUws+hU+Ve0ECD1oJN23IgptZ+NACbBUZ6 mwgqRdwuThptPe9N/9FSUYc=
=RUKh
-----END PGP SIGNATURE-----
Quoted 4 lines · Richard Purdie
Bitbake 1.8.2 has been released.
Quoted 8 lines
This release is primarily a bugfix release. It contains several bugfixes and minor improvements over the 1.8.0 release and should be used instead of 1.8.0 in all cases. Specifically, it addresses several dependency problems that were identified in the 1.8.0 release. See the Changelog in the release for a more comprehensive list of changes.
Thanks to Holger for the release guide once again.
Hmmm...I see no checkins regarding fixing the SRCDATE handling so I'd have to assume that this release still has this major bug. (which of course makes bitbake 1.8 unusable)
http://bugs.openembedded.org/show_bug.cgi?id=2133
Signature · 1 line
Justin Patrin
Damn it, I sent to both addresses again accidentally. Would someone *please* fix the list?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Justin Patrin schreef:
Quoted 11 lines · Richard Purdie
Quoted 10 lines
Bitbake 1.8.2 has been released.
http://prdownload.berlios.de/bitbake/bitbake-1.8.2.tar.gz
This release is primarily a bugfix release. It contains several bugfixes and minor improvements over the 1.8.0 release and should be used instead of 1.8.0 in all cases. Specifically, it addresses several dependency problems that were identified in the 1.8.0 release. See the Changelog in the release for a more comprehensive list of changes.
Quoted 8 lines
Quoted 2 lines
Thanks to Holger for the release guide once again.
Hmmm...I see no checkins regarding fixing the SRCDATE handling so I'd have to assume that this release still has this major bug. (which of course makes bitbake 1.8 unusable)
Try actually reading that bugreport
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGMLyOMkyGM64RGpERAkZGAJ9pNMdZbU+T9Ni9TOt32ecAVGzLjQCglXyg 9ceY6vRA+42zmzYWymTA6PQ=
=X8V/
-----END PGP SIGNATURE-----
Quoted 18 lines · Koen Kooi
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Justin Patrin schreef:
Quoted 14 lines · Richard Purdie
Quoted 12 lines
Bitbake 1.8.2 has been released.
http://prdownload.berlios.de/bitbake/bitbake-1.8.2.tar.gz
This release is primarily a bugfix release. It contains several bugfixes and minor improvements over the 1.8.0 release and should be used instead of 1.8.0 in all cases. Specifically, it addresses several dependency problems that were identified in the 1.8.0 release. See the Changelog in the release for a more comprehensive list of changes.
Thanks to Holger for the release guide once again.
Quoted 8 lines
Quoted 5 lines
Hmmm...I see no checkins regarding fixing the SRCDATE handling so I'd have to assume that this release still has this major bug. (which of course makes bitbake 1.8 unusable)
Try actually reading that bugreport
Ah. Perhaps the bug should have been closed or assigned then. Or even switched to OpenEmbedded instead of bitbake.
Quoted 13 lines
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)iD8DBQFGMLyOMkyGM64RGpERAkZGAJ9pNMdZbU+T9Ni9TOt32ecAVGzLjQCglXyg 9ceY6vRA+42zmzYWymTA6PQ=
=X8V/
-----END PGP SIGNATURE-----_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
Signature · 1 line
Justin Patrin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Justin Patrin schreef:
Quoted 2 lines
Quoted 2 lines
Ah. Perhaps the bug should have been closed or assigned then. Or even switched to OpenEmbedded instead of bitbake.
The bug couldn't be closed, since the fix needed confirmation (as the last commit asks for), and it had been switched to openembedded when we found out is was a bug in base.bbclass. Hence my reaction about actually reading the bug report. -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFGMOOzMkyGM64RGpERAlSdAKCBmbx5tXGJNVT9dC0V9NuoKg6upACZAd3t BQUj6Md/+FAvtbMDf0cB/e4=
=R1DH
-----END PGP SIGNATURE-----