All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Mills <wmills@ti.com>
To: Evade Flow <evadeflow@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: BB_NO_NETWORK and own-mirrors not working with	meta-systemd
Date: Thu, 20 Sep 2012 16:32:25 -0400	[thread overview]
Message-ID: <505B7D59.3020306@ti.com> (raw)
In-Reply-To: <CAMAb8ZOAk-oF_gJmVvAVjAEN+JpS12=WpbxZjhqD0Tx6h=f4Zw@mail.gmail.com>

On 09/20/2012 04:08 PM, Evade Flow wrote:
> To bring this full circle... if you want to build behind a restrictive
> firewall using pre-mirrored sources and BB_NO_NETWORK, be aware that
> recipes which:
>
>    1. Specify a git repo as the source, and,
>
>    2. Specify the revision to be built using a tag name
>
>
> will cause your build to abort when bitbake tries to run 'git ls-remote'
> to resolve the tag name.  So don't specify SRC_URI like this:
>
>
>    SRC_URI = "git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git;protocol=git;tag=v${PV}"
>
> Instead, use:
>
>    SRC_URI = "git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git;protocol=git;tag=8885ced062131214448fae056ef453f094303805;branch=master"
>
>
> I added a note about this to the Wiki:
>
>    - http://wiki.yoctoproject.org/wiki/How_do_I#Non-networked_Builds_and_Cached_Git_Respositories
>
> I'm still new to Yocto, so someone please chime in if any of this
> information is incorrect...
>

If true, this seems very unfortunate.  This seems to push people in the 
wrong direction.  Is there a reason the fetchers don't pull down the 
tags when they mirror in the first place?



  reply	other threads:[~2012-09-20 20:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 16:34 BB_NO_NETWORK and own-mirrors not working with meta-systemd Evade Flow
2012-09-19 16:50 ` Gary Thomas
2012-09-19 17:15   ` Evade Flow
2012-09-19 17:23     ` Gary Thomas
2012-09-19 17:33       ` Evade Flow
2012-09-19 22:30         ` Evade Flow
2012-09-20  0:13           ` Gary Thomas
2012-09-20  0:43             ` Khem Raj
2012-09-20 13:30             ` Evade Flow
2012-09-20 13:38               ` Gary Thomas
2012-09-20 13:42               ` Paul Eggleton
2012-09-20 14:12                 ` Evade Flow
2012-09-20 20:08                   ` Evade Flow
2012-09-20 20:32                     ` William Mills [this message]
2012-09-20 22:30                       ` Brian Lloyd
2012-09-20 21:41                     ` Paul Eggleton
2012-09-20 22:12                       ` Evade Flow
2012-09-20 22:20                         ` Khem Raj

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=505B7D59.3020306@ti.com \
    --to=wmills@ti.com \
    --cc=evadeflow@gmail.com \
    --cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.