Your message dated Sat, 1 Jun 2024 23:53:32 +0300
with message-id <a1807b41-7360-4657-a8a0-cc5a39a3e...@tls.msk.ru>
and subject line Re: Bug#1072370: qemu-user-static: No binfmt for armhf on
arm64 w/o 32-bit EL0 support
has caused the Debian Bug report #1072370,
regarding qemu-user-static: No binfmt for armhf on arm64 w/o 32-bit EL0 support
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1072370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-user-static
Version: 1:7.2+dfsg-7+deb12u5
Severity: normal
X-Debbugs-Cc: jrt...@debian.org
debian/binfmt-install assumes that if you're running on an architecture
in the same family as another then you can run it, and thus won't
install the binfmt file for it. This may in practice be generally true
for x86, where the vast majority of people are running a 64-bit kernel
on hardware that can do both, but it's increasingly not true for arm64
where even 32-bit support at EL0 is not available, such as on my system.
It's also almost certainly not going to be true for riscv64, where most
hardware doesn't support mixed-XLEN, but given there is no riscv32 port
for Debian in practice nobody's going to care about it.
As it stands in order to use qemu-arm-static for armhf on my arm64
system I have to go and grab the binfmt file from e.g. amd64, which is
not a good user experience. Probably something like a postinst script
that chooses whether to enable it based on your specific system config
is in order.
-- System Information:
Debian Release: 12.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: arm64 (aarch64)
Kernel: Linux 6.1.0-21-arm64 (SMP w/4 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
qemu-user-static depends on no packages.
Versions of packages qemu-user-static recommends:
ii systemd 252.22-1~deb12u1
qemu-user-static suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
01.06.2024 23:48, Jessica Clarke пишет:
Package: qemu-user-static
Version: 1:7.2+dfsg-7+deb12u5
Severity: normal
X-Debbugs-Cc: jrt...@debian.org
debian/binfmt-install assumes that if you're running on an architecture
in the same family as another then you can run it, and thus won't
install the binfmt file for it. This may in practice be generally true
for x86, where the vast majority of people are running a 64-bit kernel
on hardware that can do both, but it's increasingly not true for arm64
where even 32-bit support at EL0 is not available, such as on my system.
It's also almost certainly not going to be true for riscv64, where most
hardware doesn't support mixed-XLEN, but given there is no riscv32 port
for Debian in practice nobody's going to care about it.
As it stands in order to use qemu-arm-static for armhf on my arm64
system I have to go and grab the binfmt file from e.g. amd64, which is
not a good user experience. Probably something like a postinst script
that chooses whether to enable it based on your specific system config
is in order.
The binfmt is shipped in /usr/share/doc/qemu-user-static/qemu-arm.conf,
you can symlink it into /etc/binfmt.d/
Automatically enabling it is too risky, at least this must be checked
on every boot before enabling it.
/mjt
--- End Message ---
