[buildd-tools-devel] Bug#843137: Bug#843137: Bug#843137: sbuild: fails to deal with sid chroots (missing gpg)

[Johannes Schauer]

Hi,

Quoting Raphael Hertzog (2016-11-04 16:01:21)
> On Fri, 04 Nov 2016, Johannes Schauer wrote:
> >  2. the amount of effort required to cope with the changed situation in stretch
> >     (especially with respect to gpg) is huge. The existing patches are several
> >     hundred lines long. Help would indeed be appreciated to backport these
> >     patches. I fought with the gnupg situation for months to get it right and
> >     make things both forward and backward compatible. Lots of work is needed to
> >     do this right and test everything for a stable update. Unfortunately, this
> >     is time I currently don't have. I would be available though for guidance
> >     for anybody who's willing to give this a go.
> 
> An easy fix might be to modifiy sbuild-createchroot to install gpg and to
> document this requirement?

as I pointed in other mails in this bug report, if you *do* sign the internal
dummy repository, then you run into loads of other problems because of changes
in gnupg2. You could of course turn off signing but then you loose support for
building in chroots with Squeeze (where apt is too old). But then, even if you
decide that squeeze is too old and we don't want to support it anymore in the
current stable, you will run into issues because gnupg is for example needed to
import apt keys or for external repositories and then you are back at the
gnupg2 incompatibilities and at making sure to kill the gnupg agent or
otherwise your schroot session cannot end. See the bugreports and commits I
listed for a good overview of all the problems.

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/20161104/26e37add/attachment.sig>