public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 1/1] rootfs: unconditionally clean isar-apt lists before deploying
Date: Wed, 23 Sep 2026 17:42:43 +0200	[thread overview]
Message-ID: <20260923154243.2429624-1-felix.moessbauer@siemens.com> (raw)

The isar-apt data is non-deterministic across builds, as the content of
the isar-apt itself changes whenever new packages are added or removed.
By that, it makes the whole chroot non-reproducible which results in
cache trashing when not building the exactly same set of targets.

As the isar-apt is anyways updated prior to using it (both in sbuild, as
well as in the rootfs tasks), we can safely drop it from the rootfs.

Note, that we cannot do the same for the upstream apt lists, as they
must not change during the build. But as they are never updated and also
do not depend on the bitbake state, it is safe to keep them.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta/classes-recipe/rootfs.bbclass | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/meta/classes-recipe/rootfs.bbclass b/meta/classes-recipe/rootfs.bbclass
index d033bdf0..1fa733d9 100644
--- a/meta/classes-recipe/rootfs.bbclass
+++ b/meta/classes-recipe/rootfs.bbclass
@@ -559,6 +559,12 @@ rootfs_postprocess_clean_package_cache() {
         \( -name '*.deb' -o -name '*.bin' \) -delete
 }
 
+# always clean the isar-apt as it is not reproducible and anyways unconditionally updated
+ROOTFS_POSTPROCESS_COMMAND += "rootfs_postprocess_clean_isar_apt_lists"
+rootfs_postprocess_clean_isar_apt_lists() {
+    run_privileged find "${ROOTFSDIR}/var/lib/apt/lists" -type f -name '_isar-apt*' -delete
+}
+
 ROOTFS_POSTPROCESS_COMMAND += "${@bb.utils.contains('ROOTFS_FEATURES', 'clean-apt-lists', 'rootfs_postprocess_clean_apt_lists', '', d)}"
 rootfs_postprocess_clean_apt_lists() {
     run_privileged find "${ROOTFSDIR}/var/lib/apt/lists" -type f -delete
-- 
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/20260923154243.2429624-1-felix.moessbauer%40siemens.com.

             reply	other threads:[~2026-09-23 15:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-23 15:42 'Felix Moessbauer' via isar-users [this message]
2026-09-29  8:08 ` Zhihang Wei

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=20260923154243.2429624-1-felix.moessbauer@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=felix.moessbauer@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