Hi!

I'm a little bemused about how to handle the spyder suite of packages.

spyder (via the python3-spyder binary and Build-Depends) depends on python3-pyqt5.qtwebengine, which is (according to rmadison) only
present on amd64, armhf, i386, mips64el. ci.debian.net now only
attempts to run the spyder autopkgtests on amd64, arm64, armhf and
i386, and it passes on all these. It doesn't even say "No tests..."
for the other archs, and I don't know how ci.debian.net learnt to
ignore the other archs.

But the two (source) packages spyder-line-profiler and
spyder-unittests depend on python3-spyder and so are only installable
on that same handful of archs. However, ci.debian.net attempts to run
the autopkgtests on all 8 archs, and so four of them fail due to
uninstallable dependencies. I could mark the autopkgtests as only
running on those four archs. Is that the best thing to do, or is
there some way to indicate to ci.debian.net that the package is not
installable on some archs and so it should not try to test the package
on them?

Best wishes,

Julian

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)