Dear maintainer,
zxing-cpp has a package relationship with python3-numpy (either a
Depends/Recommends/Suggests or a build-time dependency) but doesn't defineany
autopkgtests.

Autopkgtests allow for automation to verify reverse-dependencies are still
working and/or building properly after a package is uploaded, and are helpful
in preventing a package from migrating to testing if they break other packages.

For these reasons, please add "meaningful" autopkgtests to this package, which
usually means running the upstream unittests.

Further information can be found at:

 * https://manpages.debian.org/unstable/autopkgtest/autopkgtest.1.en.html
 * https://manpages.debian.org/unstable/dh-python/pybuild-autopkgtest.1.en.html


Thanks!

Package list generated by:

https://github.com/sandrotosi/debian-tools/blob/master/find_rdeps_without_autopkgtests.py

The current control file lists (among others) the following build dependencies:

python3-numpy <!nocheck>,
python3-opencv <!nocheck>,
python3-pil <!nocheck>,

None of them are actually build dependencies. numpy used to be one in
pre 2.x times. Some unit tests are disabled if those packages are not
available.

While at it: libopencv-dev is not a build dependency either.

 - axxel

在 2026/8/11 11:31, axxel 写道:

Don't worry, they are all used only in post-build unit tests as well as post-build smoke tests.
The <!nocheck> marker means they are for tests only. In environments where
post-build tests are not necessary, they won't be installed as build-dependencies.
In other word, the current status quo is fine and need not any change. Of course, adding
an autopkgtest will make it better.

Best,
Boyuan Yang