public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'MOESSBAUER, Felix' via isar-users" <isar-users@googlegroups.com>
To: Ulrich Teichert <ulrich.teichert@ebs-group.io>,
	isar-users <isar-users@googlegroups.com>,
	"Hombourger, Cedric" <cedric.hombourger@siemens.com>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: Recent bubblewrap security upgrade causing a build failure
Date: Fri, 28 Aug 2026 13:07:09 +0000	[thread overview]
Message-ID: <64b5d7ff601632bff533f1407e3e2aa13b010208.camel@siemens.com> (raw)
In-Reply-To: <7f7d4378-0c04-4b57-8af9-428725213c53n@googlegroups.com>

On Fri, 2026-08-28 at 05:23 -0700, 'Ulrich Teichert' via isar-users
wrote:
> Hi,
> 
> I just hit a build failure like:
> 
> ...
> | DEBUG: Executing shell function rootfs_install_pkgs_download
> | bwrap: Can't mount on symlink destination /bin
> | WARNING: exit code 1 from a shell command.
> | DEBUG: Executing shell function rootfs_do_umounts
> ...
> 
> That's caused by the security upgrade from bubblewrap 0.11.0 to 0.12.0,
> which at least Debian has active right now. To get my build going again,
> downgrading to 0.11.0 was enough. Of course, that doesn't help in the
> long run, but it saved my friday afternoon....

Thanks for reporting and the root cause analysis. Luckily the just
released kas 5.5 has bubblewrap 0.11.0-2+deb13u1, hence is not
affected.

But fixing this is probably not easy :/ Maybe Cedric can have a look,
as he wrote the corresponding logic.

Best regards,
Felix

> 
> HTH,
> Uli
> -- 
> 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/7f7d4378-0c04-4b57-8af9-428725213c53n%40googlegroups.com.

-- 
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/64b5d7ff601632bff533f1407e3e2aa13b010208.camel%40siemens.com.

  reply	other threads:[~2026-08-28 13:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28 12:23 'Ulrich Teichert' via isar-users
2026-08-28 13:07 ` 'MOESSBAUER, Felix' via isar-users [this message]
2026-08-28 15:53   ` 'Florian Bezdeka' via isar-users
2026-08-31  8:19     ` 'MOESSBAUER, Felix' 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=64b5d7ff601632bff533f1407e3e2aa13b010208.camel@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=felix.moessbauer@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --cc=ulrich.teichert@ebs-group.io \
    /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