On Tue, Jul 30, 2024 at 10:47:59AM +0200, PICCA Frederic-Emmanuel wrote: > Yes, I want to be sure that all the runtime dependencies are rightfully > declared in the Depends of the python module package.
Depending on what do you mean by "all" this is not always what we want. We often don't put all modules imported by all parts of the shipped code into Depends, instead using Recommends, Suggests or nothing. > sometimes the upstream forgot about dependencies, or mark them as optional, > but they are not when running the tests... Similarly, all modules installed for tests shouldn't always go into Depends ("all modules installed for tests" is ideally the same as "all modules imported by all parts of the shipped code", plus test system deps, and minus deps for e.g. Windows code that we ship but don't run or test). > Is it possible to achieve this automatically ? lintian ? dh-python ? > python3-stdeb ? Well our tools can look at the deps declared by the upstream, and normally do that as a part of the build process. But that won't help when those deps are not what we want. -- WBR, wRAR
signature.asc
Description: PGP signature