linux-kernel - Re: linux-next: Tree for Sep 19 (make htmldocs problem)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87bjn3a2qy.fsf@trenco.lwn.net>
Date: Sun, 21 Sep 2025 15:56:37 -0600
From: Jonathan Corbet <corbet@....net>
To: Mauro Carvalho Chehab <mchehab+huawei@...nel.org>
Cc: Randy Dunlap <rdunlap@...radead.org>, Mark Brown <broonie@...nel.org>,
 Linux Next Mailing List <linux-next@...r.kernel.org>, Linux Kernel Mailing
 List <linux-kernel@...r.kernel.org>, "open list:DOCUMENTATION"
 <linux-doc@...r.kernel.org>, Mauro Carvalho Chehab <mchehab@...nel.org>
Subject: Re: linux-next: Tree for Sep 19 (make htmldocs problem)

Mauro Carvalho Chehab <mchehab+huawei@...nel.org> writes:

>> I have no idea why
>> they felt the need to employ it for Sphinx, but they did, so we need to
>> work with that kind of configuration.  Meaning, really, I think we have
>> to just invoke sphinx-build directly rather than trying to control which
>> version of Python it may ultimately get.
>
> True, but if we ignore PYTHON3 env completely, this will break on
> other setups where sphinx is installed with a different python version
> (with includes OpenSUSE non-thumbleweed).

How do those setups work prior to your changes?  We didn't have to do
that dance before, right?  What makes it necessary now?

Thanks,

jon