Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent

[Jude DaShiell <jdashiel@panix.com>]

I had problems with that earlier too.
It was because I didn't have the latest tls package installed.
This didn't used to be necessary but now appears necessary.

On Sat, 9 Mar 2019, Nicky Chorley wrote:

> Date: Sat, 9 Mar 2019 01:52:18
> 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
>
> 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
>
>

--