Your message dated Sun, 28 Feb 2021 11:20:43 +0000
with message-id <e1lgk7v-00077w...@fasolo.debian.org>
and subject line Bug#983087: fixed in schroot 1.6.10-12
has caused the Debian Bug report #983087,
regarding cannot enter foreign arch schroot since qemu 1:5.2+dfsg-4
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.)
--
983087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sbuild
Version: 0.81.2
Severity: normal
Dear Maintainer,
My existing and newly created chroots with sbuild-createchroot
are missing target/usr/libexec/qemu-binfmt/. This lead me to
see the following symptoms when attempting to schroot in my
arm64 chroot overlay environment on top of amd64 machine:
$ sudo sbuild-createchroot --arch=arm64 sid target/
[...]
$ schroot -d / -c sid-arm64-sbuild
E: 15binfmt: touch: cannot touch
'/var/run/schroot/mount/sid-arm64-sbuild-542dde2d-092f-4135-a59e-9db33d518450/usr/libexec/qemu-binfmt/aarch64-binfmt-P':
No such file or directory
E: 15binfmt: touch: cannot touch
'/var/run/schroot/mount/sid-arm64-sbuild-542dde2d-092f-4135-a59e-9db33d518450/usr/libexec/qemu-binfmt/aarch64-binfmt-P':
No such file or directory
E: sid-arm64-sbuild-542dde2d-092f-4135-a59e-9db33d518450: Chroot setup
failed: stage=setup-start
The chroot setup fails and I cannot use my build environment.
I could fix that issue by manually adding the missing directory:
$ sudo mkdir -p target/usr/libexec/qemu-binfmt
$ schroot -d / -c sid-arm64-sbuild
(sid-arm64-sbuild)$ echo ok
ok
It looks to me like this appears since qemu 1:5.2+dfsg-4: the
actual binfmt binary is now located below the directory
/usr/libexec/qemu-binfmt/. I see in the change log:
> * qemu-user: attempt to preserve argv[0] when run under binfmt
> (Closes: #970460)
> This changes the enterpreter name for all linux-user registered
> binfmts, so it potentially can break stuff. The actual binary
> being registered now is /usr/libexec/qemu-binfmt/foo-binfmt-P,
> which is a symlink to actual /usr/lib/qemu-foo[-static].
I am not too sure whether this is a bug in the sbuild package,
or something more relevant to plain debootstrap, a documentation
item perhaps, or just me missing a step on my end. Please feel
free to reassign as deemed the most appropriate.
Have a nice day, :)
Étienne.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-3-amd64 (SMP w/6 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages sbuild depends on:
ii adduser 3.118
ii libsbuild-perl 0.81.2
ii perl 5.32.1-2
Versions of packages sbuild recommends:
ii autopkgtest 5.16
ii debootstrap 1.0.123
ii schroot 1.6.10-11+b1
Versions of packages sbuild suggests:
pn deborphan <none>
ii e2fsprogs 1.46.1-1
ii kmod 28-1
ii wget 1.21-1+b1
-- no debconf information
--
Étienne Mollier <etienne.moll...@mailoo.org>
Fingerprint: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
Sent from /dev/pts/4, please excuse my verbosity.
--- End Message ---
--- Begin Message ---
Source: schroot
Source-Version: 1.6.10-12
Done: Michael Tokarev <m...@tls.msk.ru>
We believe that the bug you reported is fixed in the latest version of
schroot, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 983...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Michael Tokarev <m...@tls.msk.ru> (supplier of updated schroot package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sun, 28 Feb 2021 13:43:50 +0300
Source: schroot
Architecture: source
Version: 1.6.10-12
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packa...@qa.debian.org>
Changed-By: Michael Tokarev <m...@tls.msk.ru>
Closes: 983087
Changes:
schroot (1.6.10-12) unstable; urgency=medium
.
* QA upload.
* ensure the parent directory for binfmt-misc interpreter
for a foreign chroot exists before using it (Closes: #983087)
Checksums-Sha1:
68f8475f9f5688b144a987fdba5dddf53ae2c501 1851 schroot_1.6.10-12.dsc
f978aaa896affeb6ff61aaac806cce5cd7b87433 83636 schroot_1.6.10-12.debian.tar.xz
7285ac676498d899d2332ef8c5c9674681ef6b84 6147
schroot_1.6.10-12_source.buildinfo
Checksums-Sha256:
9e6721814bcc02e03f28ef6b14bb1f6a0e6c67727bce41b87d7c0c1ade89965f 1851
schroot_1.6.10-12.dsc
ec9e0bfddab722ed713d806959eff5002c61b04737c1500adebda9d044973da9 83636
schroot_1.6.10-12.debian.tar.xz
2b515eac78967d51cdfe7919b556a501ad240f188434f6cd49e9931f275df00f 6147
schroot_1.6.10-12_source.buildinfo
Files:
986893b9087e1d83f2802956f661573a 1851 admin optional schroot_1.6.10-12.dsc
7507db24124309b9864e0496ef0dea67 83636 admin optional
schroot_1.6.10-12.debian.tar.xz
7e657eb7f795eeb6a8bf7f6596e25a8c 6147 admin optional
schroot_1.6.10-12_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQFDBAEBCAAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAmA7d1MPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5ZNfcH/i7vggQD2OSHuSapW4GDfsiy08EhCtxYIfyI
VLlBhT4Y6+Wj9fHGDrmILoyk/ySkL0dA9mUpMQ5YcsCtnEkP5qyy8SsNreucMsAI
9UFDcWKXPdH4ytgfccADqe45fJQo+6jxu0xViuQZZRQZlZpzt0T3Kgo4Gd34vbrR
G7vT5wOwKlMMF2OA2L7qtH7ct9GByKl1TumNBY3fFgzKSJrpYyImAJXAg2C6MFvh
iZp0cqs6k1rZBJDaZgUJhlVAaqwuJoRx/8CaGjjU4Bpt9q5Im/xyW58VAgZQOUCP
saw2cJFpHnPGTpbiYhVfrpHorV5yDbtstlL+Bc9Sis4i/7SOeag=
=+3jx
-----END PGP SIGNATURE-----
--- End Message ---
