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.mo...@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