> The error message you saw: > E: unstable-i386-sbuild-22146117-8358-467e-a857-9e8d4c79e747: Failed to lock > chroot: /var/lib/sbuild/unstable-i386.tar.gz: File is not owned by user root
> does not come from sbuild but from schroot. So if you want to know why schroot > needs it to be owned by the root user, you'd have to ask the schroot > maintainer. I do not know why. > The bug could nevertheless be in sbuild though because sbuild is the package > with the postinst maintainer script that changes the ownership. I now have to > figure out whether this chown call is actually useful or not. In the former > case, the wiki page would have to be adapted to not recommend this location. What I understand is that/var/lib/sbuild is the home directory of the sbuild user. So it seems to me right to have all files under this location readable and writable by the sbuild user. So myabe you are right the problem is with schroot which could lock something not owned by root. Nevertheless it is nice to let only the root user update the schroot. ... Frederic
