From: Noam Postavsky <npostavs@gmail.com>
To: Tim Cross <theophilusx@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 08:14:32 -0400 [thread overview]
Message-ID: <87h87ixluf.fsf@gmail.com> (raw)
In-Reply-To: <CAC=50j-JAg+5Pu5e8wNCmR0mwOFdw5fpHxCjxDZn8asdGJo7Vg@mail.gmail.com> (Tim Cross's message of "Fri, 19 Jul 2019 22:09:43 +1000")
Tim Cross <theophilusx@gmail.com> writes:
> 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)
Oh, what is your value of libgnutls-version? Perhaps it's not new
enough to recognize the TLS1.3 thing. Now I'm wondering if the problem
is intermittent, and previous reports of that workaround helping are
just coincidence.
> Also tried with TLS 1.2, same error.
You mean you tried (setq gnutls-algorithm-priority
"NORMAL:-VERS-TLS1.2")?
next prev parent reply other threads:[~2019-07-19 12:14 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
2019-07-19 12:14 ` Noam Postavsky [this message]
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=87h87ixluf.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=36725@debbugs.gnu.org \
--cc=henzelen@hu-berlin.de \
--cc=theophilusx@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).