From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Broken dependency behavior in master?
Date: Mon, 04 Apr 2011 18:03:26 +0100 [thread overview]
Message-ID: <1301936606.24596.405.camel@rex> (raw)
In-Reply-To: <201104041732.48366.paul.eggleton@linux.intel.com>
On Mon, 2011-04-04 at 17:32 +0100, Paul Eggleton wrote:
> On Friday 01 April 2011 19:49:13 Scott Garman wrote:
> > I've reproduced this now, multiple times, using builds from scratch,
> > including the fact that reverting that commit fixes the the problem for me.
>
> I can confirm this, even though on the face of it the patch should not cause
> any issues.
>
> I haven't completely isolated the cause yet, however the problem occurs in
> sstate_task_postfunc -> sstate_install -> docbook_sgml_dtd_sstate_postinst
> which oddly seems to be being merged into the do_populate_lic task. I'm not
> sure but I'm assuming that these sstate functions should not be being executed
> under these circumstances.
Some data points on this:
"bitbake docbook-sgml-dtd-3.1-native -c populate_lic"
is the reproducer and the problem is the line:
SSTATEPOSTINSTFUNCS += "docbook_sgml_dtd_sstate_postinst"
in docbook-sgml-dtd-native.inc. This is running at populate_lic time as
well as populate_sysroot when its meant to run.
The commit Scott found is just a coincidence on some task order and not
responsible for this issue. I believe Scott is going to test+send a fix
which ensures the postinst only runs for the populate_sysroot postinst.
Cheers,
Richard
prev parent reply other threads:[~2011-04-04 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 0:23 Broken dependency behavior in master? Scott Garman
2011-04-01 11:31 ` Richard Purdie
2011-04-01 15:23 ` Scott Garman
2011-04-01 17:34 ` Richard Purdie
2011-04-01 18:49 ` Scott Garman
2011-04-04 16:32 ` Paul Eggleton
2011-04-04 17:03 ` 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=1301936606.24596.405.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=paul.eggleton@linux.intel.com \
--cc=poky@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.