[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: can't connect to ELPA any more
From: |
Eli Zaretskii |
Subject: |
Re: can't connect to ELPA any more |
Date: |
Sun, 30 Jun 2024 13:30:56 +0300 |
> 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.