unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jude DaShiell <jdashiel@panix.com>
To: Nicky Chorley <nick.chorley@gmail.com>
Cc: VanL <van@scratch.space>, help-gnu-emacs@gnu.org
Subject: Re: Unable to use `package-refresh-contents`: Bad signature from GNU ELPA Signing Agent
Date: Mon, 24 Jun 2019 16:38:09 -0400	[thread overview]
Message-ID: <alpine.NEB.2.21.1906241631080.11319@panix1.panix.com> (raw)
In-Reply-To: <CAAOASM8vGBCz93WtGz1R5UVP8XwwtNpC9m7011Q=a-gjPfbYtg@mail.gmail.com>

I used the (add-to-list code to add elpa and melpa in my .emacs file and
that may be working.  Why the code in emacswiki shown above the
(add-to-list doesn't work I don't know.  I could add melpa but not elpa if
melpa got added first.  If I tried adding elpa first it appears as if the


(package-initialize)
(setq epg-gpg-program "/usr/bin/gpg2")
(add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/")
'("gnu" . "https://elpa.gnu.org/packages/"))
package failed on that refresh attempt and melpa was never refreshed. On
Mon, 24 Jun 2019, Nicky Chorley wrote:


> Date: Mon, 24 Jun 2019 14:58:02
> From: Nicky Chorley <nick.chorley@gmail.com>
> To: Jude DaShiell <jdashiel@panix.com>
> Cc: VanL <van@scratch.space>, help-gnu-emacs@gnu.org
> Subject: Re: Unable to use `package-refresh-contents`: Bad signature from GNU
>     ELPA Signing Agent
>
> On Sun, 23 Jun 2019 at 19:21, Jude DaShiell <jdashiel@panix.com> wrote:
> >
> > Before (package-initialize) you need (require 'package).
>
> Sadly that did not help either.
>
>

-- 



  reply	other threads:[~2019-06-24 20:38 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.NEB.2.21.1906241631080.11319@panix1.panix.com \
    --to=jdashiel@panix.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=nick.chorley@gmail.com \
    --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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).