Hi Sandro!

On Mon, Mar 23, 2020 at 11:18:32PM -0400, Sandro Tosi wrote:
> i've been working thru python-sphinx rdeps and the current list is:
> [...]
> except for the list below, all of them are not in testing, so i will
> simply ignore them as they are already RC and dont deserve to be
> waited on for this migration
> * ghc, just uploaded a fix
> * pypy/pypy3, i'm in discussion with the maintainer, i think the
> approach we're gonna use here is to drop the -doc packages: the code
> for pypy is still python2 and the documentation build requires to
> access some pypy modules, so it cant be migrated to python3 anytime
> soon
> * xapian-bindings is #953949: the maintainer needs a bit of nudging
> ,but most likely we can just remove the documentation from the
> python-xapian package and call it a day.
> with these results i think we are good to upload the latest,
> python3-only, version of sphinx in unstable right now.
> What do you think?

Thanks a lot for your work. I think now we need to do a test rebuild of
python3-sphinx reverse-build-deps, to make sure they build fine with 2.4.

2.0, 2.1, 2.2 and 2.3 releases had incompatible changes, so my estimation
is that there will be many broken packages.

See for example the following lists of bugs for previous releases (where
we updated to the next release, and did not jump through several of them):


Also some extensions were split out to separate packages on PyPI. At least
sphinxcontrib-devhelp and sphinxcontrib-qthelp may need packaging, because
they are used by vitables and pysdl2, respectively (that is what I found by
quick codesearch).

I will work on that as time allows. So far I did not have much of it :(

Any help will be welcome, especially with test rebuilds.

Dmitry Shachnev

Attachment: signature.asc
Description: PGP signature

Python-modules-team mailing list

Reply via email to