[buildd-tools-devel] Bug#609932: Bug#609932: sbuild now runs apt-get update automatically while building

[Cyril Brulebois]

Roger Leigh <rleigh at codelibre.net> (14/01/2011):
> The latter should also be coupled with an upgrade to ensure that the
> baseline state is up-to-date prior to any installations and
> removals.  This is why the default is also to do an upgrade.

So by default I get a chroot which gets upgraded behind my back? Great!

> We don't do a distupgrade by default; that's probably not
> sufficiently safe.

What would be the difference? I don't see any.

> With the use of cloned chroots, this is much less of an issue since
> we just delete the chroot.  But for non-cloned chroots, this means
> the chroot won't randomly break when apt-get can't cope, and most
> sbuild users are using non-cloned chroots.

I don't remember having apt-get break my chroot. I built *some*
packages though.

> This is still configurable if you wish to change it;

I know.

> it's just the default that's changed.

“just”. Again. And not documented AFAICT from a quick look for
“update” in the Debian changelog.

> Note that buildd always asks sbuild to update itself on every run
> already (--apt-update).

I don't care about buildd. I care about building packages in a chroot
I control. This means that if I build package A at a given time, and
some other host hits the approx caching proxy later, I can have a new
package version showing in my chroot's cache, and I can't build
package A anymore if I went offline in the meanwhile, while all
packages were available in my cache.

Not to mention extra differences which may appear due to newer
revisions of packages. Lower pertinence of debdiff and the like.
Looks like a pretty bad plan by default.

Also, = 0 seems to be the default, in sbuild.conf, which is also
misleading.

KiBi.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20110114/2116a9e7/attachment.pgp>