mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Masaharu Noguchi <nogunix@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Akira Yokosawa <akiyks@gmail.com>,
	Chen Miao <chenmiao.ku@gmail.com>,
	 Bagas Sanjaya <bagasdotme@gmail.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Mauro Carvalho Chehab <mchehab@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	 Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v2] docs: sphinx-pre-install: warn about unsupported Docutils versions
Date: Tue, 15 Sep 2026 22:53:58 +0900	[thread overview]
Message-ID: <aqlNvld2LINsWSSe@elitemini> (raw)
In-Reply-To: <20260915101638.76e3bf1c@foz.lan>

Hi Mauro,

On Tue, 15 Sep 2026 10:16:38 +0200, Mauro Carvalho Chehab wrote:
> Fedora 44 EOL is still in at least 7 months from now (e.g. when Fedora
> 46 will be launched), so, it could still be worth.

Thank you.  And it is not only Fedora: Akira pointed at Ubuntu 26.04 LTS,
which holds up -- it ships Sphinx 8.2.3 with Docutils 0.22.4, and its
python3-sphinx depends on "python3-docutils (>= 0.20)" with no upper bound
at all.  Both fail identically here, and an LTS carries this a good deal
further than seven months.

> Indeed it sounds a better approach on my eyes.

Taken -- v3 moves the check into tools/lib/python/kdoc/docutils_version.py
and calls it from sphinx-build-wrapper next to LatexFontChecker, only
once a PDF build has failed.  sphinx-pre-install is left untouched, which
also drops the overlap with Chen Miao's series.

> On a separate but related issue, has anyone tried to use rst2pdf
> lately (https://github.com/rst2pdf/rst2pdf)?

I have not tried it myself, but not having to go through LaTeX at all is
an appealing idea.  I would like to look at porting your branch once this
one has settled.

Thanks,
Masaharu

  reply	other threads:[~2026-09-15 13:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-14 10:35 Masaharu Noguchi
2026-09-15  7:52 ` Akira Yokosawa
2026-09-15  7:58   ` Akira Yokosawa
2026-09-15  8:16   ` Mauro Carvalho Chehab
2026-09-15 13:53     ` Masaharu Noguchi [this message]
2026-09-15 14:35     ` rst2pdf (was [PATCH v2] docs: sphinx-pre-install: warn about unsupported Docutils versions) Jonathan Corbet
2026-09-15 18:20       ` Mauro Carvalho Chehab
2026-09-15 13:41   ` [PATCH v2] docs: sphinx-pre-install: warn about unsupported Docutils versions Masaharu Noguchi

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aqlNvld2LINsWSSe@elitemini \
    --to=nogunix@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=chenmiao.ku@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®