[yocto] BB_NO_NETWORK and own-mirrors not working with meta-systemd

[Evade Flow]

> Where did you get that meta-systemd layer?

>From here:

  - http://git.yoctoproject.org/cgit/cgit.cgi/meta-systemd/


On Wed, Sep 19, 2012 at 12:50 PM, Gary Thomas <gary at mlbassoc.com> wrote:
> On 2012-09-19 10:34, Evade Flow wrote:
>>
>> Trying to build the meta-ivi discovery-image behind a firewall is
>> proving to be quite a challenge. I tried modifying my conf/local.conf
>> file as follows:
>>
>> CONNECTIVITY_CHECK_URIS=""
>> BB_GENERATE_MIRROR_TARBALLS = "1"
>> SOURCE_MIRROR_URL ?= "file:///home/evadeflow/projects/poky-mirror/"
>> INHERIT += "own-mirrors"
>>
>> and then ran:
>>
>> % bitbake discovery-image
>>
>> in a VM on my home laptop over the weekend. (I'm trying to build using
>> the meta-ivi layer, per the instructions in its README.) After grinding
>> and churning for some 60+ hours, it finally succeeded, leaving 11 GB of
>> 'stuff' in my poky-mirror folder.
>>
>> Then, I copied the poky-mirror folder to a firewalled machine at work
>> and added:
>>
>> BB_NO_NETWORK="1"
>>
>> to local.conf.  When I tried to bitbake discovery-image on this machine,
>> I got the following error:
>>
>>
>> NOTE: Running task 697 of 3568 (ID: 1374,
>>
>> /home/evadeflow/projects/poky-git/meta-systemd/recipes-kernel/kmod/kmod_7.bb,
>> do_fetch)
>> NOTE: package kmod-7-r0: task do_fetch: Started
>> ERROR: Function failed: Network access disabled through BB_NO_NETWORK
>> but access rquested with command git ls-remote
>> git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git v7 (for url
>> None)
>> ERROR: Logfile of failure stored in:
>>
>> /home/evadeflow/projects/poky-git/build/tmp-eglibc-eglibc/work/armv7a-vfp-neon-oe-linux-gnueabi/kmod-7-r0/temp/log.do_fetch.29423
>> Log data follows:
>> | ERROR: Function failed: Network access disabled through
>> BB_NO_NETWORK but access rquested with command git ls-remote
>> git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git v7 (for url
>> None)
>> NOTE: package kmod-7-r0: task do_fetch: Failed
>> ERROR: Task 1374
>>
>> (/home/evadeflow/projects/poky-git/meta-systemd/recipes-kernel/kmod/kmod_7.bb,
>> do_fetch) failed with exit code '1'
>> Waiting for 1 running tasks to finish:
>> 0: libusb1-1.0.8-r4 do_compile (pid 29232)
>> NOTE: package libusb1-1.0.8-r4: task do_compile: Succeeded
>> NOTE: Tasks Summary: Attempted 697 tasks of which 105 didn't need to
>> be rerun and 1 failed.
>>
>> Summary: 1 task failed:
>>
>> /home/evadeflow/projects/poky-git/meta-systemd/recipes-kernel/kmod/kmod_7.bb,
>> do_fetch
>> Summary: There was 1 ERROR message shown, returning a non-zero exit code.
>> bitbake discovery-image  5338.15s user 995.52s system 187% cpu 56:12.92
>> total
>>
>> [NOTE: I'm on poky denzil at 65ffa73, meta-ivi denzil at e068388, and
>> meta-systemd denzil at 6a358e9. Also, that typo in the output
>> isn't mine, i.e., 'rquested' should be 'requested'.]
>>
>> Can anyone explain what's going on here? If I look in the poky-mirror
>> folder for kmod-related stuff, I see:
>>
>> % ls /home/evadeflow/projects/poky-mirror/*kmod*
>>
>> /home/evadeflow/projects/poky-mirror/git2_git.kernel.org.pub.scm.utils.kernel.kmod.kmod.git.tar.gz
>>
>> /home/evadeflow/projects/poky-mirror/git2_git.profusion.mobi.kmod.git.tar.gz
>>
>> I *think* this is what needs to be downloaded for this recipe(?) Why is
>> `git ls-remote` being run at all? I'm not sure whether this is the fault
>> of poky/oe-core, or of the meta-systemd layer. I'd just really wish it
>> worked. `:-}  Any advice?
>
>
> Where did you get that meta-systemd layer?  I can't find your
> recipe nor that revision (denzil at 6a358e9) in the published version
> which is at git://git.openembedded.org/meta-openembedded according
> to http://www.openembedded.org/wiki/LayerIndex
>
> --
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto