From: Zhihang Wei <wzh@ilbers.de>
To: Aliaksei Karpovich <akarpovich@ilbers.de>, isar-users@googlegroups.com
Subject: Re: [PATCH v2 1/2] rootfs: clean rootfs dir before unpack from sstate
Date: Thu, 29 Oct 2026 15:22:16 +0100 [thread overview]
Message-ID: <1d3ce5f2-3f1f-4297-beee-219d38ddfa32@ilbers.de> (raw)
In-Reply-To: <20261027161524.129118-1-akarpovich@ilbers.de>
Applied to next, thanks.
Zhihang
On 10/27/26 17:15, Aliaksei Karpovich wrote:
> In case when rootfs is restored (unpacked) from sstate, we have to clean
> rootfs dir because it can contain files from previous build which should
> not be included in current rootfs and will not be deleted during unpack.
> ---
> meta/classes-recipe/rootfs.bbclass | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes-recipe/rootfs.bbclass b/meta/classes-recipe/rootfs.bbclass
> index 4fd627c2..11b69d2f 100644
> --- a/meta/classes-recipe/rootfs.bbclass
> +++ b/meta/classes-recipe/rootfs.bbclass
> @@ -776,6 +776,7 @@ rootfs_install_sstate_finalize() {
> # - after restoring from cache, there will be a tar which we unpack and then delete
> if [ -f rootfs.tar ]; then
> run_privileged_heredoc <<'EOF'
> + rm -rf ${ROOTFSDIR}
> mkdir -p ${ROOTFSDIR}
> tar -C ${ROOTFSDIR} -xp ${SSTATE_TAR_ATTR_FLAGS} -f rootfs.tar
> EOF
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/1d3ce5f2-3f1f-4297-beee-219d38ddfa32%40ilbers.de.
prev parent reply other threads:[~2026-10-29 14:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 16:15 Aliaksei Karpovich
2026-10-27 16:15 ` [PATCH v2 2/2] testsuite: add test for rootfs sstate Aliaksei Karpovich
2026-10-29 14:22 ` Zhihang Wei [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=1d3ce5f2-3f1f-4297-beee-219d38ddfa32@ilbers.de \
--to=wzh@ilbers.de \
--cc=akarpovich@ilbers.de \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox