dangling/orphan key used by ppa build farm for team builds

Asked by Dick Balaska on 2018-07-09

Ahoy, newbie here,
I got everything set up and published my first package.
https://launchpad.net/~qtpovray/+archive/ubuntu/qtpovray
Locally, adding the ppa freaks about the signing key.
I failed to manually hack it in because I can't find it.
On the above page, if you click the "Signing key:" link, no key is found.
https://keyserver.ubuntu.com/pks/lookup?fingerprint=on&op=index&search=0xF9560028FD907C4B1DB27C8C6B47154730976367
Other team pages (i.e. notepadqq) get a key returned for their signing key.
I believe this is the crux of my problem.
I assume the key was created by launchpad when I created the PPA,
or I'm missing something else? I don't see any way to control *that* key.

Help?

Thanks.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Dick Balaska
Solved:
2018-07-19
Last query:
2018-07-19
Last reply:
Colin Watson (cjwatson) said : #1

This is the same problem as in https://answers.launchpad.net/launchpad/+question/670706. There's nothing you can do about it at the moment; it's probably a consequence of attempts to work around keyserver denial-of-service attacks, and we'll update you here when it's fixed.