From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: kas-devel <kas-devel@googlegroups.com>,
isar-users <isar-users@googlegroups.com>,
Baurzhan Ismagulov <ibr@ilbers.de>
Subject: Re: [PATCH v2] Dockerfile.isar: Pull qemu-user-static from buster-backports
Date: Thu, 24 Sep 2020 16:50:56 +0200 [thread overview]
Message-ID: <481708e3-1080-d23c-6b5b-3bada01309ef@siemens.com> (raw)
In-Reply-To: <20200924135238.6d067e68@md1za8fc.ad001.siemens.net>
On 24.09.20 13:52, Henning Schild wrote:
> On Thu, 24 Sep 2020 13:12:35 +0200
> "[ext] Jan Kiszka" <jan.kiszka@siemens.com> wrote:
>
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> This is needed for running fakeroot from bullseye and sid which
>> triggers an unimplemented syscall with the current version.
>>
>> Due to changes in the new qemu-user-static package, the current
>> approach to activate its binfmt settings no longer works. Instead,
>> switch to an explicit call of the binfmt-support in init script.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> Changes in v2:
>> - fix binfmt activation
>> - drop unneeded (and effectless) listing of binfmt-support for
>> buster-backports
>>
>> OK, this was a nice one:
>> - debootstrap (of buster) creates the rootfs initially with a link of
>> $target/proc -> /proc
>> - later, it tries to umount $target/proc (and then sets up a proper
>> mounting via chroot) - I consider this a bug of debootstrap
>
> Did you report that bug or are planning to do something about it?
>
I've just replied to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968927 - that fixes
the issue, in fact.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2020-09-24 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 7:56 [PATCH] " Jan Kiszka
2020-09-24 9:14 ` Jan Kiszka
2020-09-24 11:12 ` [PATCH v2] " Jan Kiszka
2020-09-24 11:52 ` Henning Schild
2020-09-24 14:50 ` Jan Kiszka [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=481708e3-1080-d23c-6b5b-3bada01309ef@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=ibr@ilbers.de \
--cc=isar-users@googlegroups.com \
--cc=kas-devel@googlegroups.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