Hi Alexandre, On 04-06-2019 15:55, Alexandre Rossi wrote: > I'm sorry but I do not understand, debian/control does not have a Testsuite > field. > > Anyway I managed to workaround the autopkgtest failure in sbuild by adding > a fixed debian/tests/source file to my source package. I had not tried that > because the manual page of autodep8 says it prepends that file with its > own output and I thought the failure due to the module naming would not go > away. However, it seems my fixed tests replaced the generated ones. Maybe > the manual page can be improved in this regard.
Than this may be a sbuild thing. If there is no Testsuite: field, than dpkg only adds a Testsuite: field for packages containing a d/t/control file. But if sbuild is always trying to run autopkgtest, then autodep8 will be tried by autopkgtest. In other words, if you ask autopkgtest to run on a source, it will try its best to run something, including autodep8 when that is installed. If you declare your test, autodep8 isn't tried unless you have an Testsuite: field that autodep8 should be used. Paul
signature.asc
Description: OpenPGP digital signature
