From: Tim Cross <theophilusx@gmail.com>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Lennard Henze <henzelen@hu-berlin.de>, 36725@debbugs.gnu.org
Subject: bug#36725: 26.1; Emacs can't connect to gnu elpa
Date: Fri, 19 Jul 2019 22:09:43 +1000 [thread overview]
Message-ID: <CAC=50j-JAg+5Pu5e8wNCmR0mwOFdw5fpHxCjxDZn8asdGJo7Vg@mail.gmail.com> (raw)
In-Reply-To: <87lfwuxmdt.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
Yep, checked and it made no difference. Did get a little more wrt error info
gnutls.el: (err=[-50] The request is invalid.) boot: (:priority
"NORMAL:-VERS-TLS1.3" :hostname melpa.org :loglevel 0 :min-prime-bits 256
:trustfiles (/etc/ssl/certs/ca-certificates.crt) :crlfiles nil :keylist nil
:verify-flags nil :verify-error nil :callbacks nil)
Also tried with TLS 1.2, same error.
On Fri, 19 Jul 2019 at 22:02, Noam Postavsky <npostavs@gmail.com> wrote:
> Robert Pluim <rpluim@gmail.com> writes:
>
> > Noam> Does (setq gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3")
> help? If
> > Noam> yes, this is likely Bug#34341 (should already be fixed already
> in
> > Noam> emacs-26, and the 26.2.90 pretest).
> >
> > elpa.gnu.org uses TLS1.2, not TLS1.3. But emacs-27 has a bunch of
> > changes in its TLS handling that might improve matters.
>
> Hmm, it does. On the other hand, Lennard told me [Lennard, please use
> "Reply All" next time so your response goes to the bug list] that (setq
> gnutls-algorithm-priority "NORMAL:-VERS-TLS1.3") did actually help.
>
> Tim, can you check the gnutls-algorithm-priority workaround too?
>
>
--
regards,
Tim
--
Tim Cross
[-- Attachment #2: Type: text/html, Size: 1992 bytes --]
next prev parent reply other threads:[~2019-07-19 12:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 19:28 bug#36725: 26.1; Emacs can't connect to gnu elpa Lennard Henze
2019-07-18 23:49 ` Noam Postavsky
2019-07-19 8:45 ` Robert Pluim
2019-07-19 12:02 ` Noam Postavsky
2019-07-19 12:09 ` Tim Cross [this message]
2019-07-19 12:14 ` Noam Postavsky
2019-07-19 12:26 ` Tim Cross
2019-07-19 12:15 ` Tim Cross
2019-07-19 14:14 ` Noam Postavsky
2019-07-19 15:46 ` Tim Cross
2019-07-19 16:50 ` Noam Postavsky
2019-07-19 12:15 ` Lennard Henze
2019-07-19 12:33 ` Tim Cross
2019-07-19 13:06 ` Lennard Henze
2019-07-19 13:18 ` Tim Cross
2019-07-19 11:01 ` bug#36725: Tim Cross
2019-07-19 11:16 ` bug#36725: Tim Cross
2019-07-19 12:46 ` bug#36725: Robert Pluim
2019-07-19 12:51 ` bug#36725: Tim Cross
2019-07-19 13:03 ` bug#36725: Tim Cross
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='CAC=50j-JAg+5Pu5e8wNCmR0mwOFdw5fpHxCjxDZn8asdGJo7Vg@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=36725@debbugs.gnu.org \
--cc=henzelen@hu-berlin.de \
--cc=npostavs@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 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).