From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Glenn Morris <rgm@gnu.org>
Cc: Mark Oteiza <mvoteiza@udel.edu>, 27796@debbugs.gnu.org
Subject: bug#27796: 26.0.50; elpa unsigned file archive-contents
Date: Mon, 24 Jul 2017 15:51:35 -0400 [thread overview]
Message-ID: <jwveft5r4v0.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <jsshhlr9l4.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 24 Jul 2017 14:08:55 -0400")
>> error in process filter: Unsigned file `archive-contents' at
>> https://elpa.gnu.org/packages/ [2 times]
> Looks like http://elpa.gnu.org/packages/archive-contents.sig exists,
> but is not a valid signature file?
Hmm... works here:
% gpg --homedir ~/.emacs.d/elpa/gnupg/ archive-contents.sig
gpg: WARNING: no command supplied. Trying to guess what you mean ...
gpg: assuming signed data in 'archive-contents'
gpg: Signature made lun 24 jui 2017 05:10:02 EDT
gpg: using DSA key CA442C00F91774F17F59D9B0474F05837FBDEF9B
gpg: Good signature from "GNU ELPA Signing Agent <elpasign@elpa.gnu.org>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: CA44 2C00 F917 74F1 7F59 D9B0 474F 0583 7FBD EF9B
%
-- Stefan
next prev parent reply other threads:[~2017-07-24 19:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-23 5:14 bug#27796: 26.0.50; elpa unsigned file archive-contents Mark Oteiza
2017-07-24 18:08 ` Glenn Morris
2017-07-24 18:25 ` Glenn Morris
2017-07-24 19:24 ` Glenn Morris
2017-07-25 2:24 ` Mark Oteiza
2017-07-25 18:06 ` Glenn Morris
2017-07-25 18:21 ` Glenn Morris
2017-07-25 22:18 ` Mark Oteiza
2017-07-25 2:35 ` Mark Oteiza
2017-07-24 19:51 ` Stefan Monnier [this message]
2020-09-08 14:05 ` Stefan Kangas
2020-09-09 16:37 ` Mark Oteiza
2022-02-15 10:33 ` Lars Ingebrigtsen
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=jwveft5r4v0.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=27796@debbugs.gnu.org \
--cc=mvoteiza@udel.edu \
--cc=rgm@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).