From: Markus Armbruster <armbru@redhat.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, devel@daynix.com,
John Snow <jsnow@redhat.com>
Subject: Re: [PATCH 0/3] docs: Bump sphinx to 6.2.1
Date: Thu, 15 May 2025 13:53:35 +0200 [thread overview]
Message-ID: <87plga2ips.fsf@pond.sub.org> (raw)
In-Reply-To: <20250510-sphinx72-v1-0-2358e0c68bbe@daynix.com> (Akihiko Odaki's message of "Sat, 10 May 2025 15:16:53 +0900")
Akihiko Odaki <akihiko.odaki@daynix.com> writes:
> Supersedes: <20250505-sphinx82-v1-0-85f2418b33b1@daynix.com>
> ("[PATCH 0/2] docs: Bump sphinx to 8.2.3")
>
> sphinx 5.3.0 fails with Python 3.13.1:
>
> ../docs/meson.build:37: WARNING: /home/me/qemu/build/pyvenv/bin/sphinx-build:
> Extension error:
> Could not import extension sphinx.builders.epub3 (exception: No module named 'imghdr')
>
> ../docs/meson.build:39:6: ERROR: Problem encountered: Install a Python 3 version of python-sphinx and the readthedoc theme
>
> Bump sphinx to 6.2.1 and also sphinx_rtd_theme as required for the new
> sphinx version.
>
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
Works fine for me on a Fedora 41 box (Sphinx 7.3.8)
Tested-by: Markus Armbruster <armbru@redhat.com>
next prev parent reply other threads:[~2025-05-15 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-10 6:16 [PATCH 0/3] docs: Bump sphinx to 6.2.1 Akihiko Odaki
2025-05-10 6:16 ` [PATCH 1/3] " Akihiko Odaki
2025-05-10 6:16 ` [PATCH 2/3] docs: Require sphinx>=6.2 Akihiko Odaki
2025-05-10 6:16 ` [PATCH 3/3] MAINTAINERS: Add docs/requirements.txt Akihiko Odaki
2025-05-15 11:53 ` Markus Armbruster [this message]
2025-05-19 17:47 ` [PATCH 0/3] docs: Bump sphinx to 6.2.1 John Snow
2025-06-04 22:06 ` John Snow
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=87plga2ips.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=akihiko.odaki@daynix.com \
--cc=devel@daynix.com \
--cc=jsnow@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).