From: David Masterson <dsmasterson@gmail.com>
To: Zhengyi Fu <i@fuzy.me>
Cc: help-gnu-emacs@gnu.org
Subject: Re: HELP: problem with ELPA archive-contents.sig in list-packages ?
Date: Wed, 15 May 2024 21:45:18 -0700 [thread overview]
Message-ID: <LV8P223MB0920498B22A3E0DECB9BF951A2ED2@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87v83egz8n.fsf@DESKTOP-B1IG6IJ.> (Zhengyi Fu's message of "Thu, 16 May 2024 12:21:04 +0800")
Zhengyi Fu <i@fuzy.me> writes:
> David Masterson <dsmasterson@gmail.com> writes:
>
>> Let's try again...
>>
>> I am using Emacs 28.3 and have a problem with list-packages in the last
>> week or so. After starting emacs, I run list-packages. It appears to
>> be successful, but, after ~5 seconds, the following *Error* buffer pops
>> up:
>>
>> ================
>> Failed to verify signature archive-contents.sig:
>> No public key for 645357D2883A0966 created at 2024-05-15T14:05:06-0700 using EDDSA
>> Command output:
>> gpg: Signature made Wed May 15 14:05:06 2024 PDT
>> gpg: using EDDSA key 0327BE68D64D9A1A66859F15645357D2883A0966
>> gpg: Can't check signature: No public key
>> ================
>>
>> I cannot find archive-contents.sig on my system (I did find
>> archive-contents.signed in the .emacs.d/elpa/archive/elpa directory), so
>> I'm thinking this has to do with something on ELPA.
>>
>> Did something change that I missed? Any advice?
>
> I ran into the same problem today. My solution is to temporarily
> disabled signature checking by setting `package-check-signature' to nil
> and installing the `gnu-elpa-keyring-update'[1] package, which helps to
> update the public keys.
>
> Footnotes:
> [1] https://elpa.gnu.org/packages/gnu-elpa-keyring-update.html
>
Thanks, that seems to have worked.
--
David Masterson
prev parent reply other threads:[~2024-05-16 4:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-16 0:40 HELP: problem with ELPA archive-contents.sig in list-packages ? David Masterson
2024-05-16 4:21 ` Zhengyi Fu
[not found] ` <87v83egz8n.fsf@DESKTOP-B1IG6IJ.>
2024-05-16 4:45 ` David Masterson [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=LV8P223MB0920498B22A3E0DECB9BF951A2ED2@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM \
--to=dsmasterson@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=i@fuzy.me \
/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).