[Python-modules-team] Bug#898009: sphinx-common: prefer scripts from py3k, if available

Sandro Tosi morph at debian.org
Sat May 5 18:32:56 BST 2018


Package: sphinx-common
Version: 1.7.4-1
Severity: important

Hello,
looking at /var/lib/dpkg/info/sphinx-common.postinst it seems to me sphinx
"prefers" script from the python2 package, if it's installed. I think we want to
migrate to actually build sphinx doc using the python3 package, so i think that
postinst script should be updated to link scripts from the py3k package instead.

This resulted in an issue when building numpy, where we specify to use the numpy
module from python3.6 but the upstream makefile still refers to sphinx-build
which is forcibly linked to ../share/sphinx/scripts/python2/sphinx-build ; this
is still on my development workstation where i want to have both python-sphinx
and python3-sphinx installed (i maintain some sphinx extensions so i want to be
able to test-build them on both before prepare the official package in a
chroot).

I set the priority to important, because IIRC there is a lintian working to use
py3k sphinx if a python-sphinx deps is detected.

Thanks for maintaining sphinx!

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sphinx-common depends on:
ii  libjs-sphinxdoc  1.7.4-1

Versions of packages sphinx-common recommends:
ii  python3-sphinx  1.7.4-1

sphinx-common suggests no packages.

-- no debconf information



More information about the Python-modules-team mailing list