all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Richard Copley <rcopley@gmail.com>
Cc: 35739@debbugs.gnu.org
Subject: bug#35739: Bad signature from GNU ELPA
Date: Tue, 14 May 2019 18:04:47 -0400	[thread overview]
Message-ID: <87mujog0ao.fsf@gmail.com> (raw)
In-Reply-To: <CAPM58oij7D9wp2E=X8Km50HFHutMEgGdpH5dLtSsU9UzZkVtxQ@mail.gmail.com> (Richard Copley's message of "Tue, 14 May 2019 22:25:42 +0100")

retitle 35739 [w32] Bad signature from GNU ELPA for archive-contents
quit

Richard Copley <rcopley@gmail.com> writes:

> Recipe from 'emacs -Q': [M-x package-list-packages RET].
>
> Symptoms: The package list is displayed but an *Error* buffer pops up:
>
> Failed to verify signature archive-contents.sig:
> Bad signature from 474F05837FBDEF9B GNU ELPA Signing Agent (2014) <
> elpasign@elpa.gnu.org>
> Command output:
> gpg: Signature made 05/14/19 22:10:03 GMT Summer Time
> gpg:                using DSA key CA442C00F91774F17F59D9B0474F05837FBDEF9B
> gpg: BAD signature from "GNU ELPA Signing Agent (2014) <
> elpasign@elpa.gnu.org>" [unknown]

> gpg (GnuPG) 2.2.11

> In GNU Emacs 27.0.50 (build 7, x86_64-w64-mingw32)
>  of 2019-05-12 built on MACHINE

I can reproduce on my Windows machine, but not on GNU/Linux.  Maybe some
line endings are getting converted?

I also noticed that doing (setq package-check-signature nil), M-x
package-refresh-contents, (setq package-check-signature t), lets
packages be installed successfully.  It's only the archive-contents that
fails to verify.






  parent reply	other threads:[~2019-05-14 22:04 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-14 21:25 bug#35739: Bad signature from GNU ELPA Richard Copley
2019-05-14 21:37 ` bug#35739: Acknowledgement (Bad signature from GNU ELPA) Richard Copley
2019-05-14 22:04 ` Noam Postavsky [this message]
2019-05-14 22:26   ` bug#35739: Bad signature from GNU ELPA Richard Copley
2019-05-14 22:42     ` Richard Copley
2019-05-15  2:42       ` Eli Zaretskii
2019-05-15  7:13         ` Richard Copley
2019-05-15 14:03           ` Stefan Monnier
2019-05-15 15:03             ` Eli Zaretskii
2019-05-18 22:36               ` Stefan Monnier
2019-05-22  5:19                 ` Eli Zaretskii
2019-05-22 16:20                   ` Stefan Monnier
2019-05-22 17:09                     ` Eli Zaretskii
2019-05-22 19:40                       ` Stefan Monnier
2019-05-23  3:50                         ` Eli Zaretskii
2019-05-23  4:06                           ` Stefan Monnier
2019-05-23  4:52                             ` Eli Zaretskii
2019-05-23 12:10                               ` Stefan Monnier
2019-05-23 14:15                                 ` Eli Zaretskii
2019-05-24 14:22                                   ` Stefan Monnier
2019-05-24 15:00                                     ` Eli Zaretskii
2019-05-24 19:31                                       ` Stefan Monnier
2019-05-24 19:43                                         ` Eli Zaretskii
2019-05-24 19:51                                           ` Stefan Monnier
2019-05-25  7:36                                             ` Eli Zaretskii
2019-05-25 18:38                                               ` Stefan Monnier
2019-05-25 19:13                                                 ` Eli Zaretskii
2019-05-15  2:41     ` Eli Zaretskii
2019-05-15  6:46       ` Richard Copley
2019-05-15 14:40         ` Eli Zaretskii
2019-05-15 15:12           ` Richard Copley
2019-05-29 18:45         ` Stefan Monnier
2019-05-29 19:11           ` Richard Copley
2019-05-29 20:07             ` Stefan Monnier
2019-05-29 20:50               ` Noam Postavsky
2019-05-30  2:35               ` Eli Zaretskii
2019-05-31  4:54                 ` Stefan Monnier

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=87mujog0ao.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=35739@debbugs.gnu.org \
    --cc=rcopley@gmail.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.