Hi Josch, On Fri, Feb 19, 2016 at 09:07:46PM +0100, Johannes Schauer wrote: > Quoting Ryan Kavanagh (2016-02-19 18:56:32) > > rak@zeta:~$ sbuild-update -udr source:jessie-amd64 > > E: 15binfmt: update-binfmts: unable to open > > /var/run/schroot/mount/jessie-snap-a6a720c2-d20d-4251-b3a5-1e043da0e1e2/bin/sh: > > No such file or directory > > E: 20copyfiles: cp: cannot create regular file > > '/var/run/schroot/mount/jessie-snap-a6a720c2-d20d-4251-b3a5-1e043da0e1e2/etc/resolv.conf': > > No such file or directory > > E: jessie-snap-a6a720c2-d20d-4251-b3a5-1e043da0e1e2: Chroot setup failed: > > stage=setup-start > > Chroot setup failed > > Error setting up source:jessie-amd64 chroot > > Chroot setup failed at /usr/bin/sbuild-update line 170. > > this error looks strange. > > Can you tell me a way how I can reproduce the problem you have with > sbuild-update?
The above error is a classic case of PEBKAC. I accomplished it roughly as follows: mkfs.ext4 /dev/wd/jessie-chroot mkdir /tmp/jessie mount /dev/wd/jessie-chroot /tmp/jessie sbuild-createchroot jessie /tmp/wd-jessie-chroot http://httpredir.debian.org/debian umount /tmp/jessie ... delete /etc/schroot/schroot.d/* and add the appropriate LVM snapshot ... config entry to /etc/schroot/schroot.conf suild-update -udr source:jessie-amd64 which then caused a snapshot of /dev/wd/jessie-chroot to get mounted, which was empty (I fed the wrong path to sbuild-createchroot), and so sbuild-update obviously couldn't find bin/sh under it :) So, I suppose this should be considered a 'wishlist' bug, where sbuild-update should fail gracefully and umount stuff even on failure. Best wishes, Ryan -- |_)|_/ Ryan Kavanagh | Debian Developer | \| \ http://ryanak.ca/ | GPG Key 4A11C97A
signature.asc
Description: PGP signature
