On 2022-07-27 04 h 18, Julian Gilbey wrote:
There seems to be little point running both pybuild-autopkgtest and a manually written debian/tests/* test suite. So would the script only add pybuild-autopkgtest to packages which don't have a manually written debian/tests/* suite?
The way I see it:1. We should have a Lintian tag for packages not using the new pybuild-autodep8 autopkgtest. It would be even better if this tag would be a pointed hint that identified 'manually' written unit test autopkgtests that could be replaced.
This way, you get something like: python-foo source: not-using-pybuil-autodep8 [debian/tests/unittests]for python packages that have old 'manually' written unit test autopkgtests and:
python-foo source: not-using-pybuild-autodep8 [no-autopkgtest] for python packages without any autopkgtest.2. lintian-brush (or something else, but I think lintian-brush is the right tool) would go over these packages to:
2.1 Add the new autodep8 autopkgtests and build the package to see if they pass
2.2 Remove the "manual" unit test autopkgtests if 2.1 succeeds 2.3 Open a bug report if 2.1 failsThis way, we can imagine a transition that would be mostly automated. We'd probably have to fix the ones that failed to migrate manually, but it would be much less work :)
Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄
OpenPGP_signature
Description: OpenPGP digital signature
