[buildd-tools-devel] Bug#622735: Bug#622735: sbuild-createchroot fails to chown /build due to non-existing user & group

[Marc Dequènes (Duck)]

Coin,

Quoting Roger Leigh <rleigh at codelibre.net>:

> After completing the chroot creation, it's attempting to run
> 'apt-get update' and 'apt-get dist-upgrade' inside the chroot.
> While this fails, the chroot was created successfully, and you
> should be able to just run 'sbuild-update -ud wheezy' to update
> the chroot.

How would i know by myself? I had a very quick look at the code, and  
it didn't seem this trivial. When a tool outputs errors and says  
"Successfully set up" later, i really wonder if it can be trusted. I  
personally wouldn't upload anything generated in this chroot without  
rebuilding it or being sure the build environment is not screwed up.

I made a test build and it seems to work well, thanks.

Regards.

-- 
Marc Dequènes (Duck)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: PGP Digital Signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20110426/a5c437a1/attachment.pgp>