Public bug reported: 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 possibly Yakkety build chroots (as they have gnupg 2.x as well) ** Affects: sbuild (Ubuntu) Importance: Undecided Status: New ** Affects: sbuild (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #827315 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827315 ** Also affects: sbuild (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827315 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624046 Title: sbuild: Does not work with gnupg 2.x installed in the chroot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/1624046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
