Bug#903698: sphinxbase: build appears broken for multiple python3 versions

Paul Gevers elbrus at debian.org
Fri Jul 13 12:46:45 BST 2018

Source: sphinxbase
Version: 0.8+5prealpha+1-2
Severity: serious

Hi all,

sphinxbase is currently involved in the python3.7 "transition"¹. I
noticed that sphinxbase was rebuild, but that is was still listed in the
"bad" category. I took a look at the amd64 build log² and spotted the
following some oddities in python3-sphinxbase.

1) it has only has the 3.6 dependencies (hence listed as bad)
2) it only has 3.7 site-packages files
3) _sphinxbase.cpython-37m-x86_64-linux-gnu.so points to a non-exitent
file. The file is in the 3.7 site-packages directory.
4) python3 versions in the build are first 3.7 and then 3.6, they seem
to be using the same build directory.

I think this is caused by the fact that we loop over $pyver in the
d/rules file, but apparently that is broken for multiple python3 versions.

I think the package is probably not working currently hence I file this
bug. (I don't know how to fix it properly yet, maybe Samuel has ideas?).


¹ https://release.debian.org/transitions/html/python3.7.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-a11y-devel/attachments/20180713/c3e62a42/attachment.sig>

More information about the Pkg-a11y-devel mailing list