Bug#681884: Same problem with schroot 1.6.8-1

2014-04-05 Thread Erik de Castro Lopo
Erik de Castro Lopo wrote: Yes, I was using systemd on the machine where this is a problem and *not* using systemd on the machine where there is no problem. On the machine that was having the problem I un-installed systemd and the problem disappeared. This is definitely systemd related.

Bug#681884: Same problem with schroot 1.6.8-1

2014-04-05 Thread Erik de Castro Lopo
Erik de Castro Lopo wrote: Can anyone figure out from what we know so far if this is an schroot but or a systemd bug? If someone can give me a gentle nudge in the right direction I'm willing to invest some time on this because I really do need this bug fixed. Now I can't even re-produce

Bug#681884: [buildd-tools-devel] Bug#681884: Same problem with schroot 1.6.8-1

2014-04-05 Thread Roger Leigh
On Sat, Apr 05, 2014 at 09:25:33PM +1100, Erik de Castro Lopo wrote: Erik de Castro Lopo wrote: Can anyone figure out from what we know so far if this is an schroot but or a systemd bug? If someone can give me a gentle nudge in the right direction I'm willing to invest some time on

Bug#681884: [buildd-tools-devel] Bug#681884: Same problem with schroot 1.6.8-1

2014-03-14 Thread Erik de Castro Lopo
Roger Leigh wrote: Could this have something to do with the fact that I have /home as a separate ext4 partition and that the chroots are kept in under /home ? I'm not sure. I wouldn't think so, but I haven't tried it myself. Have you seen the other bug where systemd breaks bind

Bug#681884: [buildd-tools-devel] Bug#681884: Same problem with schroot 1.6.8-1

2014-03-13 Thread Roger Leigh
On Tue, Mar 11, 2014 at 11:21:29AM +1100, Erik de Castro Lopo wrote: Erik de Castro Lopo wrote: I see two mount points for every one mount point I expect. Eg: /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/home/chroot/sid64/tmp and

Bug#681884: Same problem with schroot 1.6.8-1

2014-03-10 Thread Erik de Castro Lopo
Erik de Castro Lopo wrote: I see two mount points for every one mount point I expect. Eg: /var/lib/schroot/mount/sid64-5249d6ca-d680-4570-8cc3-e9ade2fd42d1/home/chroot/sid64/tmp and /home/chroot/sid64/home/chroot/sid64/tmp The second one seems wrong. Could this have

Bug#681884: Same problem with schroot 1.6.8-1

2014-03-04 Thread Erik de Castro Lopo
Erik de Castro Lopo wrote: On the machine that displays this problem I have a amd64 Sid chroot called sid64. If I run it using 'schroot -c sid64' and immediately exit I get: If I just start the chroot and run mount I see: /dev/sda4 on

Bug#681884: Same problem with schroot 1.6.8-1

2014-03-03 Thread Erik de Castro Lopo
Hi all, I'm seeing the same problem with schroot 1.6.8-1 but only on one of the two machines I regularly use schroot on. On the machine that displays this problem I have a amd64 Sid chroot called sid64. If I run it using 'schroot -c sid64' and immediately exit I get: E: 10mount: umount: