From: Akira Yokosawa <akiyks@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: Error at www.kernel.org/doc/html/next/ since next-20250610
Date: Thu, 19 Jun 2025 11:22:19 +0900 [thread overview]
Message-ID: <6fcb75ee-61db-4fb3-9c5f-2029a7fea4ee@gmail.com> (raw)
In-Reply-To: <20250616140450.79b3fedb@foz.lan>
Hi Mauro,
On Mon, 16 Jun 2025 14:05:36 +0200, Mauro Carvalho Chehab wrote:
> Em Mon, 16 Jun 2025 20:18:22 +0900
> Akira Yokosawa <akiyks@gmail.com> escreveu:
[...]
> > 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))
> > ----------------------------------------------------------------
> Perhaps it is related to docutils version.
Looks like you are right.
debian:12 (Sphinx 5.3.0) and mageia:9 (Sphinx 6.1.3) are distro releases
whose docutils is 0.19. They both show the same symptom.
Furthermore, if I install Sphinx by using venv and saying:
pip install "docutils==0.19" Sphinx pyyaml
, I have Sphinx 7.3.6 and it shows the same symptom.
So you need to say "docutils!=0.19" when you install specific versions
of Sphinx.
>
> Assuming that it doesn't work with certain versions of sphinx or
> docutils, instead of reverting the entire patch, IMO the best would
> be to add a check for Sphinx version, disabling the broken refs
> only for too old versions.
>
Can you do so against docutils 0.19 only?
Thanks, Akira
next prev parent reply other threads:[~2025-06-19 2:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 11:18 Error at www.kernel.org/doc/html/next/ since next-20250610 Akira Yokosawa
2025-06-16 12:05 ` Mauro Carvalho Chehab
2025-06-19 2:22 ` Akira Yokosawa [this message]
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=6fcb75ee-61db-4fb3-9c5f-2029a7fea4ee@gmail.com \
--to=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=konstantin@linuxfoundation.org \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab+huawei@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 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 NNTP newsgroup(s).