Package builder doesn't have my PPA's key
I uploaded a second package to my PPA and the build failed with
> Err:4 http://
> The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 2EEFC7E0186FE054
> Reading package lists...
> W: GPG error: http://
> E: The repository 'http://
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
- Assignee:
- No assignee Edit question
- Solved by:
- Etienne Dysli Metref
- Solved:
- Last query:
- Last reply: