[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#951611: python-django-modelcluster: autopkgtest failure: No module named 'django_modelcluster'

Source: python-django-modelcluster
Version: 5.0.1-1
X-Debbugs-CC: debian-ci@lists.debian.org
Severity: serious
User: debian-ci@lists.debian.org
Usertags: fails-always

Dear maintainers,

Your new package python-django-modelcluster has an autopkgtest, great.
However, it fails. I copied some of the output at the bottom of this
report. 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].

Currently this regression is blocking the migration to testing [2]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on


[2] https://qa.debian.org/excuses.php?package=python-django-modelcluster


autopkgtest [03:13:18]: 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_modelcluster;
print(django_modelcluster)" ; done
autopkgtest [03:13:18]: test autodep8-python3: [-----------------------
Testing with python3.8:
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'django_modelcluster'

Attachment: signature.asc
Description: OpenPGP digital signature

Reply to: