Bug#1010754: unblock: spyder/5.3.0+dfsg1-7 and unblock: spyder-unittest/0.5.0-3
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Please unblock package spyder and spyder-unittest
(If this isn't the correct Usertags to use, please forgive me - I
couldn't figure out a better one.)
[ Reason ]
The binary packages of spyder (spyder, python3-spyder and
spyder-common) are all "Architecture: all". However, the 5.x versions
of spyder (the previous one in stable was 4.x) now depend on
python3-pyqt5.qtwebengine, which is only available on six
architectures. For this reason, spyder's autopkgtest has seen a
regression on ppc64el and s390x as the package is no longer
installable on those architectures.
spyder-unittest depends on spyder, and so has exactly the same issue.
And when spyder-notebook and spyder-terminal are ready, they will face
the same as well, in spite of being Architecture: all.
I don't know how to handle this situation - can the package be allowed
to migrate to testing and only appear in the Packages file for those
architectures on which python3-pyqt5.qtwebengine is available? If
not, what should I do?
[ Impact ]
Spyder is a popular package and it would be very sad if it were not in
Debian in the future.
[ Tests ]
A large unit test suite.
[ Checklist ]
The checklist points do not seem to be relevant at this stage in the
release cycle
unblock spyder/5.3.0+dfsg1-7
unblock spyder-unittest/0.5.0-3
Reply to: