From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steffen Sledz <sledz@dresearch-fe.de>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>,
openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: fetch race problem
Date: Tue, 07 Apr 2015 13:29:48 +0100 [thread overview]
Message-ID: <1428409788.14020.461.camel@linuxfoundation.org> (raw)
In-Reply-To: <552396CA.7060806@dresearch-fe.de>
On Tue, 2015-04-07 at 10:35 +0200, Steffen Sledz wrote:
> Am 24.03.2015 um 12:12 schrieb Richard Purdie:
> >>> Is this a problem in oe-core too (or oe-classic only)?
> >>
> >> Any ideas how to avoid such errors?
> >
> > In theory bitbake has locks on files in DL_DIR, even for git
> > repositories so it should only touch the repo with one fetch process at
> > a time even if multiple recipes reference the same thing.
> >
> > There were some big fetcher reworks in more recent versions of bitbake.
> > For OE-Classic, I'm guessing you're using an older version. You could
> > try transplanting the modern fetcher core onto your older bitbake I
> > guess.
>
> I do not feel competent enough to try this.
>
> Is it possible (in oe-classic) to mark two or more recipes (or single stages) to run exclusive?
do_fetch[depends] += "xxx:do_fetch"
in one recipe would make it run after the fetch of the other recipe
(xxx) ...
I will say that oe-classic is dead at this point, its not something I'd
recommend people to be working with.
Cheers,
Richard
prev parent reply other threads:[~2015-04-07 12:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 11:00 fetch race problem Steffen Sledz
2015-03-24 11:12 ` Richard Purdie
2015-04-07 8:35 ` Steffen Sledz
2015-04-07 12:29 ` Richard Purdie [this message]
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=1428409788.14020.461.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=sledz@dresearch-fe.de \
/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