not possible to build yakkety packages because of gpg changes

Bug #1621269 reported by Brian Murray on 2016-09-07
48
This bug affects 8 people
Affects Status Importance Assigned to Milestone
sbuild (Debian)
Fix Released
Unknown
sbuild (Ubuntu)
Undecided
Unassigned
Trusty
High
Unassigned
Xenial
High
Unassigned

Bug Description

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.

tags: added: xenial
Changed in sbuild (Ubuntu):
status: New → Invalid
Changed in sbuild (Ubuntu Xenial):
importance: Undecided → High
status: New → Triaged
summary: - not possible to build yakkety packages
+ not possible to build yakkety packages because of gpg changes
Changed in sbuild (Debian):
status: Unknown → Fix Released
Marc Deslauriers (mdeslaur) wrote :

I just hit this too.

tags: added: gnupg2
Changed in sbuild (Ubuntu Trusty):
status: New → Triaged
importance: Undecided → High
Christoph Korn (c-korn) wrote :

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 (inaddy) wrote :

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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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