From: Fabien Lahoudere <fabien.lahoudere@collabora.co.uk>
To: yocto@yoctoproject.org
Subject: Re: Local repo no network help request
Date: Fri, 07 Apr 2017 10:17:59 +0200 [thread overview]
Message-ID: <1491553079.25991.60.camel@collabora.co.uk> (raw)
In-Reply-To: <CAHrosF9GEX9CTWTKFkuHXqS2jrZHMWKU6WKNTg1WWfcJee69Og@mail.gmail.com>
On Fri, 2017-04-07 at 00:38 -0700, Matthew Phillips wrote:
> I used an alternative pathname that eliminated the "/../", however it
> still failed. The debug messages show that it is able to find the
> local repo, but it seems to be trying to access HEAD regardless.
>
> I have also tried a couple of the additional flags that I can set for
> SRC_URI (ex. nobranch, usehead, etc.). Sadly, no option is available
> to limite remote fetch operations.
>
> 1) Should I locally (in the .bb file) override do_fetch?
>
> 2) I also tried running git archive [...] on the local repo, and
> pointing to the tgz file as such:
>
> SRC_URI = "file://${TOPDIR}/my-repo.tgz
>
can you bitbake -e your_recipe and paste SRC_URI contents ?
> However this too failed. Or, I don't think it failed in the do_fetch
> step, but it later failed during the build. (I saved the error
> messages, but I don't have them atm). Please advise...what am I doing
> incorrectly?
Please paste error message.
>
> Thank you,
> M
>
> On Thu, Apr 6, 2017 at 7:30 AM, Leonardo Sandoval
> <leonardo.sandoval.gonzalez@linux.intel.com> wrote:
> > On Wed, 2017-04-05 at 19:57 -0700, Matthew Phillips wrote:
> > > Hi all,
> > >
> > > I am trying to do the following:
> > >
> > > I have a local git repo, pulled manually from a remote repo (via a script).
> > > I have a .bb file set up referencing this repo. This .bb file includes
> > > (among other things):
> > >
> > > > > SRC_URI = "git://${TOPDIR}/../sources/my-repo;protocol=file;branch=master"
> > > > > SRCREV = "${AUTOREV}"
> >
> > did you get the same result if you hard-coded the pathname?
> >
> >
> >
> >
> > > I do not want to use the network (so BB_NO_NETWORK is 1).
> > >
> > > Although the SRC_URI is pointing to the correct path, the yocto build
> > > fails because it tries to access the network.
> > >
> > > How should I be doing this instead?
> > >
> > > I can run a script (preferably bash atm) before the build if doing
> > > something pre-build will help simplify anything.
> > >
> > > Thank you,
> > > M
> >
> >
next prev parent reply other threads:[~2017-04-07 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 2:57 Local repo no network help request Matthew Phillips
2017-04-06 14:30 ` Leonardo Sandoval
2017-04-07 7:38 ` Matthew Phillips
2017-04-07 8:17 ` Fabien Lahoudere [this message]
2017-04-06 14:38 ` Fabien Lahoudere
2017-04-07 16:08 ` Mark Hatle
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=1491553079.25991.60.camel@collabora.co.uk \
--to=fabien.lahoudere@collabora.co.uk \
--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.