Source: python-django-netfields Version: 1.2.2-1 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: fails-always
Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. I copied some of the output at the bottom of this report. Can you please investigate the situation and fix it? You're using autodep8 to trigger the test, but it seems your package naming and Python module name aren't aligned for autodep8. autodep8 recently acquired a new feature that enables you to tell autode8 what the real module name is that should be tested [1]. The release team has announced [2] that failing autopkgtest are now considered RC in testing. Paul [1] https://manpages.debian.org/unstable/autodep8/autodep8.1.en.html#PYTHON_PACKAGES [2] https://lists.debian.org/debian-devel-announce/2019/07/msg00002.html https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-django-netfields/5494902/log.gz autopkgtest [17:13: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 django_netfields; print(django_netfields)" ; done autopkgtest [17:13:47]: test autodep8-python3: [----------------------- Testing with python3.8: Traceback (most recent call last): File "<string>", line 1, in <module> ModuleNotFoundError: No module named 'django_netfields' autopkgtest [17:13:47]: test autodep8-python3: -----------------------]
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Python-modules-team mailing list Python-modules-team@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/python-modules-team
