Launchpad itself

builds failing because of "missing public key"

Asked by Steven Hillis

My builds are failing because the build server thinks my ppa has a missing public key.

Err:1 http://ppa.launchpad.net/compdrclovis/squid/ubuntu bionic InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2622B09DBB347901
Reading package lists...
W: GPG error: http://ppa.launchpad.net/compdrclovis/squid/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2622B09DBB347901
E: The repository 'http://ppa.launchpad.net/compdrclovis/squid/ubuntu bionic InRelease' is not signed.

I can load the ppa on systems without any issues, no errors about keys as of yesterday afternoon.

How long does it take for the build servers to update the keys? Is this an issue that needs to be fixed, or do I just need to wait a couple of days before trying to build things that rely on my own packages?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Colin Watson
Solved:
Last query:
Last reply:
Revision history for this message
Best Colin Watson (cjwatson) said : 		#1

It's not about how long it takes for the build servers to update the keys, but rather whether the keyserver is being reliable when the build manager tries to dispatch the builds. Unfortunately our keyservers have been somewhat unreliable lately ...

We will probably eventually rearrange things so that we store this kind of key in our database rather than relying on being able to get it back from the keyservers. In the meantime it's worth retrying occasionally, though I don't have a specific schedule.

Revision history for this message
Steven Hillis (compdrclovis) said : 		#2

Thanks.

A quick search before posting showed a few other people with this problem in the last year or so, but it was always a "marked as fixed" thing in those, so I assumed it was a temporary problem that cropped up occasionally and needed to be poked, like a service restart or something.

I'll try again in a bit then.

Revision history for this message
Steven Hillis (compdrclovis) said : 		#3

Thanks Colin Watson, that solved my question.