[Python-modules-team] Bug#973210: python-django-celery-results: FTBFS: ModuleNotFoundError: No module named 'celery.five'

Lucas Nussbaum lucas at debian.org
Tue Oct 27 17:23:11 GMT 2020


Source: python-django-celery-results
Version: 1.0.4-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201027 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<<PKGBUILDDIR>>'
> dh_auto_build
> I: pybuild base:217: /usr/bin/python3.9 setup.py build 
> running build
> running build_py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/apps.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/models.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/managers.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/admin.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> copying django_celery_results/utils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0003_auto_20181106_1101.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0002_add_task_name_args_kwargs.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0001_initial.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/migrations
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/backends
> copying django_celery_results/backends/cache.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/backends
> copying django_celery_results/backends/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/backends
> copying django_celery_results/backends/database.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.9_django-celery-results/build/django_celery_results/backends
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/apps.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/models.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/managers.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/admin.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> copying django_celery_results/utils.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0003_auto_20181106_1101.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0002_add_task_name_args_kwargs.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/migrations
> copying django_celery_results/migrations/0001_initial.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/migrations
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/backends
> copying django_celery_results/backends/cache.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/backends
> copying django_celery_results/backends/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/backends
> copying django_celery_results/backends/database.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.8_django-celery-results/build/django_celery_results/backends
> PYTHONPATH=. python3 -m sphinx -b html -d docs/.build/.doctrees -N docs docs/.build/html
> Running Sphinx v3.2.1
> 
> Configuration error:
> There is a programmable error in your configuration file:
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/sphinx/config.py", line 319, in eval_config_file
>     execfile_(filename, namespace)
>   File "/usr/lib/python3/dist-packages/sphinx/util/pycompat.py", line 89, in execfile_
>     exec(code, _globals)
>   File "/<<PKGBUILDDIR>>/docs/conf.py", line 8, in <module>
>     globals().update(conf.build_config(
>   File "/usr/lib/python3/dist-packages/sphinx_celery/conf.py", line 152, in build_config
>     configure_django(django_settings, **configure_django_settings or {})
>   File "/usr/lib/python3/dist-packages/sphinx_celery/conf.py", line 80, in configure_django
>     django_setup()
>   File "/usr/lib/python3/dist-packages/django/__init__.py", line 24, in setup
>     apps.populate(settings.INSTALLED_APPS)
>   File "/usr/lib/python3/dist-packages/django/apps/registry.py", line 114, in populate
>     app_config.import_models()
>   File "/usr/lib/python3/dist-packages/django/apps/config.py", line 211, in import_models
>     self.models_module = import_module(models_module_name)
>   File "/usr/lib/python3.8/importlib/__init__.py", line 127, in import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
>   File "<frozen importlib._bootstrap>", line 1014, in _gcd_import
>   File "<frozen importlib._bootstrap>", line 991, in _find_and_load
>   File "<frozen importlib._bootstrap>", line 975, in _find_and_load_unlocked
>   File "<frozen importlib._bootstrap>", line 671, in _load_unlocked
>   File "<frozen importlib._bootstrap_external>", line 783, in exec_module
>   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
>   File "/<<PKGBUILDDIR>>/django_celery_results/models.py", line 9, in <module>
>     from celery.five import python_2_unicode_compatible
> ModuleNotFoundError: No module named 'celery.five'
> 
> make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/10/27/python-django-celery-results_1.0.4-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.



More information about the Python-modules-team mailing list