Hi Ben,

python-coverage is a key package and as such it is transitively making
other packages as key packages too.

Hopefully there's a way to avoid this: define the appropriate
"nodoc" build profile. Please consider the pseudopatch hereunder.
I can also provide a Salsa MR with CI enabled to specificaly test the nodoc profile.


Greetings

Alexandre


https://release.debian.org/key-packages.html


d/control

 Build-Depends:
-    dh-python,
+    dh-sequence-python3,
+    dh-sequence-sphinxdoc <!nodoc>,
     pybuild-plugin-pyproject,
-    python3-sphinx,
-    python3-sphinx-code-tabs,
-    python3-sphinx-rtd-theme,
-    python3-sphinxcontrib.restbuilder,
-    python3-sphinxcontrib.spelling,
+    python3-sphinx <!nodoc>,
+    python3-sphinx-code-tabs <!nodoc>,
+    python3-sphinx-rtd-theme <!nodoc>,
+    python3-sphinxcontrib.restbuilder <!nodoc>,
+    python3-sphinxcontrib.spelling <!nodoc>,
     python3-setuptools,
     python3-all-dev,
     python3,
     debhelper-compat (= 13)
 Standards-Version: 4.7.2


d/rules


 %:
-        dh $@ --with python3,sphinxdoc --buildsystem=pybuild
+        dh $@ --buildsystem=pybuild


...


 override_dh_auto_build:
        dh_auto_build --buildsystem=pybuild
+ifeq (,$(filter nodoc,$(DEB_BUILD_PROFILES)))
        $(SPHINX) ${SPHINX_OPTS} -bhtml ${DOCUMENTATION_DIR}/ \
                ${DOCUMENTATION_BUILD_HTML_DIR}/
+endif
        $(RM) -r ${DOCUMENTATION_BUILD_PYCACHE_DIR}/