Source: furo
Version: 2023.08.19+dfsg-1
Severity: grave
furo 2023.08.19+dfsg-1 requires Sphinx v6.0:
$ grep -r 'require_sphinx(' /usr/lib/python3/dist-packages/furo
/usr/lib/python3/dist-packages/furo/__init__.py: app.require_sphinx("6.0")
However:
$ rmadison -s unstable python3-sphinx
python3-sphinx | 5.3.0-7 | unstable | all
This makes furo unusable:
$ python3 -m sphinx -N -bhtml docs/ build/html
Running Sphinx v5.3.0
making output directory... done
Sphinx version error:
The furo extension used by this project needs at least Sphinx v6.0; it
therefore cannot be built with this version.
...and breaks unrelated packages build-depending on it. I encountered
this while trying to upload a new version of tox. I'd expect the same
for the 29 packages Build-Depending on furo.
I don't know what to do at this point -- it's perhaps worth checking
with the Sphinx maintainer to see if they intend to upload a newer
version of Sphinx in the coming (very few) days, as 7.1 is already
staged in experimental.
Otherwise, backing out the commits that require the version bump, or the
version altogether, ASAP seems necessary given the impact crater.
In any case, I'd strongly suggest adding some kind of test (either at
build-time, or autopkgtests, ideally both) to avoid this kind of thing
from accidentally happening again. We're humans and bound to miss
something like that over time, so adding safeguards seems prudent :)
Regards,
Faidon
