On 2020-12-14 13:59, Michael Orlitzky wrote:
> I'm still getting this,
> 
>    $ git push --signed
>    ...
>    remote: 1C49724D229E93A2 [Michael Orlitzky <m...@gentoo.org>] [E]
>    expire:short Expiration date is too close, please renew (is 2020-12-26
>    23:30:47, less than 14 days)
>    remote: 1C49724D229E93A2:6F48D3DA05C2DADB [Michael Orlitzky
>    <m...@gentoo.org>] [E] expire:short Expiration date is too close,
>    please renew (is 2020-12-26 23:31:43, less than 14 days)
> 
> over a week after I've renewed my keys. The answer I get back from the 
> keyserver(s) looks OK:
> 
>    $ gpg --search-keys 0x6F48D3DA05C2DADB
>    gpg: data source: http://85.25.207.23:11371
>    (1)   Michael Orlitzky <m...@gentoo.org>
>          Michael Orlitzky <mich...@orlitzky.com>
>            4096 bit RSA key 0x1C49724D229E93A2, created: 2010-03-17,
>            expires: 2022-12-05
> 
> 
> Did I forget a step? How long should it take for infra to refresh?
You must pipe the "gpg --export" of your key to openpgp-key-upload when
connected to dev.gentoo.org like:

    gpg --export <your key> | ssh dev.gentoo.org 
/usr/local/bin/openpgp-key-upload

-- 
Cédric Krier

Attachment: signature.asc
Description: PGP signature

Reply via email to