[buildd-tools-devel] Bug#801798: please support building package without generating a gpg key for sbuild

[Helmut Grohne]

On Wed, Oct 14, 2015 at 06:53:56PM +0200, Helmut Grohne wrote:
> I would like to be able to use sbuild without having to create a gpg key
> for it. I understand that creating a key is required for operating as a
> buildd, but sbuild can be used in other scenarios as well. This bug is
> supposed to summarize a discussion I had with Johannes Schauer and
> Wookey.

Johannes Schauer asked me to clarify why this change is useful.
Currently, every setup of sbuild requires running sbuild-update
--keygen. This step is not done from a maintainer script and thus prone
to be forgotten. It also takes up to an hour to execute on virtual
machines that lack proper random sources.

I am attaching a basic and untested patch that implements the following
change: If sbuild fails to find the keys (for instance because
sbuild-update --keygen has not been run), it no longer errors out, but
adds "[ trusted=yes ]" to the generated sources.list. Thus existing
installations (with existing keys) will keep operating like they did and
new installations may skip the key generation step. The patch is meant
to sketch the desired behaviour.

Helmut
-------------- next part --------------
A non-text attachment was scrubbed...
Name: optional_keygen.patch
Type: text/x-diff
Size: 2176 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20151015/75e007d1/attachment-0001.patch>