From: Wang Kang <i@scateu.me>
To: meta@public-inbox.org, alpine-info@u.washington.edu
Subject: Re: [Alpine-info] NNTP served by public-inbox stalled in Alpine 2.21.99
Date: Wed, 16 Jan 2019 13:25:24 +0800 (HKT) [thread overview]
Message-ID: <alpine.DEB.2.21.99.1901161321390.17801@la.scateu.me> (raw)
In-Reply-To: <alpine.DEB.2.21.99.1901161043430.29788@la.scateu.me>
Dear lists,
Great news!
It has been just fixed by public-inbox.org. [1]
And according to [1], lore.kernel.org will be deployed with the patched
version soon.
Thank you so much.
[1]: https://public-inbox.org/meta/20190116045802.ikm67b4cwigso3tc@dcvr/
--
Wang Kang
On Wed, 16 Jan 2019, Wang Kang wrote:
> Dear lists,
>
> I was trying to read NNTP news served by public-inbox [1], for example
> [2] provided by Linux Kernel.
>
> The index screen works fine. I can see the complete list of message titles
> on the index screen. However, when I press enter on any of the message to
> read the body of this news, the screen stucks for ever.
>
> On the contrary, NNTP served by gmane, for example [3], works fine on
> alpine.
>
> I have attached those two debug logs generated by `alpine -d 4`. Hope you
> can help solve this problem.
>
>
> By the way, I can read [2] from w3m correctly:
>
> w3m nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard
>
>
> [1]: https://www.kernel.org/lore.html
> [2]: nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard
> [3]: gmane.mail.public-inbox.general
>
>
> Thank you.
>
>
prev parent reply other threads:[~2019-01-16 5:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-16 2:54 NNTP served by public-inbox stalled in Alpine 2.21.99 Wang Kang
2019-01-16 4:58 ` [PATCH] nntp: header responses use CRLF consistently Eric Wong
2019-01-18 21:04 ` Konstantin Ryabitsev
2019-01-19 1:14 ` Wang Kang
2019-01-19 4:41 ` Konstantin Ryabitsev
2019-01-19 4:47 ` Wang Kang
2019-01-16 5:25 ` Wang Kang [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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.99.1901161321390.17801@la.scateu.me \
--to=i@scateu.me \
--cc=alpine-info@u.washington.edu \
--cc=meta@public-inbox.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://80x24.org/public-inbox.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).