From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Pedro Silva Ferreira <Pedro.Silva.Ferreira@criticaltechworks.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH v2 1/2] buildhistory: fix package output folder creation
Date: Thu, 29 Aug 2024 13:00:49 +0100 [thread overview]
Message-ID: <0478d307fad333e96d7cb2c2c5f33058d6afd860.camel@linuxfoundation.org> (raw)
In-Reply-To: <AM8P193MB09004DD00D04193F371CA700C7962@AM8P193MB0900.EURP193.PROD.OUTLOOK.COM>
You'd have to test it but I've a patch I've been working on which drops
the use of SSTATEPOSTINSTFUNCS from buildhistory entirely. I've just
sent that out for review.
That might be enough to fix this on the release branches for
buildhistory even if it doesn't fix the sstate bug.
Cheers,
Richard
next prev parent reply other threads:[~2024-08-29 12:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 12:59 [PATCH v2 1/2] buildhistory: fix package output folder creation Pedro Ferreira
2024-08-06 12:59 ` [PATCH v2 2/2] buildhistory: Restoring files from preserve list Pedro Ferreira
2024-08-07 15:55 ` [OE-core] [PATCH v2 1/2] buildhistory: fix package output folder creation Alexandre Belloni
2024-08-07 16:44 ` Richard Purdie
2024-08-08 12:19 ` Peter Kjellerstedt
2024-08-13 8:05 ` Pedro Ferreira
2024-08-13 12:09 ` [OE-core] " Steve Sakoman
2024-08-27 12:50 ` Pedro Silva Ferreira
2024-08-27 14:10 ` Richard Purdie
2024-08-29 10:55 ` Pedro Silva Ferreira
2024-08-29 11:53 ` Richard Purdie
2024-08-29 12:00 ` Richard Purdie [this message]
2024-08-29 14:21 ` Pedro Silva Ferreira
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=0478d307fad333e96d7cb2c2c5f33058d6afd860.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Pedro.Silva.Ferreira@criticaltechworks.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