From: Nicky Chorley <nick.chorley@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent
Date: Sat, 9 Mar 2019 06:52:18 +0000 [thread overview]
Message-ID: <CAAOASM-jsii2of7TShXH2q636SON+d67g9QjSeUNHr46Jwa8=Q@mail.gmail.com> (raw)
In-Reply-To: <CAAOASM9RGWemHrtwG-QTMg0gjNh97A2N9d7RFo1O+ksnb3BZgw@mail.gmail.com>
I tried switching to HTTPS for the GNU ELPA repository as well, but
that didn't help either and I'm still getting the error. Again, just
clearing my .emacs.d doesn't help. Is there another cache somewhere
that I should try clearing, or does anyone have any other suggestions?
Best,
Nicky
On Sat, 9 Feb 2019 at 08:46, Nicky Chorley <nick.chorley@gmail.com> wrote:
>
> Hi all,
>
> I'm running Emacs 25.3.1 on Slackware Linux 14.2 and `M-x
> package-refresh-contents` is giving the following error:
>
> Failed to verify signature archive-contents.sig:
> Bad signature from 474F05837FBDEF9B GNU ELPA Signing Agent
> <elpasign@elpa.gnu.org>
> Command output:
> gpg: Signature made Fri 08 Feb 2019 10:15:04 PM GMT using DSA key ID 7FBDEF9B
> gpg: BAD signature from "GNU ELPA Signing Agent <elpasign@elpa.gnu.org>"
>
> I don't recall changing anything in my config recently. Just to see if
> that was causing a problem, I did remove my config (.emacs and
> .emacs.d), but the problem persisted.
>
> Any ideas about what's causing this?
>
> Thanks,
>
> Nicky Chorley
next prev parent reply other threads:[~2019-03-09 6:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 8:46 Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent Nicky Chorley
2019-02-10 12:40 ` Robert Pluim
2019-02-10 15:05 ` Stefan Monnier
2019-03-09 6:52 ` Nicky Chorley [this message]
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
2019-04-01 16:49 ` usenet qqk8
2019-04-01 22:03 ` usenet Emanuel Berg
-- strict thread matches above, loose matches on Subject: below --
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
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
2019-06-25 14:45 Nicky Chorley
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-jsii2of7TShXH2q636SON+d67g9QjSeUNHr46Jwa8=Q@mail.gmail.com' \
--to=nick.chorley@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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.