unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Copley <rcopley@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs Development <emacs-devel@gnu.org>
Subject: Re: Future release of emacs-26
Date: Tue, 14 May 2019 22:28:17 +0100	[thread overview]
Message-ID: <CAPM58oh1YWRV6sBepTX5gT-9TUNoFPELtqE=D97n4y5c=xUHfg@mail.gmail.com> (raw)
In-Reply-To: <jwv8sv8bvm4.fsf-monnier+emacs@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1123 bytes --]

On Tue, 14 May 2019 at 22:08, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:

> > The signature checking has never worked anyway, though.
>
> Maybe not for you, but it's supposed to work, and AFAIK it works for
> many people.
>

Oh, sorry. I always assumed this was why package-check-signatures defaulted
to allow-unsigned.


> > Will having a newer
> > signature make a difference? If I rename my .emacs.d/ and run "emacs"
> > (master),
> > then "M-x package-list", I get this:
> >
> > 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 10:10:03 GMT Summer Time
> > gpg:                using DSA key
> CA442C00F91774F17F59D9B0474F05837FBDEF9B
> > gpg: BAD signature from "GNU ELPA Signing Agent (2014) <
> > elpasign@elpa.gnu.org>" [unknown]
> >
> > This is on Windows, with gpg 2.2.11 on the path.
>
> Sounds like a bug.  Could you report it as such, so we can track it
> (and hopefully fix it for 26.3)?
>

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35739

Thanks.

[-- Attachment #2: Type: text/html, Size: 2044 bytes --]

  reply	other threads:[~2019-05-14 21:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+7=K2gfxsgW7sUCLR7294kcA1kG+-0FSqL1wmdq2U5s8v2Syw@mail.gmail.com>
     [not found] ` <871s1ent89.fsf@gmail.com>
     [not found]   ` <m2pnovu7es.fsf@gmail.com>
     [not found]     ` <87pnovlr5z.fsf@gmail.com>
     [not found]       ` <m2lfzju6cg.fsf@gmail.com>
     [not found]         ` <83k1f3k3rm.fsf@gnu.org>
2019-05-14  0:34           ` Future release of emacs-26 (WAS: bug#34341) Noam Postavsky
2019-05-14 12:11             ` Nicolas Petton
2019-05-14 13:25             ` Future release of emacs-26 Stefan Monnier
2019-05-14 15:32             ` Future release of emacs-26 (WAS: bug#34341) Eli Zaretskii
2019-05-14 20:34             ` Richard Copley
2019-05-14 21:03               ` Future release of emacs-26 Stefan Monnier
2019-05-14 21:28                 ` Richard Copley [this message]
2019-05-15  1:27                   ` Stefan Monnier
2019-05-17  0:03                     ` Stephen Leake
2019-05-17  3:03                       ` Stefan Monnier
2019-05-17  6:17                         ` Richard Copley
2019-05-22 16:07             ` Phillip Lord
2019-05-22 16:26               ` Stefan Monnier
2019-05-22 17:04               ` Eli Zaretskii
2019-05-23 10:09                 ` Leo Liu
2019-05-27  9:05                 ` Phillip Lord
2019-05-27 16:13                   ` Eli Zaretskii
2019-05-27 20:17                     ` Richard Stallman
2019-05-28  2:37                       ` Eli Zaretskii
2019-05-28 21:41                     ` Noam Postavsky
2019-06-02 18:42                     ` Phillip Lord
2019-06-02 20:34                       ` Stefan Monnier
2019-06-03 14:22                     ` Noam Postavsky
2019-06-03 14:53                       ` Eli Zaretskii
2019-06-03 15:45                         ` Noam Postavsky
2019-06-03 16:00                           ` Eli Zaretskii

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='CAPM58oh1YWRV6sBepTX5gT-9TUNoFPELtqE=D97n4y5c=xUHfg@mail.gmail.com' \
    --to=rcopley@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).