Your message dated Sun, 29 May 2022 20:45:31 +0200 with message-id <1653849...@msgid.manchmal.in-ulm.de> and subject line Re: Bug#984768: schroot: fails chrooting in qemu-debootstrap rootfs has caused the Debian Bug report #984768, regarding schroot: fails chrooting in qemu-debootstrap rootfs 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.) -- 984768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: schroot Version: 1.6.10-11+b1 Severity: normal X-Debbugs-Cc: carsanbu+deb...@gmail.com Dear Maintainer, I've found this problem when I upgraded Debian, previously it worked correctly in my system. These are the steps to reproduce: qemu-debootstrap --arch=armhf bullseye bullseye-armhf http://ftp.debian.org/debian/ echo "[bullseye-armhf] description=Debian Bullseye directory=$(pwd)/bullseye-armhf users=$(whoami) type=directory" | tee /etc/schroot/chroot.d/bullseye-armhf schroot -c bullseye-armhf The output of this command is an error like this one: E: 15binfmt: touch: cannot touch '/var/run/schroot/mount/bullseye-armhf-dev-cce33164-30dc-4e03-85d7-ec441246e808/usr/libexec/qemu-binfmt/arm-binfmt-P': No such file or directory E: 15binfmt: touch: cannot touch '/var/run/schroot/mount/bullseye-armhf-dev-cce33164-30dc-4e03-85d7-ec441246e808/usr/libexec/qemu-binfmt/arm-binfmt-P': No such file or directory E: bullseye-armhf-dev-cce33164-30dc-4e03-85d7-ec441246e808: Chroot setup failed: stage=setup-start I've expect to chroot like in the past but I'm unable because in my rootfs there are not /usr/libexec/qemu-binfmt/arm-binfmt-P Best regards, Carlos SanmartĂn -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/4 CPU threads) Locale: LANG=C, 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 schroot depends on: ii libboost-filesystem1.74.0 1.74.0-8 ii libboost-iostreams1.74.0 1.74.0-8 ii libboost-program-options1.74.0 1.74.0-8 ii libc6 2.31-9 ii libgcc-s1 10.2.1-6 ii libpam0g 1.4.0-4 ii libstdc++6 10.2.1-6 ii libuuid1 2.36.1-7 ii lsb-base 11.1.0 ii schroot-common 1.6.10-11 schroot recommends no packages. Versions of packages schroot suggests: pn aufs-tools | unionfs-fuse <none> pn btrfs-progs <none> ii debootstrap 1.0.123 pn lvm2 <none> ii qemu-user-static 1:5.2+dfsg-6 pn zfsutils-linux <none> -- no debconf information
--- End Message ---
--- Begin Message ---Control: fixed 984768 1.6.10-12 Carlos SanmartĂn wrote... > I've found this problem when I upgraded Debian, previously it > worked correctly in my system. Seems this has been fixed in the meantime. I could reproduced this with your version 1.6.10-11+b1, but later the problem was gone. (For the interested, it might be necessary to re-recreate a chroot to verify this.) Regards, Christophsignature.asc
Description: PGP signature
--- End Message ---