From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Jean Louis <bugs@gnu.support>
Cc: Emacs Developers <emacs-devel@gnu.org>
Subject: Re: Failed to verify signature archive-contents.sig:
Date: Sat, 26 Feb 2022 15:35:59 -0500 [thread overview]
Message-ID: <jwv4k4l2wso.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <courier.00000000621A28B2.0000703B@stw1.rcdrun.com> (Jean Louis's message of "Sat, 26 Feb 2022 16:19:24 +0300")
Jean Louis [2022-02-26 16:19:24] wrote:
> Failed to verify signature archive-contents.sig:
> Bad signature from 066DAFCB81E42C40 GNU ELPA Signing Agent (2019) <elpasign@elpa.gnu.org>
> Command output:
> gpg: Signature made Fri 25 Feb 2022 01:05:04 AM EAT
> gpg: using RSA key C433554766D3DDC64221BFAA066DAFCB81E42C40
> gpg: BAD signature from "GNU ELPA Signing Agent (2019) <elpasign@elpa.gnu.org>" [unknown]
>
> after M-x package-list-packages
Do you still see that?
If it was transient, than I think it's sadly normal given the way the
scripts are written, there is a short time window between the update of
`archive-contents` and `archive-contents.sig`.
Stefan
next prev parent reply other threads:[~2022-02-26 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 13:19 Failed to verify signature archive-contents.sig: Jean Louis
2022-02-26 20:35 ` Stefan Monnier [this message]
2022-02-28 11:43 ` Jean Louis
2022-02-28 13:19 ` Stefan Monnier
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=jwv4k4l2wso.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).