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

Johannes Schauer josch at debian.org
Thu Sep 8 05:40:06 UTC 2016


Hi,

Quoting Thorsten Glaser (2016-09-07 22:53:37)
> Markus Koschany dixit:
> 
> >I have just created a new cowbuilder base chroot with
> >
> >sudo DIST=sid ARCH=amd64 cowbuilder --create
> >
> >and this command still installs gnupg. I don't know what I'm currently
> >missing
> 
> --variant=minbase or --variant=buildd (minbase+build-essential)

as we are talking about testing packages in the most minimal environment
possible it must be noted that debootstrap --variant=minbase or
--variant=buildd does not only install Essential:yes or Essential:yes with
build-essential, respectively, (and their transitive dependencies of course)
but also Priority:required packages like lsb-base or tzdata which are not
depended upon by any Essential:yes package.

Thus, with the current situation, there could exist many source packages that
should explicitly build-depend on Priority:required packages but don't and were
never found so far because all build chroots created by debootstrap include
these packages already.

Maybe a bug against debootstrap is in order that adds a new variant allowing it
to create a more minimal chroot?

Personally, I so far used multistrap to create my chroots, which doesn't suffer
from this problem.

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20160908/1fd6c81b/attachment-0001.sig>


More information about the Buildd-tools-devel mailing list