public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrey Grozin <grozin@woodpecker.gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] A problem with updating my key (again)
Date: Tue, 13 Jun 2023 17:00:16 +0000 (UTC)	[thread overview]
Message-ID: <4d69ec37-1c28-15ab-f476-d73a2c649fed@woodpecker.gentoo.org> (raw)

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) <grozin@gentoo.org>] [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) 
<grozin@gentoo.org>] [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


             reply	other threads:[~2023-06-13 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 17:00 Andrey Grozin [this message]
2023-06-13 17:21 ` [gentoo-dev] A problem with updating my key (again) Sam James
2023-06-15  2:09 ` Robin H. Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4d69ec37-1c28-15ab-f476-d73a2c649fed@woodpecker.gentoo.org \
    --to=grozin@woodpecker.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox