Re: BB_NO_NETWORK = "1" causes fetch to fail for unnecessary u-boot parsing

[Martin Jansa <martin.jansa@gmail.com>]

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

On Tue, Jan 29, 2013 at 04:54:30AM -0500, Robert P. J. Day wrote:
> On Tue, 29 Jan 2013, Martin Jansa wrote:
> 
> > On Tue, Jan 29, 2013 at 04:08:10AM -0500, Robert P. J. Day wrote:
> > >
> > >   not sure if this is expected behaviour, but i'm using the meta-ti
> > > layer to build a core-image-minimal for a am180x-evm.  i'm using
> > > "own-mirrors" to use my own premirrors directory and i've collected
> > > all of the necessary tarballs and actually completed the build, after
> > > which i make sure i have saved all of the tarballs so i don't need
> > > to download anything for a subsequent build.
> > >
> > >   as a test, i totally delete my build and start over, but this time
> > > with
> > >
> > >   BB_NO_NETWORK = "1"
> > >
> > > which i assumed would still work.  instead, i almost immediately got
> > > this:
> > >
> > > $ bitbake -c fetch core-image-minimal
> > > Pseudo is not present but is required, building this first before the
> > > main build
> > > ERROR: ExpansionError during parsing
> > > /home/rpjday/oe/dist/layers/meta-ti/recipes-bsp/u-boot/u-boot_2013.01.bb:
> > > Failure expanding variable SRCPV, expression was
> > > ${@bb.fetch2.get_srcrev(d)} which triggered exception NetworkAccess:
> > > Network access disabled through BB_NO_NETWORK but access requested
> > > with command git ls-remote
> > > git://arago-project.org/git/projects/u-boot-keystone.git
> > > DEV.MCSDK-03.00.00.06 (for url None)
> > > ERROR: Command execution failed: Exited with 1
> >
> > It's using tag instead of hash in SRCREV, so it behaves the same as
> > SRC_URI = "git://.*;tag=foo" and tries to access upstream repo to
> > convert tag name to hash (or check if it's still the same hash as when
> > you've built it last time.
> 
>   ah ... so as a cheap hack to get around this, as long as i don't
> need that recipe, i guess i could just BBMASK it out.  is that the
> easiest solution?  thanks.

It would be better to change SRCREV to hash corresponding to that tag
and move tag only to comment above SRCREV. Such patch could be applied
in upstream...

Cheers,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]