Hi *,
My key was going to expire soon. So, as usual, I have prolonged it for the
next year (several days ago). I've sent it to the Gentoo keyserver. I've
checked that the fingerpring of my key in LDAP coinsides with the
fingerprint I see locally.
Today I've tried to bump dev-lisp/sbcl to 2.3.5. But I got
remote: *** None of your keys comply with GLEP 63.
remote: Please update the keys into conformance if you wish to
continue
remote: using them. If not, please remove unused keys from LDAP.
remote: FATAL: VREF/proj-gentoo-02-gpg: helper program exit status 256
remote: 53D4ABFA88DD61C4 [Andrey Grozin (science) <[email protected]>] [E]
expire:short Expiration date is too close, please renew (is 2023-06-17
15:32:53, less than 14 days)
remote: 53D4ABFA88DD61C4:3AFFCE974D34BD8C [Andrey Grozin (science)
<[email protected]>] [E] expire:short Expiration date is too close, please
renew (is 2023-06-17 15:34:59, less than 14 days)
remote: error: hook declined to update refs/heads/master
To git.gentoo.org:repo/gentoo.git
! [remote rejected] master -> master (hook declined)
error: failed to push some refs to 'git.gentoo.org:repo/gentoo.git'
It seems that the remote git has ignored the fact that my key has been
prolonged about 3 days ago. One year ago I had the same situation. Is
there any reliable way to inform this git hook about the prolongation of
my key?
Every year the same problem :-(
Andrey
