public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Zhihang Wei <wzh@ilbers.de>
To: Felix Moessbauer <felix.moessbauer@siemens.com>,
	isar-users@googlegroups.com
Cc: jan.kiszka@siemens.com, Clara Kowalsky <clara.kowalsky@siemens.com>
Subject: Re: [PATCH 1/1] bootstrap: fix building from isar checkout with strict file permissions
Date: Tue, 15 Sep 2026 10:32:10 +0200	[thread overview]
Message-ID: <1aac300f-680d-4110-8438-8193d7cb5260@ilbers.de> (raw)
In-Reply-To: <20260911075941.1175172-1-felix.moessbauer@siemens.com>

Applied to next, thanks.

Zhihang

On 9/11/26 09:59, 'Felix Moessbauer' via isar-users wrote:
> When cloning the isar repository under a umask of 0007, the
> chroot-setup.sh file is not world readable. In unshare mode, the
> setup-hook of mmdebstrap runs in the unprivileged namespace under a
> different user, unable to read the chroot-setup.sh file. By that, the
> install <...> fails. For cases like this, mmdebstrap provides the upload
> helper, which internally handles the copy in of the file. As this does
> not provide a way to set the permissions (in contrast to install), we
> chmod the file afterwards.
>
> Fixes: 4fedb1ae ("add support for fully rootless builds")
> Reported-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
>   meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc | 3 ++-
>   1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc b/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
> index ee6eda3c..5d4ca1ef 100644
> --- a/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
> +++ b/meta/recipes-core/isar-mmdebstrap/isar-mmdebstrap.inc
> @@ -248,7 +248,8 @@ do_bootstrap() {
>                      --setup-hook='mkdir -p "$1/etc/apt/trusted.gpg.d"' \
>                      --setup-hook='sync-in "${WORKDIR}/trusted.gpg.d" /etc/apt/trusted.gpg.d' \
>                      --setup-hook='chown -R root:root "$1/etc/apt/trusted.gpg.d"' \
> -                   --setup-hook='install -v -m755 "${WORKDIR}/chroot-setup.sh" "$1/chroot-setup.sh"' \
> +                   --setup-hook='upload "${WORKDIR}/chroot-setup.sh" "/chroot-setup.sh"' \
> +                   --setup-hook='chmod a+rx "$1/chroot-setup.sh"' \
>                      --extract-hook="$extra_extract" \
>                      --essential-hook="$extra_essential" \
>                      --customize-hook="$extra_customize" \

-- 
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/1aac300f-680d-4110-8438-8193d7cb5260%40ilbers.de.

      reply	other threads:[~2026-09-15  8:32 UTC|newest]

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

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=1aac300f-680d-4110-8438-8193d7cb5260@ilbers.de \
    --to=wzh@ilbers.de \
    --cc=clara.kowalsky@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --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