From: Daniel Mendler via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 72319@debbugs.gnu.org
Cc: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#72319: ELPA archive download fails with signature error during rebuild
Date: Sat, 27 Jul 2024 12:51:07 +0200 [thread overview]
Message-ID: <8734nvrtus.fsf@daniel-mendler.de> (raw)
The ELPA archive download fails during package archive rebuilding. The
rebuilding process on the ELPA server happens twice every day (e.g., in
the morning at 09:00 UTC or 11:00 local time in my time zone). As a
package maintainer I receive mails that new package releases have been
created at that time.
When I execute M-x package-upgrade-all shortly afterwards, approximately
in the time frame from 11:00 to 11:10, I observe the following failures:
Failed to download ‘gnu’ archive.
Failed to download ‘nongnu’ archive.
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 Fri 26 Jul 2024 11:10:06 AM CEST
gpg: using EDDSA key 0327BE68D64D9A1A66859F15645357D2883A0966
gpg: BAD signature from "GNU ELPA Signing Agent (2023) <elpasign@elpa.gnu.org>" [unknown]
I've already discussed with Stefan about this problem. The issue seems
to be that the archive-contents file is updated during the archive building
process, while the signature is only updated in the end. Ideally the
update of the archive-contents file should happen a little more
atomically: First build a new archive-contents file, sign it, and then
replace the old files as the final step.
reply other threads:[~2024-07-27 10:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8734nvrtus.fsf@daniel-mendler.de \
--to=bug-gnu-emacs@gnu.org \
--cc=72319@debbugs.gnu.org \
--cc=mail@daniel-mendler.de \
--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.
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).