[buildd-tools-devel] Bug#831462: Bug#831462: sbuild: requires gpg in chroot but does not install it

[Christian Hofstaedtler]

Hi,

* Johannes Schauer <josch at debian.org> [160717 11:28]:
> Hi,
> 
> Quoting Christian Hofstaedtler (2016-07-16 14:38:17)
> > recently apt has stopped depending on gnupg; as such it is not installed any
> > more in the chroot created by sbuild-createchroot.
> > 
> > But then at build time, sbuild wants gpg to create the APT archive and
> > aborts.
> 
> on the other hand... having thought about this for a bit longer, maybe a better
> solution than increasing the size of the list of manual "build essential"
> packages, this would be a good time to get rid of gnupg inside the chroot. The
> only reason gnupg support still exists is for old-old-stable (squeeze) chroots.
> I do not see another reason why one would want to sign the internal repository.
[...]
> What do you think?

Alright, if this is only for legacy reasons, then adding gnupg to
the installed-packages list makes no sense whatsoever.

Maybe put signing behind a (default off) config variable, instead of automatically
doing it when /var/lib/sbuild/apt-keys exists? This way, upgrades
would receive the new behaviour by default, and users building for
squeeze can flip it back on (maybe with an 'if dist eq "squeeze"').

Thanks!
-- 
 ,''`.  Christian Hofstaedtler <zeha at debian.org>
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-