[buildd-tools-devel] Bug#836940: Bug#836940: cowbuilder, sbuild: should behave identically in regard to default gnupg installation

[Thorsten Glaser]

Johannes Schauer dixit:

>> I think it is important that all maintainers can rely on the same default
>> chroot environment to test their packages before uploading to avoid possible
>> build failures.

The default chroot environment is one created with
debootstrap --variant=minbase, and then kept up to
date. Some chroot maintainers recreate it, or clean
up extra packages, more often than others; cowbuilder
--update runs apt-get autoremove, but that sometimes
doesn’t pick up packages that are part of minbase.

Either way, you can rely on whatever minbase is, and
nothing more. You can’t rely on that “nothing more”
either, which is why Build-Conflicts exist for those
rare cases that need it.

>In fact, to further minimize the number of packages installed into the build
>chroot, I have plans to even get rid of apt and its dependencies during the
>build and only leave build-essential, Essential:yes packages, the build
>dependencies and their transitive dependencies.

And libcowdancer and libeatmydata, I presume… or we
could inject them via /tmp.

Good idea! (Though please make this optional. For
slower architectures, adding and removing apt all
the time will suck; on m68k I even added debhelper
into the base chroot as 99% of all packages need
it anyway, as a speed hack.)

bye,
//mirabilos
-- 
Stéphane, I actually don’t block Googlemail, they’re just too utterly
stupid to successfully deliver to me (or anyone else using Greylisting
and not whitelisting their ranges). Same for a few other providers such
as Hotmail. Some spammers (Yahoo) I do block.