On Fri, Mar 14, 2025 at 07:58:38PM +0500, Andrey Rakhmatullin wrote:
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.
Also, for most packages, the runtime dependencies should be being filled in automatically based on the package metadata (${python3:Depends}). Therefore, most of the time, missing runtime dependencies should be a non-issue, except in the case of dependencies on non-Python packages.
With that said, it *would* be possible to move away from @builddeps@, or even to filter it somehow. For Ruby packages, for example, autodep8 reads the build dependencies, and removes debhelper and gem2deb from the list when generating the autopkgtest control file. There could be a similar mechanism for pybuild-autopkgtest.
I was told the autodep8 maintainer accepts patches. :)
signature.asc
Description: PGP signature
