On Mon, Jul 29, 2024 at 05:14:33PM +0200, PICCA Frederic-Emmanuel wrote: > > Maybe we indeed want a "minimal" autopkgtest environment, but many > > upstream tests will fail in those and I don't see an automatic way to test > > a random package in this way. > > Even if not minimal, at least correspond to the upstream declares > dependencies.
Those will correspond to build dependencies in a typical simple case, as the upstream tests need all those optional deps, assuming you mean the tests dependencies (and not the runtime dependencies which should already be in Depends). > Maybe we should install only the python binaries and the dependencies marked > <!nocheck>. In a typical simple case all B-Ds except sphinx stuff will be <!nocheck> as you don't need anything beyond the build system to "build" a pure Python module. So this is exactly what you wanted to avoid. -- WBR, wRAR
signature.asc
Description: PGP signature