| 1 |
On 2020-12-14 13:59, Michael Orlitzky wrote: |
| 2 |
> I'm still getting this, |
| 3 |
> |
| 4 |
> $ git push --signed |
| 5 |
> ... |
| 6 |
> remote: 1C49724D229E93A2 [Michael Orlitzky <mjo@g.o>] [E] |
| 7 |
> expire:short Expiration date is too close, please renew (is 2020-12-26 |
| 8 |
> 23:30:47, less than 14 days) |
| 9 |
> remote: 1C49724D229E93A2:6F48D3DA05C2DADB [Michael Orlitzky |
| 10 |
> <mjo@g.o>] [E] expire:short Expiration date is too close, |
| 11 |
> please renew (is 2020-12-26 23:31:43, less than 14 days) |
| 12 |
> |
| 13 |
> over a week after I've renewed my keys. The answer I get back from the |
| 14 |
> keyserver(s) looks OK: |
| 15 |
> |
| 16 |
> $ gpg --search-keys 0x6F48D3DA05C2DADB |
| 17 |
> gpg: data source: http://85.25.207.23:11371 |
| 18 |
> (1) Michael Orlitzky <mjo@g.o> |
| 19 |
> Michael Orlitzky <michael@××××××××.com> |
| 20 |
> 4096 bit RSA key 0x1C49724D229E93A2, created: 2010-03-17, |
| 21 |
> expires: 2022-12-05 |
| 22 |
> |
| 23 |
> |
| 24 |
> Did I forget a step? How long should it take for infra to refresh? |
| 25 |
|
| 26 |
You must pipe the "gpg --export" of your key to openpgp-key-upload when |
| 27 |
connected to dev.gentoo.org like: |
| 28 |
|
| 29 |
gpg --export <your key> | ssh dev.gentoo.org /usr/local/bin/openpgp-key-upload |
| 30 |
|
| 31 |
-- |
| 32 |
Cédric Krier |
Archives