From: Anton Mikanovich <amikan@ilbers.de>
To: Florian Bezdeka <florian.bezdeka@siemens.com>,
isar-users@googlegroups.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>, Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH] meta: Drop lazy and recursive unmounts
Date: Fri, 6 Sep 2024 17:34:07 +0300 [thread overview]
Message-ID: <deeeb768-e3c4-43a4-a132-51fb51643f0b@ilbers.de> (raw)
In-Reply-To: <8086840c9b7bcf8dbcd6d3141d493c87f9e6d5c8.camel@siemens.com>
29/08/2024 15:26, Florian Bezdeka wrote:
> I think this is the relevant line from "mount":
>
> tmpfs on /builds/<project>/build/tmp/work/debian-bookworm-amd64/sbuild-
> chroot-target/1.0-r0/rootfs/dev type tmpfs
> (rw,nosuid,size=65536k,mode=755,inode64)
>
> Florian
So it is sbuild who should manage mount in this rootfs. Not sure how
this patch
influence on internal sbuild mount/unmount logic. But sbuild shouldn't
left any
mounts without any errors. Do you have any packages failed to be built?
Are there any lost schroot sessions running before external rm you have
issue
with? This can be checked with 'schroot -la' command.
You can also try to add some verbose to sbuild with following change:
diff --git a/meta/classes/dpkg.bbclass b/meta/classes/dpkg.bbclass
index bcc3f828..b54e3ab9 100644
--- a/meta/classes/dpkg.bbclass
+++ b/meta/classes/dpkg.bbclass
@@ -113,6 +113,8 @@ dpkg_runbuild() {
DSC_FILE=$(find ${WORKDIR} -maxdepth 1 -name
"${DEBIAN_SOURCE}_*.dsc" -print)
sbuild -A -n -c ${SBUILD_CHROOT} \
+ -D \
+ --chroot-setup-commands="mount" \
--host=${PACKAGE_ARCH} --build=${BUILD_ARCH} ${profiles} \
--no-run-lintian --no-run-piuparts --no-run-autopkgtest
--resolve-alternatives \
--bd-uninstallable-explainer=apt \
This will be very helpfull to get some build logs from your setup.
--
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 on the web visit https://groups.google.com/d/msgid/isar-users/deeeb768-e3c4-43a4-a132-51fb51643f0b%40ilbers.de.
next prev parent reply other threads:[~2024-09-06 14:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 10:41 Anton Mikanovich
2024-06-26 6:31 ` Uladzimir Bely
2024-08-28 13:05 ` 'Florian Bezdeka' via isar-users
2024-08-29 9:26 ` Anton Mikanovich
2024-08-29 12:26 ` 'Florian Bezdeka' via isar-users
2024-09-06 14:34 ` Anton Mikanovich [this message]
2024-10-01 11:59 ` 'Florian Bezdeka' via isar-users
2024-10-01 12:14 ` 'Jan Kiszka' via isar-users
2024-10-01 12:18 ` 'Florian Bezdeka' via isar-users
2024-10-01 12:28 ` 'Jan Kiszka' via isar-users
2024-10-03 14:37 ` Baurzhan Ismagulov
2024-10-04 7:28 ` 'Florian Bezdeka' via isar-users
2024-10-04 8:00 ` Uladzimir Bely
2024-10-04 8:16 ` 'Jan Kiszka' via isar-users
2024-10-10 4:33 ` 'Jan Kiszka' via isar-users
2024-10-10 9:43 ` Baurzhan Ismagulov
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=deeeb768-e3c4-43a4-a132-51fb51643f0b@ilbers.de \
--to=amikan@ilbers.de \
--cc=florian.bezdeka@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@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