From: Mike Westerhof <mike@mwester.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: base.bbclass changes broke BitBake 1.8.19
Date: Wed, 22 Dec 2010 09:28:05 -0600 [thread overview]
Message-ID: <4D121905.3060205@mwester.net> (raw)
In-Reply-To: <iescrt$keo$2@dough.gmane.org>
On 12/22/2010 2:28 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 21-12-10 23:00, Denys Dmytriyenko wrote:
>> Chris,
>>
>> The c67b95955d023c1f198531b4f06100a40b05efa7 has introduced the following
>> problem with BitBake 1.8.19 and even af81d52e48cb6d4f91fff0c70e09dfd421e0057d
>> didn't fix it. Any thoughts? Thanks.
>
> Since the release is out, can be bump to 1.10.0 as minimum bitbake now?
As one of the objectors when this was originally proposed, I think it
pertinent to note that I've (finally) managed to test SlugOS with
bitbake 1.10.1 and all's well, so +1 from me.
Thanks,
-Mike (mwester)
prev parent reply other threads:[~2010-12-22 15:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 22:00 base.bbclass changes broke BitBake 1.8.19 Denys Dmytriyenko
2010-12-21 22:07 ` Denys Dmytriyenko
2010-12-21 22:13 ` Chris Larson
2010-12-22 8:28 ` Koen Kooi
2010-12-22 14:00 ` Chris Larson
2010-12-22 15:28 ` Mike Westerhof [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D121905.3060205@mwester.net \
--to=mike@mwester.net \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox