> > The reason why your patch works is weird, and it's apparent when you > > run the "pip install" commands one by one: > > > > ========= > > $ pip install 'sphinx_rtd_theme==2.1.0rc1' > > Defaulting to user installation because normal site-packages is not > > writeable > > Collecting sphinx_rtd_theme==2.1.0rc1 > > Using cached sphinx_rtd_theme-2.1.0rc1-py2.py3-none-any.whl.metadata (4.4 > > kB) > > Collecting sphinx<8,>=5 (from sphinx_rtd_theme==2.1.0rc1) > > Downloading sphinx-7.4.7-py3-none-any.whl.metadata (6.1 kB) > > Requirement already satisfied: docutils<0.21 in > > /usr/lib/python3.12/site-packages (from sphinx_rtd_theme==2.1.0rc1) > > (0.20.1) > > [more "requirement already satisfied" lines...] > > Downloading sphinx_rtd_theme-2.1.0rc1-py2.py3-none-any.whl (7.7 MB) > > Downloading sphinx-7.4.7-py3-none-any.whl (3.4 MB) > > Installing collected packages: sphinx, sphinx_rtd_theme > > Attempting uninstall: sphinx > > Found existing installation: Sphinx 8.0.0rc1 > > Uninstalling Sphinx-8.0.0rc1: > > Successfully uninstalled Sphinx-8.0.0rc1 > > Successfully installed sphinx-7.4.7 sphinx_rtd_theme-2.1.0rc1 > > ========= > > > > It doesn't install 8.0.0rc1 at all... :) > > Aha. Is it possible to get mkvenv to produce these full > error messages rather than the truncated version?
Heh, the idea of pythondeps.toml was that they wouldn't be necessary - hence the messages that are slightly more tailored to the QEMU-specific issue. It's certainly a good idea to at least place them in a venv-pip.log file or something like that. Paolo
