not possible to build yakkety packages because of gpg changes

[Brian Murray]

I was trying to build update-manager in a yakkety sbuild chroot from a xenial system and encountered the following error:

Local sources
-------------

update-manager_16.10.5.dsc exists in .; copying to chroot

Check architectures
-------------------

Check dependencies
------------------

Merged Build-Depends: build-essential, fakeroot
Filtered Build-Depends: build-essential, fakeroot
dpkg-deb: building package 'sbuild-build-depends-core-dummy' in '/<<BUILDDIR>>/resolver-9lYerC/apt_archive/sbuild-build-depends-core-dummy.deb'.
gpg: /<<BUILDDIR>>/resolver-9lYerC/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.

I worked around the issue by installing the yakkety version of sbuild on my xenial system, but the fix should be backported.

[Marc Deslauriers (mdeslaur)]

I just hit this too.

[Christoph Korn (c-korn)]

The workaround from this comment works:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827315#24

Just uninstall gnupg and gnupg-l10n and install gnupg with "dpkg -i" from the latest xenial packages:
http://packages.ubuntu.com/xenial-updates/gnupg

[Rafael David Tinoco (rafaeldtinoco)]

Quick Tip: Inside the container, for devel purposes only, you can remove gnupg2 (and -agent, etc) and stay with v1 only. Creating a link /usr/bin/gpg1 to /usr/bin/gpg. This will allow debuild scripts to finish building packages.