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] bootstrap: do not include apt cache
Date: Wed,  9 Sep 2026 18:49:59 +0200	[thread overview]
Message-ID: <20260909164959.1199121-1-felix.moessbauer@siemens.com> (raw)

We currently include the full apt cache (.deb files) in the bootstrap
artifact. As we copy-in (not mount) the existing downloads dir prior to
starting mmdebstrap, this results in the following issues:

- output tar is not reproducible (depends on the content of the
  downloads dir)
- output tar is potentially huge (multi gigabyte)

This likely is a forgotten side effect of skipping the apt cache
cleaning, as we need to preserve the lists. By instructing mmdebstrap to
only keep the lists, can avoid both issues. Later stages (like
the assembly of the sbuild-chroot) anyways sync in the apt cache from
the downloads dir, so the existing data is not needed / used.

Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
 meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc b/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
index 11706b71..a961fe1d 100644
--- a/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
+++ b/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
@@ -258,7 +258,7 @@ do_bootstrap() {
                    --customize-hook='echo nameserver 127.0.0.1 > "$1"/etc/resolv.conf' \
                    --customize-hook='echo isar > "$1"/etc/hostname' \
                    ${@'--skip=output/dev' if d.getVar('ISAR_CHROOT_MODE') == 'unshare' else ''} \
-                   --skip=cleanup/apt \
+                   --skip=cleanup/apt/lists \
                    --skip=download/empty \
                    ${MMOPTS} \
                    ${@get_apt_opts(d, '--aptopt')} \
-- 
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/20260909164959.1199121-1-felix.moessbauer%40siemens.com.

             reply	other threads:[~2026-09-09 16:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09 16:49 'Felix Moessbauer' via isar-users [this message]
2026-09-15  9:02 ` 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=20260909164959.1199121-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