From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: failure in installing xelb: ELPA signature verification failure
Date: Mon, 22 Apr 2024 08:57:57 -0400 [thread overview]
Message-ID: <jwvedaxmuhu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87zftl65pz.fsf@ucl.ac.uk
> Any suggestions on how to get around this or, better yet, get it fixed?
[ I had put an entry in my agenda to not forget to prepare for the
end-of-life of that key, but it got lost somehow in the mean time.
<sigh>. ]
I'll try and get this fixed ASAP.
[ but of course it had to come at a time where I'm a bit more busy
than usual. ]
> I guess the problem lies with ELPA?
Yes. AFAICT it affects all the packages whose release is "too old"
(hence the signature was made with this old key that has just expired).
Stefan
prev parent reply other threads:[~2024-04-22 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 10:40 failure in installing xelb: ELPA signature verification failure Eric S Fraga
2024-04-22 11:01 ` [SOLVED] " Eric S Fraga
2024-04-22 12:57 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvedaxmuhu.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).