It's a mixed issue of python module (pip declaration deps) and python debian packages.
swh.core (thus python3-swh.core) now pulls transitively the python3-postgresql server.
This means, it installs, within debian stable, the postgresql server wherever a package
installs core (so pretty much every machine...).
Rework module and packaging so it's only a test dependency when necessary should
fix that issue (well that and cleaning up machines...)
Main package:
- python3-swh.core (0.9.0)
- python3-swh.core.db.pytestplugin (0.9.0)
Impacted packages, iirc:
- python3-swh.scheduler (0.8.0)
- python3-swh.storage (0.18.0)
- python3-swh.lister (0.4.0)
- python3-swh.vault (0.4.0)