From: Akira Yokosawa <akiyks@gmail.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Error at www.kernel.org/doc/html/next/ since next-20250610
Date: Mon, 16 Jun 2025 20:18:22 +0900 [thread overview]
Message-ID: <de7bae91-3200-481f-9db2-c0dc382c91dd@gmail.com> (raw)
Hi Konstantin,
As you might well be aware of, latest successful documentation build against
linux-next at https://www.kernel.org/doc/html/next/ was that of next-20250606.
I managed to reproduce the build error using debian bookworm's distro packages
which can be close enough to Sphinx 5.3.0 used there.
This is the error I got from "make htmldocs":
----------------------------------------------------------------
Extension error (automarkup):
Handler <function auto_markup at 0x796307745bc0> for event 'doctree-resolved' threw an exception (exception: argument for warn() given by name ('stacklevel') and position (3))
----------------------------------------------------------------
Bisection points to commit d6d1df92c25f ("docs: automarkup: Mark up
undocumented entities too") queued in Jon's docs-next branch.
Reverting it resolves the error, but honestly speaking, I don't have
any plausible theory on how that change could cause such an issue.
Actually, when I install Sphinx 5.3.0 by using venv and saying
pip install "Sphinx<6.0" pyyaml
on Ubuntu 24.04 today, said error doesn't reproduce.
I'm not sure but there might have been some minor incompatibility
between past versions of dependencies.
I'd rather upgrade Sphinx to 8.2.3 (latest).
Konstantin, could you try it?
Thanks, Akira
next reply other threads:[~2025-06-16 11:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 11:18 Akira Yokosawa [this message]
2025-06-16 12:05 ` Error at www.kernel.org/doc/html/next/ since next-20250610 Mauro Carvalho Chehab
2025-06-19 2:22 ` Akira Yokosawa
2025-06-19 6:16 ` Mauro Carvalho Chehab
2025-06-19 6:50 ` Randy Dunlap
2025-06-17 20:29 ` Konstantin Ryabitsev
2025-06-19 19:51 ` Jonathan Corbet
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=de7bae91-3200-481f-9db2-c0dc382c91dd@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.