Reinhard Tartler <[EMAIL PROTECTED]> writes: > Yes, your patch indeed 'fixed' the problem, in the sense that > listmounts doesn't segfault any longer. Somehow, the UID got > truncated. I'm now echo'ing the $CHROOT_MOUNT_LOCATION, now a > typical invocation looks like this: > > [EMAIL PROTECTED]:/srv/scratch/packages/schroot >>> schroot -c feisty > I: [Chroot feisty-e697053d-6887-4745-a69c-f21257a88d60] Starte > Login-Shell: »/usr/bin/zsh« > > [EMAIL PROTECTED]:/srv/scratch/packages/schroot >>> id > uid=1000(siretart) gid=1000(siretart) > groups=4(adm),20(dialout),24(cdrom),25(floppy),29(audio),30(dip),44(video),46(plugdev),107(lpadmin),108(scanner),109(admin),121(backuppc),1000(siretart),1001(sbuild) > > [EMAIL PROTECTED]:/srv/scratch/packages/schroot >>> logout > calling do_umount all > with /var/lib/schroot/mount/feisty-e697053d-6887-4745-a69c-f21257a88d60 > E: Failed to find > '/var/lib/schroot/mount/feisty-e697053d-6887-4745-a69c-f21257a88d60': No > such file or directory > > I'm still a bit puzzled why that directory doesn't exit. > > If you don't mind, I'd like to upload this fix as 1.0.4-1ubuntu1 to > feisty. When -2 hits unstable, I can request to overwrite the ubuntu > package. (The autosync is now disabled for feisty anyway)
That's fine with me. However, the patch isn't fixing the underlying problem. If you do find why the directory doesn't exist, please do let me know! Running schroot with "--debug=notice" should tell you what the path was when the chroot was created, in case it differs for some reason. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/ `- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
pgpygzapdxFRo.pgp
Description: PGP signature
