Launchpad itself

Error when uploading signed CoC: (7, 9, 'No public key')

Asked by Pablo Hoffman

I'm getting the following error when uploading my signed CoC in https://launchpad.net/codeofconduct/1.1/+sign

(7, 9, 'No public key') error

I've been re-trying since yesterday, in case there could be some delays involved. I know there are several tickets around about this problem, but none of them have been of help.

Any idea?.

My user: https://launchpad.net/~pablohoffman
My key: http://keyserver.ubuntu.com:11371/pks/lookup?search=0x5BEE3CAF18F8A7264E517421195C4B0DD2E7F7B6&op=index

I can paste the signed CoC here if it can help you for debugging, just let me know.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Pablo Hoffman
Solved:
Last query:
Last reply:
Revision history for this message
Pablo Hoffman (pablohoffman) said : 		#1

I made it work, but I had to create a new key from scratch. I would certainly have preferred to use my already existing OpenPGP key, but there seems to be a bug that prevents that.

Revision history for this message
Brad Crittenden (bac) said : 		#2

Pablo had you uploaded your old GPG key to Launchpad? Just having it on the keyserver is not enough.

Revision history for this message
Pablo Hoffman (pablohoffman) said : 		#3

I did run "gpg --keyserver keyserver.ubuntu.com --send-keys" with the old key, just like with the new one (which worked).

Revision history for this message
Brad Crittenden (bac) said : 		#4

Yes but did you go to https://launchpad.net/people/+me/+editpgpkeys and insert the fingerprint?

Revision history for this message
Pablo Hoffman (pablohoffman) said : 		#5

Yes, I also did that. But, after adding the new key (1024D/24C071FE), I disabled the old one (1024D/D2E7F7B6) which is now listed as disabled in https://launchpad.net/people/+me/+editpgpkeys

Anyway, I think I've found the problem now. It was related to the (somewhat) complex structure of my old OpenPGP key.

Also (and as a side problem) when I tried this page: http://keyserver.ubuntu.com:11371/pks/lookup?search=0x5BEE3CAF18F8A7264E517421195C4B0DD2E7F7B6&op=index

Some times it showed this:

pub 1024D/D2E7F7B6 2002-08-07

uid Pablo Hoffman (Personal key) <email address hidden>
sig sig3 D2E7F7B6 2005-04-21 __________ __________ [selfsig]

uid Pablo Hoffman (Work key) <email address hidden>
sig sig3 D2E7F7B6 2005-04-21 __________ __________ [selfsig]

sub 1024g/2573A76D 2002-08-07
sig sbind D2E7F7B6 2002-08-07 __________ __________ []

And sometimes (randomly) this (which is the most recent version of my key):

pub 1024D/D2E7F7B6 2002-08-07

uid Pablo Hoffman (Personal key) <email address hidden>
sig sig3 D2E7F7B6 2005-04-21 __________ __________ [selfsig]

uid Pablo Hoffman <email address hidden>
sig sig3 D2E7F7B6 2009-09-17 __________ __________ [selfsig]

uid Pablo Hoffman (Work key) <email address hidden>
sig sig3 D2E7F7B6 2005-04-21 __________ __________ [selfsig]

sub 1024g/2573A76D 2002-08-07
sig sbind D2E7F7B6 2002-08-07 __________ __________ []

sub 4096R/0AD95B80 2009-09-17
sig sbind D2E7F7B6 2009-09-17 __________ __________ []

I was using the 0AD95B80 key for signing before, and I think Launchpad expects me to use the main-key (D2E7F7B6) for signing, which is what I do with the new one (I sign with 24C071FE).

Not sure if this should be considered a Launchpad bug or not, but at least we've found the problem.

Thanks for your help Brad!