On Wed, Mar 23, 2011 at 01:53:32PM +0100, Jakub Wilk wrote: > * Roger Leigh <[email protected]>, 2011-03-20, 21:41: > >Group sbuild is not in source-root-groups, and you're using a > >filesystem union which requires it. > > That's right. > > >This configuration was previously working, but not entirely correct. > >With 0.62.0, the privilege separation means the 'sbuild' user is used > >to run schroot, and this required group sbuild to be in root-groups > >and source-root-groups. > > Is it documented anywhere?
In the schroot documentation. When you use a source chroot, the allowed users/groups are taken from source-*. It's not mentioned in the sbuild documentation; it could be mentioned in the setup documentation. > >If you were running sbuild-update as a normal user in group > >sbuild, you would probably have already hit the issue. > > > >This is, I think, the problem you are seeing. Please let me know > >if this assessment is correct (or not). > > Yes, this is the case. > > I can't say I'm happy with current behaviour (I normally expect that > if I am root, I can do anything), but I guess I can live with it. > Feel free to close the bug. This is an additional issue: #619128 which will be fixed in the next upload. You'll then be able to continue to work as root. 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.
signature.asc
Description: Digital signature
