Ubuntu
signing-party package

caff: No public keys found with list-key

Bug #1650146 reported by Graham Inggs on 2016-12-15

This bug affects 1 person

	Status	Importance	Assigned to
signing-party (Debian)	Fix Released	Unknown	debbugs #837406
signing-party (Ubuntu)	Fix Released	Undecided	Unassigned
Yakkety	Fix Released	Undecided	Unassigned

Bug Description

[Impact]

Users are unable to import any public keys, making caff unusable.

[Test Case]

Replace 12345678 with someone's keyid.
With caff from signing-party 2.4-1:

$ caff 12345678
...
[WARN] gpg exited with value 2
[WARN] No public keys found with list-key 12345678 (note that caff uses its own keyring in /home/user/.caff/gnupghome)
[NOTICE] No keys to sign found

With caff from signing-party 2.4-1ubuntu1:

$ caff 12345678
...
[NOTICE] Fetching keys from a keyserver (this may take a while)...
[INFO] Key 12345678 imported

[Regression Potential]

Minimal, the patch reverts a single line to the previous working version.

See original description

Tags:

Graham Inggs (ginggs) on 2016-12-15

description:	updated
Changed in signing-party (Ubuntu):
status:	New → Fix Released

Bug Watch Updater (bug-watch-updater) on 2016-12-15

Changed in signing-party (Debian):
status:	Unknown → Fix Released

Revision history for this message

Graham Inggs (ginggs) wrote on 2016-12-16:

signing-party-sru.debdiff Edit (2.6 KiB, text/plain)

Debdiff of signing-party 2.4-1ubuntu1 uploaded to yakkety

description:	updated
Changed in signing-party (Ubuntu Yakkety):
status:	New → In Progress

Revision history for this message

Timo Aaltonen (tjaalton) wrote on 2016-12-16: Please test proposed package

Hello Graham, or anyone else affected,

Accepted signing-party into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/signing-party/2.4-1ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in signing-party (Ubuntu Yakkety):
status:	In Progress → Fix Committed
tags:	added: verification-needed

Revision history for this message

Stefano Rivera (stefanor) wrote on 2016-12-22:

SRU verified.

tags:

added: verification-done
removed: verification-needed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-01-04:

This bug was fixed in the package signing-party - 2.4-1ubuntu1

---------------
signing-party (2.4-1ubuntu1) yakkety; urgency=medium

  * SRU: backport the fix from 2.5-1 in zesty (LP: #1650146)
  * caff:
    + Fix regression (introduced in 2.4-1) skipping --recv-key when
      'keys-from-gnupg' isn't set. (Closes: #837406)

-- Graham Inggs <email address hidden> Fri, 16 Dec 2016 07:44:44 +0200

Changed in signing-party (Ubuntu Yakkety):
status:	Fix Committed → Fix Released

Revision history for this message

Brian Murray (brian-murray) wrote on 2017-01-04: Update Released

The verification of the Stable Release Update for signing-party has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.