[oe] [PATCH] sanity: release 2010.12 is out, so bump minimum bitbake to 1.10.0 per TSC decision

Tom Rini tom_rini at mentor.com
Wed Dec 22 16:35:43 UTC 2010


On 12/22/2010 08:52 AM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 22-12-10 16:45, Tom Rini wrote:
>> On 12/22/2010 05:48 AM, Frans Meulenbroeks wrote:
>>> 2010/12/22 Koen Kooi<k.kooi at student.utwente.nl>:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> On 22-12-10 12:55, Frans Meulenbroeks wrote:
>>>>> 2010/12/22 Koen Kooi<koen.kooi at gmail.com>:
>>>>>> Signed-off-by: Koen Kooi<koen at openembedded.org>
>>>>>> ---
>>>>>>    conf/sanity.conf |    2 +-
>>>>>>    1 files changed, 1 insertions(+), 1 deletions(-)
>>>>>>
>>>>>> diff --git a/conf/sanity.conf b/conf/sanity.conf
>>>>>> index 0f53cb2..1c83c14 100644
>>>>>> --- a/conf/sanity.conf
>>>>>> +++ b/conf/sanity.conf
>>>>>> @@ -3,7 +3,7 @@
>>>>>>    # See sanity.bbclass
>>>>>>    #
>>>>>>    # Expert users can confirm their sanity with "touch
>>>>>> conf/sanity.conf"
>>>>>> -BB_MIN_VERSION = "1.8.18"
>>>>>> +BB_MIN_VERSION = "1.10.0"
>>>>>>
>>>>>>    SANITY_ABIFILE = "${TMPDIR}/abi_version"
>>>>>>    SANITY_PRFILE = "${TMPDIR}/distro_pr"
>>>>>> --
>>>>>> 1.7.0
>>>>>>
>>>>>
>>>>> As 1.10.1 is already out for quite a while and (if I recall correctly)
>>>>> 1.10.0 had some issues that are resolved in 1.10.1 wouldn't it be
>>>>> better to set 1.10.1 as minimal version?
>>>>> Otherwise no objections.
>>>>
>>>> The head of the 1.10 branch says it's 1.10.0, not 1.10.1 :(
>>>
>>> Indeed :-(
>>> Guess this should be changed then
>>>
>>> There is http://developer.berlios.de/projects/bitbake/ which lists 1.10.1
>>> and the git also has a tag for 1.10.1 and a donwload for it.
>>>
>>> Btw I assume we also need to update the wiki
>>
>> I think what happened was Chris forgot to bump the version number when
>> tagging / etc.  As he plans to do a 1.10.2 soon, maybe we can wait for
>> that?  And maybe we can get that done this week?
>
> I really want the 1.10 in sooner than later, since at OEDEM we agreed to
> do it before the release, but the TSC disagreed for undisclosed reasons.

I agree and would like it done soon too (well, I'd almost rather see 
1.11 be required, yaaay parallel parsing) but since we can't tell 1.10.0 
from .1 and I don't think this week (since that's just a few more days) 
is too bad.  Chris, when can you do a 1.10.2?

-- 
Tom Rini
Mentor Graphics Corporation




More information about the Openembedded-devel mailing list