From: Eli Zaretskii <eliz@gnu.org>
To: Iakov Davydov <dav02.davs@myths.ru>
Cc: 28780-done@debbugs.gnu.org
Subject: bug#28780: 25.3; Bad signature from GNU ELPA whe coding-system-for-read is utf-8
Date: Tue, 10 Oct 2017 22:26:56 +0300 [thread overview]
Message-ID: <83h8v6pzwf.fsf@gnu.org> (raw)
In-Reply-To: <CA+xYm8-_pvVbCCExAYEM=DR_ctsFE2yT0GUSn=rLOD1pQsSyww@mail.gmail.com> (message from Iakov Davydov on Tue, 10 Oct 2017 18:55:05 +0000)
> From: Iakov Davydov <dav02.davs@myths.ru>
> Date: Tue, 10 Oct 2017 18:55:05 +0000
> Cc: 28780@debbugs.gnu.org
>
> After carefully reading the documentation for coding-system-for-read, I think you are right. It shouldn't be used
> like that.
>
> However the snipped including this command to "unicodify" emacs is mentioned in many places including
> some answers on stackoverflow.
That's why you should always treat answers on stackoverflow with a
grain of salt (a.k.a. "suspicion").
> I think you the bug can be closed, thank you.
Done.
> > 2. https://emacs.stackexchange.com/questions/10046
> > 7. https://www.linux.org.ru/forum/security/13718006 (In Russian)
>
> I see no clear evidence that these reports are due to setting
> coding-system-for-read.
>
> At least cases #2 and #7 have a very the similar error message (and the same package in one case).
Yes, the messages are very similar. But there's no data to point in
the direction of coding-system-for-read being set.
Thanks.
prev parent reply other threads:[~2017-10-10 19:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 16:09 bug#28780: 25.3; Bad signature from GNU ELPA whe coding-system-for-read is utf-8 Iakov Davydov
2017-10-10 16:46 ` Eli Zaretskii
2017-10-10 18:55 ` Iakov Davydov
2017-10-10 19:26 ` Eli Zaretskii [this message]
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=83h8v6pzwf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28780-done@debbugs.gnu.org \
--cc=dav02.davs@myths.ru \
/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).