From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: BB_NO_NETWORK broken for git
Date: Thu, 05 Dec 2013 07:09:49 -0700 [thread overview]
Message-ID: <52A0892D.3090400@mlbassoc.com> (raw)
In-Reply-To: <1386251419.25847.19.camel@ted>
On 2013-12-05 06:50, Richard Purdie wrote:
> On Thu, 2013-12-05 at 05:18 -0700, Gary Thomas wrote:
>> I try to use a local source mirror, fully populated with packages, so I
>> can deliver a complete (no network required) bundle to my customers. This
>> has recently been broken.
>>
>> I can no longer use BB_NO_NETWORK=1 for git recipes, since this revision:
>> commit 2354250a95eab484459f41f8715ae112295c2174
>> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
>> Date: Mon Nov 18 17:17:16 2013 +0000
>
> Its actually the metadata that has the issue. The commit specified is
> not on the master branch, its on the cross_prelink branch so the fetcher
> is justifiably getting upset.
>
> When the network is present it does a complete reset to upstream and
> then assumes the revision is present though which is something we might
> want to fix too.
>
> For now we can at least correct the metadata to point at the right
> branch. I've sent out a patch accordingly.
Does this work for other git based repositories? My example was for
prelink, but it seems to fail for me for any SRC_URI that uses git.
For example, matchbox-keyboard also fails under the same test scenario.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-12-05 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 12:18 BB_NO_NETWORK broken for git Gary Thomas
2013-12-05 13:50 ` Richard Purdie
2013-12-05 14:09 ` Gary Thomas [this message]
2013-12-05 15:09 ` Richard Purdie
2013-12-05 15:24 ` Gary Thomas
2013-12-05 15:31 ` Richard Purdie
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=52A0892D.3090400@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox