From: Tim Cross <theophilusx@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: ELPA and https from linux
Date: Fri, 19 Jul 2019 23:09:39 +1000 [thread overview]
Message-ID: <CAC=50j_k+01Zw8cgZp83AL6vQyPzh7HLekGCzhibx4MPwgHhoQ@mail.gmail.com> (raw)
In-Reply-To: <CAC=50j_Dxr74ZsxCweo7vG0M7=YLjQSu1GswAW3CrfdGT2SbVA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1833 bytes --]
Just for the records....
Updating to the pretest version emacs-26.2.90 seems to have fixed this
issue. However, it should also be noted that when I increased the
gnutls-log-level to 1, I also saw a message reporting a non-fatal temporary
resource unavailable error, so there is a small chance the issue may have
been server rather than client related.
Tim
On Fri, 19 Jul 2019 at 21:12, Tim Cross <theophilusx@gmail.com> wrote:
> Correction to previous message. Tried testing again under macOS and it
> also fails on that platform. So previous test must have just been lucky -
> suspect this is server related. Will also report to the other list.
>
> On Fri, 19 Jul 2019 at 20:54, Tim Cross <theophilusx@gmail.com> wrote:
>
>> Still doesn't work.
>>
>> My symptoms do seem very similar to the issue in bug#36725 and I suspect
>> the use-package component mentioned there is just incidental (I also have
>> use-package and it was installation of the delight package, which is used
>> by use-package, which I was using to diagnose this). I also tried the same
>> process on a mcaOS system, same emacs version and it worked with no
>> problems. So, seems to be a TLS issue and restricted to GNU Linux. Will try
>> and update the bug report with this additional info.
>>
>> thanks Eli.
>>
>> Tim
>>
>> On Fri, 19 Jul 2019 at 19:16, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>>> > Date: Fri, 19 Jul 2019 11:59:09 +0300
>>> > From: Eli Zaretskii <eliz@gnu.org>
>>> > Cc: emacs-devel@gnu.org
>>> >
>>> > If you are still seeing this now, please write to
>>> > savannah-hackers-public@gnu.org and describe the details.
>>>
>>> Alternatively, see bug#36725, maybe that is what you are seeing.
>>>
>>
>>
>> --
>> regards,
>>
>> Tim
>>
>> --
>> Tim Cross
>>
>>
>
> --
> regards,
>
> Tim
>
> --
> Tim Cross
>
>
--
regards,
Tim
--
Tim Cross
[-- Attachment #2: Type: text/html, Size: 3545 bytes --]
prev parent reply other threads:[~2019-07-19 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 7:46 ELPA and https from linux Tim Cross
2019-07-19 8:59 ` Eli Zaretskii
2019-07-19 9:15 ` Eli Zaretskii
2019-07-19 10:54 ` Tim Cross
2019-07-19 11:12 ` Tim Cross
2019-07-19 13:09 ` Tim Cross [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='CAC=50j_k+01Zw8cgZp83AL6vQyPzh7HLekGCzhibx4MPwgHhoQ@mail.gmail.com' \
--to=theophilusx@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).