On Fri, Mar 14, 2025 at 01:17:24PM +0100, PICCA Frederic-Emmanuel wrote:
But also you should understand that what you want to do is very different from running the test suite, as you explicitly don't want to install deps needed for running it.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.
You said "I want to check during the autopkgtest that the runtime dependencies are well defines in the package" and for that you shouldn't have any additional packages installed, but to run tests you normally need additional packages, usually quite a lot of them.
but @builddep@ are not the dependency in order to run the test as installed but during the build.
Most of them are, considering that the build process of a pure-Python package is moving files around, building docs and running tests. Which ones aren't? sphinx and friends?
I need to check that my python-<package> dependencies and the specific tests dependencies is a working subset of @builddep@ for these tests. Am I clear ?
Yes, I just don't think the difference between @builddep@ and actual test deps is big enough to matter for this task and, as I wrote above, this won't help for your originally stated task so I'll assume you didn't actually want that.
-- WBR, wRAR
signature.asc
Description: PGP signature
