From: Nicky Chorley <nick.chorley@gmail.com>
To: VanL <van@scratch.space>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent
Date: Sun, 23 Jun 2019 05:50:19 +0100 [thread overview]
Message-ID: <CAAOASM-mQ64v+VaNADUuz-akPpXnK-cUdH9u8c4tbJf4kZ26Rw@mail.gmail.com> (raw)
In-Reply-To: <AC6F51E8-9232-4488-8024-5F394A050CD9@scratch.space>
On Sat, 22 Jun 2019 at 14:04, VanL <van@scratch.space> wrote:
> May be you need to locate your gpg program and put it in .emacs like
>
> (setq epg-gpg-program "/usr/local/bin/gpg2")
>
> May be you need to update your gpg.
>
> It would be neat to have a thing that checklisted all your certificate handling components are working correctly.
>
> My be you could point eww to the https address for the packages and see if your emacs can get thru to there.>
>
The version of gpg2 on Slackware is quite old, so I tried the
following .emacs on Fedora 30 (which has a much newer gpg2) running
inside a Docker container
(setq epg-gpg-program "/usr/bin/gpg2")
(setq package-archives '(("gnu" . "https://elpa.gnu.org/packages/")))
but no joy.
Is there a way I can get Emacs to tell me how it's downloading the
file and how it's running gpg2 to verify it? I'd like to try the same
outside Emacs to see if I can reproduce the problem.
In any case, I found this bug:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35534, so maybe we just
have to wait and see what the maintainers find.
Best,
Nicky
next prev parent reply other threads:[~2019-06-23 4:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 7:26 Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent Nicky Chorley
2019-06-22 13:04 ` VanL
2019-06-23 4:50 ` Nicky Chorley [this message]
2019-06-23 11:50 ` VanL
2019-06-23 14:19 ` Nicky Chorley
2019-06-24 8:13 ` VanL
2019-06-24 19:00 ` Nicky Chorley
2019-06-25 10:26 ` VanL
2019-06-24 12:50 ` Stefan Monnier
2019-06-23 18:21 ` Jude DaShiell
2019-06-24 12:49 ` Stefan Monnier
2019-06-24 18:58 ` Nicky Chorley
2019-06-24 20:38 ` Jude DaShiell
2019-06-22 16:15 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2019-06-25 14:45 Nicky Chorley
2019-02-09 8:46 Nicky Chorley
2019-02-10 12:40 ` Robert Pluim
2019-02-10 15:05 ` Stefan Monnier
2019-03-09 6:52 ` Nicky Chorley
2019-03-09 7:57 ` Jude DaShiell
2019-03-09 20:15 ` Stefan Monnier
2019-03-09 20:34 ` Jude DaShiell
2019-06-13 7:25 ` Nicky Chorley
2019-06-13 12:23 ` Van L
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=CAAOASM-mQ64v+VaNADUuz-akPpXnK-cUdH9u8c4tbJf4kZ26Rw@mail.gmail.com \
--to=nick.chorley@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=van@scratch.space \
/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.