sbuild: Does not work with gnupg 2.x installed in the chroot

Bug #1624046 reported by Thomas Ward
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sbuild (Debian)
Fix Released
Unknown
sbuild (Ubuntu)
New
Undecided
Unassigned
Nominated for Trusty by Thomas Ward

Bug Description

This issue is one I've replicated on Trusty. This is already fixed in Yakkety based on the Debian bug's 'fixed' version and the fact it was merged into Yakkety already.

------

From the original Debian bug (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827315) I'm using, the core issue is this:

I recently accidentally upgraded gnupg in my experimental chroots to
version 2.x. This upgrade rendered the chroots unusable with sbuild,
attempting to build a package will fail with the following error:

gpg: /«BUILDDIR»/resolver-X436Nh/gpg/trustdb.gpg: trustdb created
gpg: Warning: not using 'Sbuild Signer' as default key: No secret key
gpg: all values passed to '--default-key' ignored
gpg: no default secret key: No secret key
gpg: signing failed: No secret key
Failed to sign dummy archive Release file.

------

This prevents sbuild from operating as it should for Debian Sid/Experimental build chroots, and also Yakkety build chroots (as they have gnupg 2.x as well)

Tags: gnupg2
Thomas Ward (teward)
description: updated
Changed in sbuild (Debian):
status: Unknown → Fix Released
tags: added: gnupg2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.