On Thu, Nov 28, 2019 at 12:46:34PM +0100, Paul Gevers wrote:
> Source: python-pypubsub
> Version: 4.0.3-2
> X-Debbugs-CC: debian...@lists.debian.org
> User: debian...@lists.debian.org
> Usertags: regression
>
> ...
>
> [1] https://qa.debian.org/excuses.php?package=python-pypubsub
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-pypubsub/3403470/log.gz
>
> autopkgtest [15:15:47]: test autodep8-python3: set -e ; for py in
> $(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
> with $py:" ; $py -c "import pypubsub; print(pypubsub)" ; done
> autopkgtest [15:15:47]: test autodep8-python3: [-----------------------
> Testing with python3.7:
> Traceback (most recent call last):
> File "<string>", line 1, in <module>
> ModuleNotFoundError: No module named 'pypubsub'
> autopkgtest [15:15:47]: test autodep8-python3: -----------------------]
The test is correct since the correct module name is pubsub (rather than
pypubsub). It seems that's a usual pattern since if I check python3-pyvcf[1]
it ends up in:
autopkgtest [08:47:45]: test autodep8-python3: set -e ; for py in $(py3versions
-r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c
"import pyvcf; print(pyvcf)" ; done
autopkgtest [08:47:45]: test autodep8-python3: [-----------------------
Testing with python3.8:
Traceback (most recent call last):
File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'pyvcf'
autopkgtest [08:47:46]: test autodep8-python3: -----------------------]
autopkgtest [08:47:46]: test autodep8-python3: - - - - - - - - - - results - -
- - - - - - - -
autodep8-python3 FAIL non-zero exit status 1
Is there any trick to enable autopkgtest-pkg-python detecting the correct
module name?
Kind regards
Andreas.
[1]
https://ci.debian.net/data/autopkgtest/unstable/amd64/p/python-pyvcf/3462810/log.gz
--
http://fam-tille.de
