9.0.1 release tarball requires bitbake 1.19.1 but provides 1.18.0?

9.0.1 release tarball requires bitbake 1.19.1 but provides 1.18.0?

[r10kindsofpeople]

[-- Attachment #1: Type: text/plain, Size: 848 bytes --]

I've run into another issue when trying to upgrade my system from Denzil to
Dylan using the released packages.  I extracted the 9.0.1 released tarball,
added the crownbay BSP, then moved my layers over from Denzil.  Sourced the
build directory, then modified bblayers.conf and local.conf to merge my
specifics with the new formats.

'bitbake core-image-minimal' results in an error... "OE-core's config
sanity checker detected a potential misconfiguration." and "Bitbake version
1.19.1 is required and version 1.18.0 was found".

A contributing factor may be that I also have a git snapshot from 2 days
ago on the same system (that builds), but I've tried to keep them in
separate directories and be careful about running the source script in it's
own shell.

Is this a problem with the release tarball or a PICNIC problem?

John

[-- Attachment #2: Type: text/html, Size: 1004 bytes --]

Re: 9.0.1 release tarball requires bitbake 1.19.1 but provides 1.18.0?

[Flanagan, Elizabeth]

On Fri, Jul 19, 2013 at 6:07 AM, r10kindsofpeople
<r10kindsofpeople@gmail.com> wrote:
> I've run into another issue when trying to upgrade my system from Denzil to
> Dylan using the released packages.  I extracted the 9.0.1 released tarball,
> added the crownbay BSP, then moved my layers over from Denzil.  Sourced the
> build directory, then modified bblayers.conf and local.conf to merge my
> specifics with the new formats.
>
> 'bitbake core-image-minimal' results in an error... "OE-core's config sanity
> checker detected a potential misconfiguration." and "Bitbake version 1.19.1
> is required and version 1.18.0 was found".
>
> A contributing factor may be that I also have a git snapshot from 2 days ago
> on the same system (that builds), but I've tried to keep them in separate
> directories and be careful about running the source script in it's own
> shell.
>
> Is this a problem with the release tarball or a PICNIC problem?
>

It shouldn't be a problem with the tarball as the download tarball is

http://downloads.yoctoproject.org/releases/yocto/yocto-1.4.1/poky-73f103bf9b2cdf985464dc53bf4f1cfd71d4531f.tar.bz2

which corresponds with the tagged release at:

http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dylan&id=73f103bf9b2cdf985464dc53bf4f1cfd71d4531f

I just validated the tarball and can't reproduce so my guess is that
this is probably a dirty env issue.

-b

> John
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
Elizabeth Flanagan
Yocto Project
Build and Release

Re: 9.0.1 release tarball requires bitbake 1.19.1 but provides 1.18.0?

[Paul Eggleton]

On Friday 19 July 2013 07:52:03 Flanagan, Elizabeth wrote:
> On Fri, Jul 19, 2013 at 6:07 AM, r10kindsofpeople
> <r10kindsofpeople@gmail.com> wrote:
> > I've run into another issue when trying to upgrade my system from Denzil
> > to Dylan using the released packages.  I extracted the 9.0.1 released
> > tarball, added the crownbay BSP, then moved my layers over from Denzil. 
> > Sourced the build directory, then modified bblayers.conf and local.conf to
> > merge my specifics with the new formats.
> > 
> > 'bitbake core-image-minimal' results in an error... "OE-core's config
> > sanity checker detected a potential misconfiguration." and "Bitbake
> > version 1.19.1 is required and version 1.18.0 was found".
> > 
> > A contributing factor may be that I also have a git snapshot from 2 days
> > ago on the same system (that builds), but I've tried to keep them in
> > separate directories and be careful about running the source script in
> > it's own shell.
> > 
> > Is this a problem with the release tarball or a PICNIC problem?
> 
> It shouldn't be a problem with the tarball as the download tarball is
> 
> http://downloads.yoctoproject.org/releases/yocto/yocto-1.4.1/poky-73f103bf9b
> 2cdf985464dc53bf4f1cfd71d4531f.tar.bz2
> 
> which corresponds with the tagged release at:
> 
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dylan&id=73f103bf9b
> 2cdf985464dc53bf4f1cfd71d4531f
> 
> I just validated the tarball and can't reproduce so my guess is that
> this is probably a dirty env issue.

It does sound that way. John, you haven't perhaps changed the path to the 
metadata but re-used the build directory, such that BBLAYERS in bblayers.conf 
still points to the development snapshot?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: 9.0.1 release tarball requires bitbake 1.19.1 but provides 1.18.0?

[r10kindsofpeople]

[-- Attachment #1: Type: text/plain, Size: 2252 bytes --]

On Fri, Jul 19, 2013 at 11:09 AM, Paul Eggleton <
paul.eggleton@linux.intel.com> wrote:

> On Friday 19 July 2013 07:52:03 Flanagan, Elizabeth wrote:
> > On Fri, Jul 19, 2013 at 6:07 AM, r10kindsofpeople
> > <r10kindsofpeople@gmail.com> wrote:
> > > I've run into another issue when trying to upgrade my system from
> Denzil
> > > to Dylan using the released packages.  I extracted the 9.0.1 released
> > > tarball, added the crownbay BSP, then moved my layers over from Denzil.
> > > Sourced the build directory, then modified bblayers.conf and
> local.conf to
> > > merge my specifics with the new formats.
> > >
> > > 'bitbake core-image-minimal' results in an error... "OE-core's config
> > > sanity checker detected a potential misconfiguration." and "Bitbake
> > > version 1.19.1 is required and version 1.18.0 was found".
> > >
> > > A contributing factor may be that I also have a git snapshot from 2
> days
> > > ago on the same system (that builds), but I've tried to keep them in
> > > separate directories and be careful about running the source script in
> > > it's own shell.
> > >
> > > Is this a problem with the release tarball or a PICNIC problem?
> >
> > It shouldn't be a problem with the tarball as the download tarball is
> >
> >
> http://downloads.yoctoproject.org/releases/yocto/yocto-1.4.1/poky-73f103bf9b
> > 2cdf985464dc53bf4f1cfd71d4531f.tar.bz2
> >
> > which corresponds with the tagged release at:
> >
> >
> http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?h=dylan&id=73f103bf9b
> > 2cdf985464dc53bf4f1cfd71d4531f
> >
> > I just validated the tarball and can't reproduce so my guess is that
> > this is probably a dirty env issue.
>
> It does sound that way. John, you haven't perhaps changed the path to the
> metadata but re-used the build directory, such that BBLAYERS in
> bblayers.conf
> still points to the development snapshot?
>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre
>


Thanks, Paul and Elizabeth.  Once I had a working bblayers.conf in the
snapshot, I just copied that file to the build directory of the release,
and forgot to change the paths inside.  Building now, sorry for the
distraction...

John

[-- Attachment #2: Type: text/html, Size: 3278 bytes --]