From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B7D102D0C8F; Sun, 21 Sep 2025 21:56:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=45.79.88.28 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758491801; cv=none; b=owCCIhvqlWvnGG95M0xU/faL8cFB3LSJvByYM5b/Eyl1f1kQuyU1izVbVYxG4Ilqx729vZQJHkNF8KU7Ohj47zKA06WeKndg+qA6h9+7K6W3CS6Ra+DO/L6AG/XNtMwY+QlSmT38ajGB7rTtzzh95KVbdA91mytSc3eT79z4QlM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1758491801; c=relaxed/simple; bh=traPmwsZR7eiQJi6yFmKFtjTOxCpbDAgJO4/zZdpQ54=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=MKNcbI5zE3nIqvdUFTbo5cqNeuuXYBcgsrimNkMeacNosux0sQxgdUgoc9g6n6eXFtk+tkNe6SNXaDd6UwniqO8mefnPuHiRIDurGotCkRw+ieUTot7Ds07HW1q+NEWYRe52keRttnjqpT39tglZLj9+JPM5wI3Yu579/2oFAFU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net; spf=pass smtp.mailfrom=lwn.net; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b=hiinDJhk; arc=none smtp.client-ip=45.79.88.28 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lwn.net Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lwn.net Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=lwn.net header.i=@lwn.net header.b="hiinDJhk" DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net 7AEB640AF9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1758491798; bh=Y8yVgxKjQHj5EERyq5tPeJ6Cwh7VvXI9VdhRG9pAbwA=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=hiinDJhkHWE4iEzOdq6rQ07cYgrl+gmsP3ByNjEkko6ILX2MviNKTjp+BiBV3oY9V LIPTFPRFcIZu/JhWeGnVBQkdY5wS1Bxz89UEK7fo0q+Dz0ZJeIbanpKkKYgOJPZ2nR +zLqWfZtAlY2dNTc/6MW+/PQ+O1A7XR/68OxKHfT874afEDq+0c7WwkHsyfXwKOUwv zARYh7axvorOPdt8xNsuFLiSO8iCXAxxwijkjRZL2p5rWS2KAEtj970FSjqEsCj3bp 2EcbXTUsSFlqLg8+zwyTDcNeG8qmiwXs9Sd/STJwfkXoAYSLVCD/fl+kgKDbr1FYYW AzyjCMHTk55+g== Received: from localhost (unknown [IPv6:2601:280:4600:2da9::824]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 7AEB640AF9; Sun, 21 Sep 2025 21:56:38 +0000 (UTC) From: Jonathan Corbet To: Mauro Carvalho Chehab Cc: Randy Dunlap , Mark Brown , Linux Next Mailing List , Linux Kernel Mailing List , "open list:DOCUMENTATION" , Mauro Carvalho Chehab Subject: Re: linux-next: Tree for Sep 19 (make htmldocs problem) In-Reply-To: <20250921234301.0110130d@foz.lan> References: <883df949-0281-4a39-8745-bcdcce3a5594@infradead.org> <87ldm7c382.fsf@trenco.lwn.net> <87cy7jbo7f.fsf@trenco.lwn.net> <20250921223250.7af92f98@foz.lan> <87qzvza62n.fsf@trenco.lwn.net> <20250921234301.0110130d@foz.lan> Date: Sun, 21 Sep 2025 15:56:37 -0600 Message-ID: <87bjn3a2qy.fsf@trenco.lwn.net> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Mauro Carvalho Chehab 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