Source: pywps Version: 4.5.2-2 Severity: minor Tags: trixie sid ftbfs User: [email protected] Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build User: [email protected] Usertags: qa-doublebuild
Hi, This package fails to do build a binary-only build (not source) after a successful build (dpkg-buildpackage ; dpkg-buildpackage -b). This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target. More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild Relevant part of the build log: > cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env > -us -uc -rfakeroot -b > ----------------------------------------------------------------------------------------------------------------- > > dpkg-buildpackage: info: source package pywps > dpkg-buildpackage: info: source version 4.5.2-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Bas Couwenberg > <[email protected]> > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --with apache2,python3,sphinxdoc --buildsystem=pybuild > dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:291: python3.11 setup.py clean > running clean > removing '/<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build' (and everything > under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.11' does not exist -- can't clean it > dh_autoreconf_clean -O--buildsystem=pybuild > dh_clean -O--buildsystem=pybuild > debian/rules binary > dh binary --with apache2,python3,sphinxdoc --buildsystem=pybuild > dh_update_autotools_config -O--buildsystem=pybuild > dh_autoreconf -O--buildsystem=pybuild > dh_auto_configure -O--buildsystem=pybuild > I: pybuild base:291: python3.11 setup.py config > running config > debian/rules override_dh_auto_build > make[1]: Entering directory '/<<PKGBUILDDIR>>' > dh_auto_build > I: pybuild base:291: /usr/bin/python3 setup.py build > running build > running build_py > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps > copying pywps/configuration.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps > copying pywps/dependencies.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps > copying pywps/ext_autodoc.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps > copying pywps/tests.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps > copying pywps/dblog.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps > copying pywps/translations.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps > copying pywps/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps > copying pywps/exceptions.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps > copying pywps/util.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps > copying pywps/xml_util.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/processing > copying pywps/processing/scheduler.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/processing > copying pywps/processing/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/processing > copying pywps/processing/job.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/processing > copying pywps/processing/basic.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/processing > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/validator > copying pywps/validator/complexvalidator.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/validator > copying pywps/validator/mode.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/validator > copying pywps/validator/base.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/validator > copying pywps/validator/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/validator > copying pywps/validator/literalvalidator.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/validator > copying pywps/validator/allowed_value.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/validator > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout > copying pywps/inout/outputs.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout > copying pywps/inout/types.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout > copying pywps/inout/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout > copying pywps/inout/inputs.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout > copying pywps/inout/basic.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout > copying pywps/inout/literaltypes.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout > copying pywps/inout/array_encode.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/response > copying pywps/response/execute.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/response > copying pywps/response/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/response > copying pywps/response/describe.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/response > copying pywps/response/capabilities.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/response > copying pywps/response/status.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/response > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/app > copying pywps/app/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/app > copying pywps/app/exceptions.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/app > copying pywps/app/Common.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/app > copying pywps/app/Service.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/app > copying pywps/app/Process.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/app > copying pywps/app/basic.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/app > copying pywps/app/WPSRequest.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/app > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/resources > copying pywps/resources/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/resources > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout/formats > copying pywps/inout/formats/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout/formats > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout/storage > copying pywps/inout/storage/builder.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout/storage > copying pywps/inout/storage/file.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout/storage > copying pywps/inout/storage/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout/storage > copying pywps/inout/storage/implementationbuilder.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout/storage > copying pywps/inout/storage/s3.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/inout/storage > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/resources/schemas > copying pywps/resources/schemas/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/resources/schemas > running egg_info > writing pywps.egg-info/PKG-INFO > writing dependency_links to pywps.egg-info/dependency_links.txt > writing entry points to pywps.egg-info/entry_points.txt > writing requirements to pywps.egg-info/requires.txt > writing top-level names to pywps.egg-info/top_level.txt > reading manifest file 'pywps.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > no previously-included directories found matching 'docs/' > warning: no previously-included files matching '*.py[co]' found anywhere in > distribution > adding license file 'LICENSE.txt' > writing manifest file 'pywps.egg-info/SOURCES.txt' > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'pywps.schemas.geojson' is absent from the `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'pywps.schemas.geojson' as an importable > package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that 'pywps.schemas.geojson' is explicitly > added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'pywps.schemas.geojson' to be distributed and are > already explicitly excluding 'pywps.schemas.geojson' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > ******************************************************************************** > > !! > check.warn(importable) > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'pywps.schemas.metalink' is absent from the `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'pywps.schemas.metalink' as an importable > package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that 'pywps.schemas.metalink' is explicitly > added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'pywps.schemas.metalink' to be distributed and are > already explicitly excluding 'pywps.schemas.metalink' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > ******************************************************************************** > > !! > check.warn(importable) > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'pywps.schemas.ncml' is absent from the `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'pywps.schemas.ncml' as an importable package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that 'pywps.schemas.ncml' is explicitly > added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'pywps.schemas.ncml' to be distributed and are > already explicitly excluding 'pywps.schemas.ncml' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > ******************************************************************************** > > !! > check.warn(importable) > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'pywps.templates' is absent from the `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'pywps.templates' as an importable package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that 'pywps.templates' is explicitly added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'pywps.templates' to be distributed and are > already explicitly excluding 'pywps.templates' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > ******************************************************************************** > > !! > check.warn(importable) > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'pywps.templates.metalink' is absent from the `packages` > configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'pywps.templates.metalink' as an importable > package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that 'pywps.templates.metalink' is > explicitly added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'pywps.templates.metalink' to be distributed and are > already explicitly excluding 'pywps.templates.metalink' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > ******************************************************************************** > > !! > check.warn(importable) > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/geojson > copying pywps/schemas/geojson/README -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/geojson > copying pywps/schemas/geojson/bbox.json -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/geojson > copying pywps/schemas/geojson/crs.json -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/geojson > copying pywps/schemas/geojson/geojson.json -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/geojson > copying pywps/schemas/geojson/geometry.json -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/geojson > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/metalink > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/metalink/3.0 > copying pywps/schemas/metalink/3.0/metalink.xsd -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/metalink/3.0 > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/metalink/4.0 > copying pywps/schemas/metalink/4.0/metalink4.xsd -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/metalink/4.0 > copying pywps/schemas/metalink/4.0/xml.xsd -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/metalink/4.0 > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/ncml > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/ncml/2.2 > copying pywps/schemas/ncml/2.2/ncml-2.2.xsd -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/schemas/ncml/2.2 > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/1.0.0 > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/1.0.0/capabilities > copying pywps/templates/1.0.0/capabilities/main.xml -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/1.0.0/capabilities > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/1.0.0/describe > copying pywps/templates/1.0.0/describe/bbox.xml -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/1.0.0/describe > copying pywps/templates/1.0.0/describe/complex.xml -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/1.0.0/describe > copying pywps/templates/1.0.0/describe/literal.xml -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/1.0.0/describe > copying pywps/templates/1.0.0/describe/main.xml -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/1.0.0/describe > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/1.0.0/execute > copying pywps/templates/1.0.0/execute/main.xml -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/1.0.0/execute > creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/2.0.0 > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/2.0.0/capabilities > copying pywps/templates/2.0.0/capabilities/main.xml -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/2.0.0/capabilities > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/metalink > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/metalink/3.0 > copying pywps/templates/metalink/3.0/main.xml -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/metalink/3.0 > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/metalink/4.0 > copying pywps/templates/metalink/4.0/main.xml -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/templates/metalink/4.0 > copying pywps/resources/schemas/wps_all.xsd -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/pywps/resources/schemas > (cd docs && PYTHONPATH=/<<PKGBUILDDIR>> /usr/bin/make html && \ > ln -s /usr/share/javascript/mathjax _build/html/_static/) > make[2]: Entering directory '/<<PKGBUILDDIR>>/docs' > sphinx-build -W -b html -d _build/doctrees . _build/html > Running Sphinx v5.3.0 > loading pickled environment... done > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 0 source files that are out of date > updating environment: 0 added, 0 changed, 0 removed > looking for now-outdated files... none found > no targets are out of date. > build succeeded. > > The HTML pages are in _build/html. > > Build finished. The HTML pages are in _build/html. > make[2]: Leaving directory '/<<PKGBUILDDIR>>/docs' > ln: failed to create symbolic link '_build/html/_static/mathjax': File exists > make[1]: *** [debian/rules:25: override_dh_auto_build] Error 1 > make[1]: Leaving directory '/<<PKGBUILDDIR>>' > make: *** [debian/rules:16: binary] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 > > E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage > --sanitize-env -us -uc -rfakeroot -b' failed to run. The full build log is available from: http://qa-logs.debian.net/2023/08/16/pywps_4.5.2-2_unstable.log If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
