From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: "chris.laplante@agilent.com" <chris.laplante@agilent.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/4] staging: Ensure cleaned dependencies are added
Date: Wed, 07 Oct 2020 11:29:53 +0100 [thread overview]
Message-ID: <ae93fdcf366f38395f74b0eb6d22f471a57fb0be.camel@linuxfoundation.org> (raw)
In-Reply-To: <SN1PR12MB2480A99FEE6B179D1A5A76E58B0D0@SN1PR12MB2480.namprd12.prod.outlook.com>
On Tue, 2020-10-06 at 16:59 +0000, chris.laplante@agilent.com wrote:
> > > Is this patch something that should be backported to zeus and
> > > friends?
> >
> > Its fixing a very rare problem that I only ran into whilst doing
> > "interesting"
> > things most people don't probably do.
> >
> > If people were running into those issues I'd backport but for
> > master it was
> > more a correctness fix which did fix some weird corner cases I
> > debugged...
>
> A colleague today did see something that sounded to me like it may be
> fixed by this patch. It was a native tool that should have been
> available during a do_configure that wasn't. We didn't take the time
> to dig into it though - it was resolved with a -c cleansstate of the
> -native recipe and the target recipe.
I kind of wish people would dig into these things as its the only real
way we'll get them fixed. If it was this issue, removing the
prepare_recipe_sysroot stamp should have sorted the problem.
The issue is there in zeus so I guess we could need this fix there.
Question is whether its worth any other inadvertent breakage.
Cheers,
Richard
next prev parent reply other threads:[~2020-10-07 10:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 13:38 [PATCH 1/4] staging: Ensure cleaned dependencies are added Richard Purdie
2020-09-28 13:38 ` [PATCH 2/4] pseudo: Ignore mismatched inodes from the db Richard Purdie
2020-09-28 14:13 ` [OE-core] " Seebs
2020-09-28 14:51 ` Richard Purdie
2020-09-28 15:56 ` Seebs
2020-09-28 21:42 ` Richard Purdie
2020-09-29 17:05 ` Seebs
2020-09-28 13:38 ` [PATCH 3/4] pseudo: Add support for ignoring paths from the pseudo DB Richard Purdie
2020-09-28 13:38 ` [PATCH 4/4] base/bitbake.conf: Enable pseudo path filtering Richard Purdie
2020-09-28 15:15 ` [OE-core] [PATCH 1/4] staging: Ensure cleaned dependencies are added Christopher Larson
2020-09-28 17:03 ` Richard Purdie
2020-10-06 16:07 ` Chris Laplante
2020-10-06 16:49 ` Richard Purdie
2020-10-06 16:59 ` Chris Laplante
2020-10-07 10:29 ` Richard Purdie [this message]
2020-10-07 14:58 ` Chris Laplante
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=ae93fdcf366f38395f74b0eb6d22f471a57fb0be.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=chris.laplante@agilent.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