On Sat, Jun 16, 2012 at 05:19:59PM -0700, Vagrant Cascadian wrote: > On Sun, Jun 17, 2012 at 12:29:02AM +0200, Julian Andres Klode wrote: > > On Sat, Jun 16, 2012 at 11:13:03PM +0100, Roger Leigh wrote: > > > On Sat, Jun 16, 2012 at 02:57:26PM -0700, Vagrant Cascadian wrote: > > It turns out that mount has changed behavior recently (but man-pages > > document > > the one that worked until now). Replacing > > mount -o remount,ro "$dst" > > by > > mount -o remount,ro,bind "$dst" > > fixes this. A bug report against mount seems to be a good > > idea. > > I can confirm that that fixes it. > > > > The best solution in my opinion would be to make qemu-user-static > > multi-arch and add the native architecture to the chroot, and then > > install qemu-user-static for the native architecture inside the > > chroot. > > I have mixed feelings on this approach... it adds some overhead to the chroot > to support foreign architectures in apt and installing the whole of > qemu-user-static, instead of dynamically including the binary when neeeded.
It seems like it should be patched to work with the bind mounts (as above), or removed, as currently it breaks the ability to install a foreign-architecture qemu-user-static in the chroot manually, so neither approach works. :( live well, vagrant -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
