From: Brandon Invergo <brandon@invergo.net>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: 35414@debbugs.gnu.org
Subject: bug#35414: 26.2; ELPA packages signed with second, unknown key
Date: Wed, 24 Apr 2019 23:03:29 +0100 [thread overview]
Message-ID: <875zr36oy6.fsf@invergo.net> (raw)
In-Reply-To: <jwvsgu7p5ui.fsf-monnier+emacs@gnu.org>
Stefan Monnier writes:
>> I assume (without checking) that this is related to the key from
>> http://lists.gnu.org/r/emacs-diffs/2019-04/msg00546.html
>
> Hmm... Indeed: this new keyring contains two keys (the old 2014 key
> which will expire in September and a new key to replace it).
I see. Sorry, I only searched the bugs list but not the diffs list!
> Hmm... I just tried with Debian's Emacs-25.1 and with a new build from
> the `emacs-26` branch:
>
> emacs -Q --eval '(setq package-check-signature t)
> M-x package-list-packages RET
> M-x package-refresh-contents RET
>
> and didn't get any error.
I suppose it's worth asking (but apologies if I misunderstand what's
happening under the hood): did you perform this test with an empty
keyring (or just with what's available in Debian's Emacs-25.1
installation)? I suspect that you already have the new public key in
your keyring, so you wouldn't experience the problem.
> It's a brand new key that is now in etc/package-keyring.gpg in the
> `master` branch of Emacs, as well as in the `gnu-elpa-keyring-update`
> package in GNU ELPA.
>
> This is because the key 474F05837FBDEF9B is about to expire (it's
> really high time we start preparing for the new key).
OK, that should make things easy enough. Of course, I hadn't seen that
package because I was unable to update my archives!
Unfortunately, installing the package (after temporarily disabling sig
verification) doesn't solve the problem for me. Am I correct to assume
that the package should "just work" after installing (and restarting
Emacs)? Just for fun I tried manually running gnu-elpa-keyring-update,
which resulted in this this:
Debugger entered--Lisp error: (error "Can’t find the keyring.gpg file with the new keys")
signal(error ("Can’t find the keyring.gpg file with the new keys"))
error("Can't find the keyring.gpg file with the new keys")
gnu-elpa-keyring-update--keyring()
gnu-elpa-keyring-update()
eval((gnu-elpa-keyring-update) nil)
eval-expression((gnu-elpa-keyring-update) nil nil 127)
funcall-interactively(eval-expression (gnu-elpa-keyring-update) nil nil 127)
call-interactively(eval-expression nil nil)
command-execute(eval-expression)
gnu-elpa-keyring-update--keyring has the value
"etc/gnu-elpa-keyring.gpg", which doesn't exist relative to any relevant
paths that I can think of. The files in .emacs.d/elpa/gnupg haven't
been modified.
I looked at the ELPA git repo and saw that the keyring should be
distributed in the etc subdirectory of the package. So I tried manually
downloading the keyring from elpa.gnu.org via wget, however I got a 404
error (trying different reasonable URLs). I then manually downloaded it
from the ELPA git repository and put it in
.emacs.d/elpa/gnu-elpa-keyring-update-2019.0/etc et voila! Success.
So, I guess the "bug" at this point is that it would appear that the
keyring isn't properly installed with the keyring-update package. I
apologize for the original noise, since you obviously had already
considered and worked on a fix for the underlying problem.
Thanks for your help!
--
-brandon
next prev parent reply other threads:[~2019-04-24 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 12:56 bug#35414: 26.2; ELPA packages signed with second, unknown key Brandon Invergo
2019-04-24 16:08 ` Glenn Morris
2019-04-24 19:36 ` Stefan Monnier
2019-04-24 22:03 ` Brandon Invergo [this message]
2019-04-24 22:36 ` Stefan Monnier
2019-04-24 23:02 ` Stefan Monnier
2019-04-24 23:07 ` Glenn Morris
2019-04-25 6:23 ` Eli Zaretskii
2019-05-08 17:20 ` Stefan Monnier
2019-04-25 8:36 ` Brandon Invergo
2019-09-30 22:02 ` Stefan Kangas
2019-09-30 23:27 ` Stefan Monnier
2020-01-25 17:12 ` Stefan Kangas
2020-01-25 17:31 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875zr36oy6.fsf@invergo.net \
--to=brandon@invergo.net \
--cc=35414@debbugs.gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.