[buildd-tools-devel] Bug#834898: propellor: problem with the new gpg2

[Johannes Schauer]

Hi,

Quoting Sean Whitton (2016-08-20 19:58:49)
> On Sat, Aug 20, 2016 at 06:56:59PM +0200, Johannes Schauer wrote:
> > You might want to open another bug against propellor to ask it not to generate
> > the key anymore if the propellor maintainers agree that that they don't want to
> > support squeeze chroots anymore.
> 
> We've got one open here: http://propellor.branchable.com/todo/updates_for_sbuild_0.70.0-1/

that page conflates two "issues" which roughly happened at the same time:

 1. gnupg2 went from experimental to unstable replacing gnupg1 as the default
implementation. This lead to incompatibilities between generated key pairs as
well as problems with remaining gpg-agent versions.

 2. apt stopped depending on gnupg. This meant that gpg wasn't available
anymore in the chroot and thus, users who still wanted to do signing had to
install it manually or disable signing.

So in fact, sbuild never ever installed gnupg into the chroot. It just so
happened that äround the time that sbuild 0.70.0 was released, apt stopped
depending on it in unstable and thus there is no gnupg anymore in Debian
unstable chroots. If you use sbuild to create a Debian jessie chroot then you
will see that it will contain gnupg as expected. This is not a property of
sbuild. Sbuild never did install gnupg into the chroot explicitly and thus
never stopped doing so either.

Thanks!

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