not possible to build yakkety packages because of gpg changes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
sbuild (Debian) |
Fix Released
|
Unknown
|
|||
sbuild (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Trusty |
Triaged
|
High
|
Unassigned | ||
Xenial |
Triaged
|
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-
Check architectures
-------------------
Check dependencies
------------------
Merged Build-Depends: build-essential, fakeroot
Filtered Build-Depends: build-essential, fakeroot
dpkg-deb: building package 'sbuild-
gpg: /<<BUILDDIR>
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 |
tags: | added: gnupg2 |
Changed in sbuild (Ubuntu Trusty): | |
status: | New → Triaged |
importance: | Undecided → High |
I just hit this too.