all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicky Chorley <nick.chorley@gmail.com>
To: Jude DaShiell <jdashiel@panix.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent
Date: Thu, 13 Jun 2019 08:25:11 +0100	[thread overview]
Message-ID: <CAAOASM-5TY1OxmU79Z32JqaOiyLjOL_bZGbe1HSNW3zJNzbUyw@mail.gmail.com> (raw)
In-Reply-To: <alpine.NEB.2.21.1903090256170.27575@panix1.panix.com>

Well, I upgraded GnuTLS to 3.6.7 (the latest in Slackware's repos),
but nothing changed. I also tried building the latest version of Emacs
(26.2) just to see if it made a difference, but it didn't.

I also realised that my version of GnuPG 2 is quite old, but don't
know what else is using that. So, I just tried
package-refresh-contents on Emacs 26.2 on a Fedora 30 install (albeit
inside a Docker container), which has a much newer version of GnuPG 2
(2.2.13). The same problem occurred.

This is extremely frustrating!

On Sat, 9 Mar 2019 at 07:57, Jude DaShiell <jdashiel@panix.com> wrote:
>
> 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
> >
> >
>
> --
>



  parent reply	other threads:[~2019-06-13  7:25 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
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 [this message]
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-5TY1OxmU79Z32JqaOiyLjOL_bZGbe1HSNW3zJNzbUyw@mail.gmail.com \
    --to=nick.chorley@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=jdashiel@panix.com \
    /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.