GNU bug report logs - #35739
[w32] Bad signature from GNU ELPA for archive-contents

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Richard Copley <rcopley <at> gmail.com>
Cc: 35739 <at> debbugs.gnu.org, npostavs <at> gmail.com
Subject: bug#35739: Bad signature from GNU ELPA
Date: Wed, 15 May 2019 17:40:16 +0300

> From: Richard Copley <rcopley <at> gmail.com>
> Date: Wed, 15 May 2019 07:46:12 +0100
> Cc: Noam Postavsky <npostavs <at> gmail.com>, 35739 <at> debbugs.gnu.org
> 
>  I don't see how disabling decoding could make sense, can you explain?
> 
> Not in detail, it's not an area of expertise of mine. We call
> (decode-coding-region (point-min) (point-max) 'undecided) on the
> payload of "https://elpa.gnu.org/packages/archive-contents",
> which is raw text. The resulting buffer's buffer-file-coding-
> system is iso-latin-1-dos.
>  
> 
>  What does this code do on GNU/Linux?
> 
> The same. The resulting coding system is iso-latin-1-unix.

That URL seems to bring ASCII text.  Are you saying that GPG produces
a wrong signature because EOL format is significant for it?  (Please
forgive silly questions about GPG: I seldom if ever use it.)

In any case, if we don't want EOL conversion, we should bind
inhibit-eol-conversion to a non-nil value, and change nothing else.
But this should not be done in url-insert-buffer-contents, it should
be done in package.el, because the former is a general utility and not
necessarily needs to inhibit EOL conversion for all of its callers.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.