On Mon, Oct 02, 2023 at 11:32:31PM +0100, Carles Pina i Estany wrote: > I will create a new version of the package and upload it into > mentors.debian.net when I finish this email. For reference: it will be > the version 1.2.69-3. Note that the usual practice is not bumping Debian versions for packages that were not uploaded yet and always uploading -1.
> In my first version (not published) I wrote a simple autopkgtest with an > "import cloudscraper" (I know that this is not fully testing everything > but at least something!). Then I realised that it's not needed... Yeah. And you should try "Testsuite: autopkgtest-pkg-pybuild" instead, to run upstream tests. Though I think it won't see your explicit `pytest -k` and you should replace the override with a PYBUILD_TEST_ARGS var. > without debian/tests it's just doing it: > > https://salsa.debian.org/python-team/packages/python-cloudscraper/-/jobs/4762103#L180 > """ > autopkgtest [22:24:36]: test autodep8-python3: set -e ; for py in > $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with > $py:" ; $py -c "import cloudscraper; print(cloudscraper)" ; done > """ > > I don't see this mentioned in "man autodep8": It says "each supported package type is tried against a set of heuristics, based on packages names, build dependencies. specific files under debian/, or a combination of those", or do you mean something else?
