From: Eli Zaretskii <eliz@gnu.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: oub@mat.ucm.es, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: can't connect to ELPA any more
Date: Sun, 30 Jun 2024 13:30:56 +0300 [thread overview]
Message-ID: <86frsuhgdb.fsf@gnu.org> (raw)
In-Reply-To: <871q4en3hp.fsf@posteo.net> (message from Philip Kaludercic on Sun, 30 Jun 2024 10:12:34 +0000)
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: Uwe Brauer <oub@mat.ucm.es>, Stefan Monnier <monnier@iro.umontreal.ca>,
> emacs-devel@gnu.org
> Date: Sun, 30 Jun 2024 10:12:34 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > Here's what I get from package-list-packages in "emacs -Q" (in the
> > *Error* buffer):
> >
> > Failed to verify signature archive-contents.sig:
> > Bad signature from 645357D2883A0966 GNU ELPA Signing Agent (2023) <elpasign@elpa.gnu.org>
> > Command output:
> > gpg: Signature made 30/06/2024 12:10:02 Jerusalem Daylight Time
> > gpg: using EDDSA key 0327BE68D64D9A1A66859F15645357D2883A0966
> > gpg: BAD signature from "GNU ELPA Signing Agent (2023) <elpasign@elpa.gnu.org>" [unknown]
> >
> > Stefan, Philip: could you please look into this?
>
> I believe you can fix this by installing "gnu-elpa-keyring-update".
How come this is suddenly required? It's a nuisance to keep this
updated at all times. I think I'd rather disable signature
verification. Too bad.
next prev parent reply other threads:[~2024-06-30 10:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 8:47 can't connect to ELPA any more Uwe Brauer via Emacs development discussions.
2024-06-30 9:23 ` Eli Zaretskii
2024-06-30 10:12 ` Philip Kaludercic
2024-06-30 10:30 ` Uwe Brauer
2024-06-30 10:30 ` Eli Zaretskii [this message]
2024-07-01 1:32 ` Michael Heerdegen via Emacs development discussions.
2024-07-01 11:23 ` Eli Zaretskii
2024-07-03 22:07 ` Mekeor Melire
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=86frsuhgdb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=oub@mat.ucm.es \
--cc=philipk@posteo.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.