From: Jani Nikula <jani.nikula@linux.intel.com>
To: Akira Yokosawa <akiyks@gmail.com>,
Jonathan Corbet <corbet@lwn.net>,
Vegard Nossum <vegard.nossum@oracle.com>
Cc: linux-doc@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: docs: requirements.txt has stopped working again
Date: Tue, 23 Jan 2024 20:11:54 +0200 [thread overview]
Message-ID: <87cytrnclx.fsf@intel.com> (raw)
In-Reply-To: <87y1cgm1nc.fsf@intel.com>
On Tue, 23 Jan 2024, Jani Nikula <jani.nikula@linux.intel.com> wrote:
> I looked into the root cause here. Sphinx since early versions
> (predating even 2.4.4) depends on packages such as
>
> - sphinxcontrib-applehelp
> - sphinxcontrib-devhelp
> - sphinxcontrib-htmlhelp
> - sphinxcontrib-qthelp
> - sphinxcontrib-serializinghtml
>
> but does so without any version constraints. Recently, all of those
> *packages* started first depending on Sphinx >= 5. Apparently this
> prevented installation of incompatible combos, but resulted in circular
> dependency issues in pip.
See: https://github.com/sphinx-doc/sphinx/issues/11567
> To fix the circular dependencies, all of those *packages* made the
> dependency on Sphinx >= 5 optional, but made the *extensions* in them
> app.require_sphinx('5.0') runtime. This happened in the past two weeks.
See: https://github.com/sphinx-doc/sphinx/issues/11890
BR,
Jani.
--
Jani Nikula, Intel
prev parent reply other threads:[~2024-01-23 18:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 4:14 docs: requirements.txt has stopped working again Akira Yokosawa
2024-01-23 7:43 ` Vegard Nossum
2024-01-23 12:30 ` Jani Nikula
2024-01-23 13:21 ` Vegard Nossum
2024-01-23 16:19 ` Jonathan Corbet
2024-01-24 15:02 ` Akira Yokosawa
2024-01-24 15:25 ` Jonathan Corbet
2024-01-24 15:43 ` Akira Yokosawa
2024-01-26 14:42 ` Akira Yokosawa
2024-01-24 19:56 ` Vegard Nossum
2024-01-23 16:53 ` Jani Nikula
2024-01-23 18:11 ` Jani Nikula [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=87cytrnclx.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=akiyks@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=vegard.nossum@oracle.com \
/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).