From: Masaharu Noguchi <nogunix@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Shuah Khan <skhan@linuxfoundation.org>,
Randy Dunlap <rdunlap@infradead.org>,
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
Subject: Re: [PATCH] docs: sphinx-pre-install: warn about unsupported Docutils versions
Date: Mon, 14 Sep 2026 18:52:06 +0900 [thread overview]
Message-ID: <aqfDff8BC8vJAOAg@elitemini> (raw)
In-Reply-To: <20260914074206.05579309@foz.lan>
Hi Mauro,
Thank you for looking at this. Both directions you suggest are ones I went
down first; here is what I measured.
On Mon, 14 Sep 2026 07:42:06 +0200, Mauro Carvalho Chehab wrote:
> If so, maybe a more interesting patch would be to adjust pdf generaion
> to use a more reasonable memory limit, as 6GB sounds too little.
main_memory is counted in words rather than bytes, so that 6000000 is not 6
GB -- but raising it does not help either. Fedora 44, the broken pairing
held fixed, varying only extra_mem_top/extra_mem_bot:
core-api admin-guide
----------------------------------------------------------------
stock FAILS 26x Dim 1194p FAILS capacity 13p
+60M words FAILS 26x Dim 1194p FAILS 40x Dim 2886p, no capacity
core-api does not move at all, and admin-guide, once TeX has all the memory
it asks for, fails on "Dimension too large" instead: the memory was masking
those boxes, not causing them. Neither produces a PDF.
> This is also another parameter that may require adjustments.
> If I'm not mistaken, this is related to the maximum level depth
> on titles.
That one is maxlistdepth, which Documentation/conf.py already sets to 10.
\fb@put@frame is framed.sty's frame placement macro, and what it reports is
a box past TeX's maximum dimension, 16383.99998pt, which no setting raises.
Bisecting a single block under the kernel's LaTeX settings, 1450 lines
builds and 1500 does not, at stock memory and at ten times it;
memory-barriers.txt is 3016 lines. I wrote an override for \fb@put@frame
too, and dropped it: the same content passes unframed under an older
Docutils.
> On both cases, I don't think you can blame docutils or sphinx
> version: those are distro-specific configuration parameters.
This is what I should have shown in v1. Same container, same TeX Live, same
unmodified texmf.cnf, same tree; only the two Python packages differ:
sphinx docutils core-api admin-guide
------------------------------------------
8.2.3 0.21.2 ok ok
8.2.3 0.22.4 FAILS FAILS
9.0.4 0.22.4 FAILS FAILS
9.1.0 0.22.4 ok ok
The 9.0.4 row is a plain "pip install sphinx==9.0.4": 9.0.x declares
"docutils>=0.20,<0.23" upstream, so pip resolves Docutils to 0.22.4 by
itself, with no distribution involved.
You are right that it takes a combination, and I will say that plainly
rather than pointing at one package.
> I don't mind having a warning
One thing needs fixing regardless: Akira pointed out that the fix for this,
sphinx-doc/sphinx#3099, landed in Sphinx 9.1.0 rather than 9.0.0, so v1's
constant skips the 9.0.4 row above. I think that calls for a v2, with the
constant fixed and the commit message reworded as described.
Thanks,
Masaharu
prev parent reply other threads:[~2026-09-14 9:52 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
2026-09-14 9:19 ` Masaharu Noguchi
2026-09-14 5:42 ` Mauro Carvalho Chehab
2026-09-14 9:52 ` Masaharu Noguchi [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aqfDff8BC8vJAOAg@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®