From: Philip Kaludercic <philipk@posteo.net>
To: Okamsn <okamsn@protonmail.com>
Cc: 62230@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#62230: File "elpa-packages.eld" not signed, unlike file "archive-contents"
Date: Fri, 17 Mar 2023 08:24:48 +0000 [thread overview]
Message-ID: <87pm97lr8v.fsf@posteo.net> (raw)
In-Reply-To: <b8651f56-f659-49b9-a209-193a54260d5a@protonmail.com> (okamsn@protonmail.com's message of "Fri, 17 Mar 2023 00:16:30 +0000")
Okamsn <okamsn@protonmail.com> writes:
> Hello,
Hi,
> I have `package-check-signature` set to `all`. When I run the command
> `package-vc-install`, it tries to download the file "elpa-package.eld"
> from the archive. However, this file is not signed, so the download fails.
>
> When I disable the checking of signatures, the download succeeds.
I assume you have configured `package-check-signature' or something like
that? Because I don't appear to have any issues fetching the file.
> It is possible to sign this file with the GNU ELPA key, just like the
> file "archive-contents", which downloads successfully?
It should be, but I actually don't know how it is generated or at least
I am missing something in elpa-admin.el. I have Cc'ed Stefan who should
know.
> Thank you.
--
Philip Kaludercic
next prev parent reply other threads:[~2023-03-17 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 0:16 bug#62230: File "elpa-packages.eld" not signed, unlike file "archive-contents" Okamsn via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-17 8:24 ` Philip Kaludercic [this message]
2023-03-18 13:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 17:14 ` Okamsn via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18 17:28 ` Philip Kaludercic
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=87pm97lr8v.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=62230@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=okamsn@protonmail.com \
/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).