Control: tag -1 + confirmed wontfix 25.07.2011 21:27, Emmet Hikory wrote: > Package: qemu-user-static > Version: 0.14.1+dfsg-3 > Severity: minor > Tags: patch > > When qemu-debootstrap is used to create an emulation chroot, it > copies a static library into the chroot for use by binfmt-misc. In > the event that the qemu-user-static package is updated, the static > libraries used in the chroots are not updated, so that the user > continues to use the old code, unless they manually track which > chroots they are using, and manually update them periodically. In > practice, this means that users will be continuously exposed to fixed > bugs over time unless they take tedious manual action. > > The attached patch is one way to address this issue: it will not > help in cases where users have chroots on transient storage (e.g. > removable drives) as the data file cleanup routine will remove those > entries if an upgrade is performed without the chroot at the same > pathname. It also introduces a --temporary-chroot argument to > qemu-debootstrap, which breaks argument compatibility with > debootstrap, although this does allow users to opt out of the chroot > creation logging, if they so wish.
We don't officially keep track of created chroots. Maybe we should, but I think it is better to do together with schroot or some other more widely used mechanism. And before upgrading the emulator in every chroot, maybe we should think about chroots currently running -- at least we shouldn't copy things over, it should be copytemp+rename to be atomic. But that's a minor thing, more important is to decide on what level we want to do that. For now I'm not convinced we shold udpate it at all, because we had and still have lots of bugs in user emulation, and some chroot work better with older versions, and you may try several versions to find out which works best or which one is broken and so on. Plus if we decice to do that, it should be well documented, and there should be a good, also documented, way to enable/disable updating on per-chroot basis, and maybe a separate command to update a given chroot. Marking as `wontfix' for now. Thanks, /mjt -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
