Package builder doesn't have my PPA's key

Asked by Etienne Dysli Metref on 2020-01-31

I uploaded a second package to my PPA and the build failed with

> Err:4 http://ppa.launchpad.net/pkg-shibboleth/shibboleth-backports/ubuntu bionic InRelease
> The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2EEFC7E0186FE054
> Reading package lists...
> W: GPG error: http://ppa.launchpad.net/pkg-shibboleth/shibboleth-backports/ubuntu bionic InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2EEFC7E0186FE054
> E: The repository 'http://ppa.launchpad.net/pkg-shibboleth/shibboleth-backports/ubuntu bionic InRelease' is not signed.

build log: https://launchpadlibrarian.net/462921768/buildlog_ubuntu-bionic-amd64.xml-security-c_2.0.2-3~ubuntu18.04.1_BUILDING.txt.gz

Apparently the builder doesn't have the key for this PPA yet. How long does it take for new PPA's keys to propagate?
Should I wait longer or is it something to be manually fixed?

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Etienne Dysli Metref
Solved:
2020-02-03
Last query:
2020-02-03
Last reply:
2020-01-31
Colin Watson (cjwatson) said : #1

This looks like a transient issue fetching the key from the keyserver, which is sadly not quite as reliable as we might like. Have you tried simply retrying the failed build (which you can do from https://launchpad.net/~pkg-shibboleth/+archive/ubuntu/shibboleth-backports/+build/18637293).

Colin Watson (cjwatson) said : #2

(Sorry, that last sentence was meant to be a question, but I only noticed after hitting the submit button ...)

Hi Colin and thanks for your reply! I did not retry the build on Friday, but I now have and this time it succeeded. :)