From: Akira Yokosawa <akiyks@gmail.com>
To: Masaharu Noguchi <nogunix@gmail.com>
Cc: 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] docs: sphinx-pre-install: warn about unsupported Docutils versions
Date: Mon, 14 Sep 2026 13:56:16 +0900 [thread overview]
Message-ID: <53fbb5e6-70c3-49cd-96a3-3477f048eebc@gmail.com> (raw)
In-Reply-To: <20260913-docs-sphinx-pre-install-docutils-v1-1-d923c769af91@gmail.com>
Hi,
On Sun, 13 Sep 2026 12:13:23 +0900, Masaharu Noguchi wrote:
> Sphinx declares the range of Docutils versions it supports, but a
> distribution can relax that upper bound when it wants to ship a newer
> Docutils. The pair then installs happily, and htmldocs builds without
> a complaint, so nothing looks wrong until pdfdocs is run.
>
> Fedora 44 ships such a pair: Sphinx 8.2.3 (which declares
> "docutils>=0.20,<0.22") is patched to accept "<0.23" and is installed
> alongside Docutils 0.22.4. make pdfdocs then fails to produce four of
> its books.
It sounds to me like a packaging issue in Fedora side.
I'd rather ask Fedora's Sphinx maintainer to backport the fix applied
in Sphinx 9.1.0 to their Sphinx 8.2.3.
> admin-guide runs out of TeX main memory 13 pages in:
>
> ! TeX capacity exceeded, sorry [main memory size=6000000].
> \sphinxafterbreak ->\copy \sphinxcontinuationbox
>
> while arch, core-api and translations stop on
>
> ! Dimension too large.
> \fb@put@frame ...p \ifdim \dimen@ >\ht \@tempboxa
> \end{sphinxVerbatim}
>
> Both come from the large literal blocks those books include whole --
> memory-barriers.txt, devices.txt, kernel-parameters.txt and
> arch/sparc/oradax/dax-hv-api.txt. Keeping everything else fixed and
> varying only the two versions shows that neither component is at fault
> on its own:
>
> sphinx docutils core-api admin-guide
> ------------------------------------------
> 8.1.3 0.21.2 ok ok
> 8.2.3 0.21.2 ok ok
> 8.2.3 0.22.4 FAILS FAILS
> 9.1.0 0.22.4 ok ok
>
> Sphinx gained Docutils 0.22 support in 9.0.0
This is not the case. It was done in Sphinx 9.1.0.
> and upstream decided not
> to backport it to 8.2.x [1], so this pair will stay broken rather than
> be fixed in a later 8.2 point release.
>
As this is an transient issue, I don't see much point in bothering it
in a kernel documentation script. Fedora 45 will come with Sphinx 9.1.0.
Regards, Akira
PS:
I was involved in testing the upstream fix.
(https://github.com/sphinx-doc/sphinx/issues/3099)
[...]
next prev parent reply other threads:[~2026-09-14 4:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 3:13 Masaharu Noguchi
2026-09-14 4:56 ` Akira Yokosawa [this message]
2026-09-14 9:19 ` Masaharu Noguchi
2026-09-14 5:42 ` Mauro Carvalho Chehab
2026-09-14 9:52 ` 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=53fbb5e6-70c3-49cd-96a3-3477f048eebc@gmail.com \
--to=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@kernel.org \
--cc=nogunix@gmail.com \
--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®