From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: quirin.gylstorff@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 0/8] Make all sstate artifacts reproducible
Date: Thu, 20 Aug 2026 10:30:06 +0200 [thread overview]
Message-ID: <20260820083014.3377283-1-felix.moessbauer@siemens.com> (raw)
Currently many artifacts we deploy to the sstate cache are not reproducible
by itself. By that, rebuilds of the same artifact result in different sstate hashes,
which leads to cache trashing.
As a preparation to use the hashequiv signature handler, we have to make all artifacts
reproducible, as this handler tracks which input hashes influence the output hash (hash
of the artifact).
As a result of this requirement, we can no longer split the do_rootfs_install task
(which is cached) and the do_rootfs_postprocess task which makes the rootfs reproducible.
Instead, we now fold the postprocess task into the install task, similar to how OE does it.
Best regards,
Felix Moessbauer
Siemens AG
Felix Moessbauer (8):
make bootstrap output reproducible
rootfs: fold do_rootfs_postprocess task into do_rootfs_install
rootfs: make tarring of sstate artifact reproducible
rootfs: split clean_package_cache command
rootfs: make file timestamps reproducible
repository: create isar-apt with a reproducible timestamp
make our internal chroots bit-by-bit reproducible
rootfs: make capture of apt state bit-by-bit reproducible
RECIPE-API-CHANGELOG.md | 6 ++
.../recipes-core/images/isar-rootfs-ci.bb | 2 +-
.../image-account-extension.bbclass | 3 -
meta/classes-recipe/image.bbclass | 15 ++--
meta/classes-recipe/initramfs.bbclass | 5 +-
meta/classes-recipe/repository.bbclass | 19 +++++
meta/classes-recipe/rootfs.bbclass | 72 ++++++++++---------
meta/classes-recipe/sdk.bbclass | 2 +-
.../isar-mmdebstrap/isar-mmdebstrap.inc | 2 +
9 files changed, 74 insertions(+), 52 deletions(-)
--
2.55.0
--
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/20260820083014.3377283-1-felix.moessbauer%40siemens.com.
next reply other threads:[~2026-08-20 8:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 8:30 'Felix Moessbauer' via isar-users [this message]
2026-08-20 8:30 ` [PATCH 1/8] make bootstrap output reproducible 'Felix Moessbauer' via isar-users
2026-08-20 8:30 ` [PATCH 2/8] rootfs: fold do_rootfs_postprocess task into do_rootfs_install 'Felix Moessbauer' via isar-users
2026-08-20 8:30 ` [PATCH 3/8] rootfs: make tarring of sstate artifact reproducible 'Felix Moessbauer' via isar-users
2026-08-20 8:30 ` [PATCH 4/8] rootfs: split clean_package_cache command 'Felix Moessbauer' via isar-users
2026-08-20 8:30 ` [PATCH 5/8] rootfs: make file timestamps reproducible 'Felix Moessbauer' via isar-users
2026-08-20 8:30 ` [PATCH 6/8] repository: create isar-apt with a reproducible timestamp 'Felix Moessbauer' via isar-users
2026-08-20 8:30 ` [PATCH 7/8] make our internal chroots bit-by-bit reproducible 'Felix Moessbauer' via isar-users
2026-08-20 8:30 ` [PATCH 8/8] rootfs: make capture of apt state " 'Felix Moessbauer' via isar-users
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=20260820083014.3377283-1-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=quirin.gylstorff@siemens.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