Source: pynn Version: 0.9.5-2 X-Debbugs-CC: debian-ci@lists.debian.org Severity: serious User: debian-ci@lists.debian.org Usertags: fails-always Dear maintainer(s), With a recent upload of pynn you added 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 https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://manpages.debian.org/unstable/autodep8/autodep8.1.en.html#PYTHON_PACKAGES [2] https://qa.debian.org/excuses.php?package=pynn https://ci.debian.net/data/autopkgtest/testing/amd64/p/pynn/5144998/log.gz autopkgtest [19:53:41]: test autodep8-python3: [----------------------- Testing with python3.8: Traceback (most recent call last): File "<string>", line 1, in <module> ModuleNotFoundError: No module named 'pynn' autopkgtest [19:53:42]: test autodep8-python3: -----------------------]
Attachment:
signature.asc
Description: OpenPGP digital signature