Hello Frederic,
Am 14.03.25 um 14:17 schrieb PICCA Frederic-Emmanuel:
I want to run the same test suite (which is most often provided by
the upstream in order to test the package), during the build and as
installed.
but @builddep@ are not the dependency in order to run the test as
installed but during the build.
I need to check that my python-<package> dependencies and the
specific tests dependencies is a working subset of @builddep@ for
these tests.
then drop this variable and list all the packages that are needed to get
the upstream tests running.
I've dropped using @builddep@ in general within the packages I'm
involved to achieve exactly what Andrey has written, I want to detect
broken or missing dependencies, broken tests by changed dependencies in
other depending packages. And don't want to get this hidden by packages
that are within @builddep@ that potential pull in the other then needed
packages.
Using @builddep@ is mostly not useful for testing Python packages.
So yes, need to figure out which packages then you want to have listed
in d/t/control to make the tests pass.
--
Regards
Carsten
