From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Barker <pbarker@toganlabs.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 4/4] runqueue: Rewrite and optimize recrdepends handling
Date: Sun, 25 Feb 2018 22:11:57 +0000 [thread overview]
Message-ID: <1519596717.24236.384.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAPyrkgwKMnb7OchXGr8OE3f_NK90ehxphS1HzGpOYjuyaKemhQ@mail.gmail.com>
On Sun, 2018-02-25 at 19:25 +0000, Paul Barker wrote:
> I've been having build failures recently which I've tracked down to
> this commit in bitbake via git bisect.
>
> I have an image recipe, oryx-image, and a publish recipe,
> oryx-publish. In oryx-publish I have a do_publish task that copies
> files out of "tmp/deploy/images/*" to their final places and so it
> needs to run after the tasks in oryx-image that create the relevant
> files. So I've explicitly added oryx-image:do_build to
> do_publish[depends].
Is do_publish added before do_build?
Does oryx-publish inherit any of the image/meta classes?
I suspect I need to better understand the problem as you've described
what you think the problem is but not what problem you're seeing...
Cheers,
Richard
next prev parent reply other threads:[~2018-02-25 22:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 12:10 [PATCH 1/4] runqueue: Fix recidepends handling Richard Purdie
2018-01-30 12:10 ` [PATCH 2/4] runqueue: Remove unused variables Richard Purdie
2018-01-30 12:10 ` [PATCH 3/4] runqueue: Optimize recrdepends handling Richard Purdie
2018-01-30 12:10 ` [PATCH 4/4] runqueue: Rewrite and optimize " Richard Purdie
2018-02-25 19:25 ` Paul Barker
2018-02-25 22:11 ` Richard Purdie [this message]
2018-02-25 22:17 ` Paul Barker
2018-02-25 22:20 ` Paul Barker
2018-02-26 16:53 ` Richard Purdie
2018-02-26 16:55 ` Paul Barker
2018-02-26 22:20 ` Paul Barker
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=1519596717.24236.384.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=pbarker@toganlabs.com \
/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.