15.05.2022 09:06, Johannes Schauer Marin Rodrigues wrote:
...
Hello!
Thank you very much for this excellent bug report!
From the output above it is quite clear that the upgrade of
qemu-user-static from 1:7.0+dfsg-2+b1 to 1:7.0+dfsg-3 is the culprit.
Looking at d/changelog indeed reveals some changes to qemu-user-static
between these versions.
Here's the change which went into -3:
* d/binfmt-install: also generate binfmt.d/ entries for systemd
* d/control: use systemd as preferred alternative to binfmt-support
hopefully Closes: #789011 (Minimal dependencies to register binfmt)
Closes: #985889 (make binfmt setup configurable)
Basically I switched from binfmt-misc to systemd for binfmt registration,
or, actually, made the two coexist.
I will take a look at this hopefully tomorrow (I don't have access to my
usual test systems right now).
Meanwhile can you please try moving qemu bits away from /usr/lib/binfmt.d/
(this particular architecture should be enough), and see if that helps?
I don't know what's needed for binfmt-support to re-register its fmt
though, - a reboot should help but there is definitely a shorter way.
Speaking of mmdebstrap: why does it try to "fall back"? Did it try this
before, or is it intentional? The thing is that today, qemu-user-static
is transparent (or should be anyway), there's no need to run it explicitly,
it is done the binfmt-misc way so *bootstrap should not notice the arch
it is installing is foreign. It is okay if mmdebstrap does that since
historic times when this transparency didn't work, and it is not okay
if it expects such transparency now but it doesn't work.
Thanks,
/mjt
