On Tue 2019-05-07 22:48:15 +0200, Paul Gevers wrote: > This is not the recommended way of using autodep8, albeit it does fix an > issue that is worrying me a bit [1]. You are supposed to add a > "Testsuite: autopkgtest-pkg-<flavor>" to the source stanza of your > package and never look back. See $(man autodep8).
That's news to me. I see no such documentation:
1 dkg@alice:~$ dpkg -l autodep8
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==============-============-============-=================================
ii autodep8 0.18 all DEP-8 test control file generator
0 dkg@alice:~$ man autodep8 | grep -i autopkgtest-pkg
1 dkg@alice:~$
If you could clarify this someplace that developers could find, it would
be very much appreciated.
> [1] currently the autopkgtest framework uses the version of autodep8
> from the host, which is typically up-to-date. However the test may have
> only been working with an older version of autodep8. E.g. package from
> stable/stretch that pass with autodep8 from stable/stretch may fail with
> autodep8 from buster.
understood -- but fwiw, i don't think this is particularly a problem.
that's a very similar issue as any other test suite failure caused by
shifting dependencies.
--dkg
signature.asc
Description: PGP signature
