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 15:19:51 +0100 [thread overview]
Message-ID: <CAAOASM9eCaFSc221-BG_EHwQz_eh+3R8-35=i4nCjdQ3SZMo_Q@mail.gmail.com> (raw)
In-Reply-To: <BD07FCB0-9C5B-4EF2-A109-A8104DB1B74C@scratch.space>
Putting
(package-initialize)
at the top didn't help either (and FWIW I copied and pasted the whole thing).
Also, I tried
$ wget https://elpa.gnu.org/packages/archive-contents{,.sig} && gpg2
--homedir ~/.emacs.d/elpa/gnupg/ --verify archive-contents.sig
... wget output omitted for brevity...
gpg: assuming signed data in 'archive-contents'
gpg: Signature made Sun 23 Jun 2019 10:10:02 AM BST using DSA key ID 7FBDEF9B
gpg: Good signature from "GNU ELPA Signing Agent
<elpasign@elpa.gnu.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: CA44 2C00 F917 74F1 7F59 D9B0 474F 0583 7FBD EF9B
So, it seems that gpg2 can verify the signature perfectly well.
Best,
Nicky
On Sun, 23 Jun 2019 at 12:50, VanL <van@scratch.space> wrote:
>
>
> > On 23 Jun 2019, at 14:50, Nicky Chorley <nick.chorley@gmail.com> wrote:
> >
> > (setq package-archives '(("gnu" . "https://elpa.gnu.org/packages/")))
>
> At the top of my .emacs is the following...
>
> --8<---------------cut here---------------start------------->8---
> (package-initialize)
> (setq package-archives '(("gnu" . "https://elpa.gnu.org/packages/")
> ("org" . "https://orgmode.org/elpa/")
> ("melpa" . "https://melpa.org/packages/")))
> --8<---------------cut here---------------end--------------->8---
>
>
next prev parent reply other threads:[~2019-06-23 14:19 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
2019-06-23 11:50 ` VanL
2019-06-23 14:19 ` Nicky Chorley [this message]
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='CAAOASM9eCaFSc221-BG_EHwQz_eh+3R8-35=i4nCjdQ3SZMo_Q@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.