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

[Benjamin Drung]

Am Donnerstag, den 15.10.2015, 23:54 +0200 schrieb 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.

Adding cases complicates the code. So why not just change the behavior
to always use "[ trusted=yes ]"?
-- 
Benjamin Drung
System Developer
Debian & Ubuntu Developer

ProfitBricks GmbH
Greifswalder Str. 207
D - 10405 Berlin

Email: benjamin.drung at profitbricks.com
URL:  http://www.profitbricks.com

Sitz der Gesellschaft: Berlin.
Registergericht: Amtsgericht Charlottenburg, HRB 125506B.
Geschäftsführer: Andreas Gauger, Achim Weiss.