From: "'Felix Moessbauer' via isar-users" <isar-users@googlegroups.com>
To: isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, quirin.gylstorff@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH v5 05/17] bootstrap: move cleanup trap to function
Date: Tue, 9 Jun 2026 14:33:43 +0200 [thread overview]
Message-ID: <20260609123355.2368573-6-felix.moessbauer@siemens.com> (raw)
In-Reply-To: <20260609123355.2368573-1-felix.moessbauer@siemens.com>
By that, we can make the trap more easily conditional.
Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
---
.../isar-mmdebstrap/isar-mmdebstrap.inc | 25 +++++++++++--------
1 file changed, 15 insertions(+), 10 deletions(-)
diff --git a/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc b/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
index 596a6152..eba6ea85 100644
--- a/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
+++ b/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
@@ -110,10 +110,24 @@ def get_apt_auth_opts(d):
f"--setup-hook='upload \"{workdir}/apt-auth\" /etc/apt/auth.conf.d/isar.conf'"
return ''
+bootstrap_cleanup() {
+ [ -r "${WORKDIR}/mmtmpdir" ] && tmpdir=$(cat "${WORKDIR}/mmtmpdir") \
+ && rm "${WORKDIR}/mmtmpdir"
+ [ -d "$tmpdir" ] && mountpoint -q $tmpdir/$base_apt_tmp \
+ && run_privileged umount $tmpdir/$base_apt_tmp
+ [ -d "$tmpdir" ] && mountpoint -q $tmpdir/base-apt \
+ && run_privileged umount $tmpdir/base-apt
+ [ -d "$tmpdir" ] && run_privileged rm -rf --one-file-system $tmpdir
+ [ -n "$base_apt_tmp" ] && mountpoint -q $base_apt_tmp \
+ && run_privileged umount $base_apt_tmp \
+ && rm -rf --one-file-system $base_apt_tmp
+}
+
do_bootstrap[vardeps] += " \
DISTRO_APT_PREMIRRORS \
ISAR_ENABLE_COMPAT_ARCH \
${DISTRO_VARS_PREFIX}DISTRO_APT_SOURCES \
+ bootstrap_cleanup \
"
do_bootstrap[dirs] = "${DEPLOY_DIR_BOOTSTRAP} ${BOOTSTRAP_TMPDIR} ${WORKDIR}/trusted.gpg.d ${WORKDIR}/sources.list.d"
do_bootstrap[depends] = "base-apt:do_cache isar-apt:do_cache_config"
@@ -206,16 +220,7 @@ do_bootstrap() {
# Cleanup mounts if fails
trap 'exit 1' INT HUP QUIT TERM ALRM USR1
- trap '[ -r "${WORKDIR}/mmtmpdir" ] && tmpdir=$(cat "${WORKDIR}/mmtmpdir") \
- && rm "${WORKDIR}/mmtmpdir"; \
- [ -d "$tmpdir" ] && mountpoint -q $tmpdir/$base_apt_tmp \
- && run_privileged umount $tmpdir/$base_apt_tmp; \
- [ -d "$tmpdir" ] && mountpoint -q $tmpdir/base-apt \
- && run_privileged umount $tmpdir/base-apt; \
- [ -d "$tmpdir" ] && run_privileged rm -rf --one-file-system $tmpdir; \
- [ -n "$base_apt_tmp" ] && mountpoint -q $base_apt_tmp \
- && run_privileged umount $base_apt_tmp \
- && rm -rf --one-file-system $base_apt_tmp' EXIT
+ trap 'bootstrap_cleanup' EXIT
# Create lock file so that it is owned by the user running the build (not root)
mkdir -p ${DEBDIR}
--
2.53.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/20260609123355.2368573-6-felix.moessbauer%40siemens.com.
next prev parent reply other threads:[~2026-06-09 12:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 12:33 [PATCH v5 00/17] add support to build isar unprivileged 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 01/17] refactor bootstrap: store rootfs tar with user permissions 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 02/17] deb-dl-dir: export without root privileges 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 03/17] download debs without locking 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 04/17] introduce wrappers for privileged execution 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` 'Felix Moessbauer' via isar-users [this message]
2026-06-09 12:33 ` [PATCH v5 06/17] rootfs: rework sstate caching of rootfs artifact 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 07/17] rootfs_generate_initramfs: rework deployment to avoid chowning 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 08/17] use bitbake function to generate mounting scripts 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 09/17] apt-fetcher: prepare for chroot specific fetching 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 10/17] add support for fully rootless builds 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 11/17] add helper script to clean artifacts in build dir 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 12/17] apt-fetcher: implement support for unshare backend 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 13/17] dpkg-source: implement multiarch " 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 14/17] use copy of sbom-chroot for sbom creation 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 15/17] add support for devshell on unshare backend 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 16/17] testsuite: add parameter to run tests in rootless mode 'Felix Moessbauer' via isar-users
2026-06-09 12:33 ` [PATCH v5 17/17] run-tests: add support for isar-rootless mode '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=20260609123355.2368573-6-felix.moessbauer@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.com \
--cc=jan.kiszka@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