Your message dated Sun, 19 Nov 2023 18:06:21 +0000 with message-id <e1r4mbz-005jwz...@fasolo.debian.org> and subject line Bug#1042693: fixed in python-django-celery-results 2.5.1-2 has caused the Debian Bug report #1042693, regarding python-django-celery-results: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: python-django-celery-results Version: 2.5.1-1 Severity: important Tags: ftbfs User: python-modules-t...@lists.alioth.debian.org Usertags: sphinx7.1 Hi, python-django-celery-results fails to build with Sphinx 7.1 and docutils 0.20, both of which are currently available in experimental. Relevant part (hopefully): > make[1]: Entering directory '/<<PKGBUILDDIR>>' > dh_auto_build > I: pybuild base:240: /usr/bin/python3 setup.py build > running build > running build_py > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/views.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/utils.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/apps.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/urls.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/admin.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/models.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > copying django_celery_results/managers.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying > django_celery_results/migrations/0011_taskresult_periodic_task_name.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0008_chordcounter.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0006_taskresult_date_created.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0003_auto_20181106_1101.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0010_remove_duplicate_indices.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0007_remove_taskresult_hidden.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0001_initial.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0009_groupresult.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0002_add_task_name_args_kwargs.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0004_auto_20190516_0412.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > copying django_celery_results/migrations/0005_taskresult_worker.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/migrations > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/backends > copying django_celery_results/backends/cache.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/backends > copying django_celery_results/backends/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/backends > copying django_celery_results/backends/database.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/backends > running egg_info > creating django_celery_results.egg-info > writing django_celery_results.egg-info/PKG-INFO > writing dependency_links to > django_celery_results.egg-info/dependency_links.txt > writing entry points to django_celery_results.egg-info/entry_points.txt > writing requirements to django_celery_results.egg-info/requires.txt > writing top-level names to django_celery_results.egg-info/top_level.txt > writing manifest file 'django_celery_results.egg-info/SOURCES.txt' > reading manifest file 'django_celery_results.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > warning: manifest_maker: MANIFEST.in, line 9: 'recursive-include' expects > <dir> <pattern1> <pattern2> ... > > warning: no files found matching '*' under directory 'examples' > warning: no files found matching '*.rst' under directory 'requirements' > warning: no previously-included files matching '__pycache__' found under > directory '*' > warning: no previously-included files matching '*.py[co]' found under > directory '*' > warning: no previously-included files matching '.*.sw*' found under directory > '*' > adding license file 'LICENSE' > adding license file 'AUTHORS' > writing manifest file 'django_celery_results.egg-info/SOURCES.txt' > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'django_celery_results.locale.es.LC_MESSAGES' is absent from the > `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'django_celery_results.locale.es.LC_MESSAGES' as an > importable package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that > 'django_celery_results.locale.es.LC_MESSAGES' is explicitly added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'django_celery_results.locale.es.LC_MESSAGES' to be > distributed and are > already explicitly excluding > 'django_celery_results.locale.es.LC_MESSAGES' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > ******************************************************************************** > > !! > check.warn(importable) > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'django_celery_results.locale.pt_BR.LC_MESSAGES' is absent from the > `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'django_celery_results.locale.pt_BR.LC_MESSAGES' as > an importable package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that > 'django_celery_results.locale.pt_BR.LC_MESSAGES' is explicitly added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'django_celery_results.locale.pt_BR.LC_MESSAGES' to > be distributed and are > already explicitly excluding > 'django_celery_results.locale.pt_BR.LC_MESSAGES' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > ******************************************************************************** > > !! > check.warn(importable) > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'django_celery_results.locale.ru.LC_MESSAGES' is absent from the > `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'django_celery_results.locale.ru.LC_MESSAGES' as an > importable package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that > 'django_celery_results.locale.ru.LC_MESSAGES' is explicitly added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'django_celery_results.locale.ru.LC_MESSAGES' to be > distributed and are > already explicitly excluding > 'django_celery_results.locale.ru.LC_MESSAGES' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > ******************************************************************************** > > !! > check.warn(importable) > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'django_celery_results.locale.zh_Hans.LC_MESSAGES' is absent from the > `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'django_celery_results.locale.zh_Hans.LC_MESSAGES' > as an importable package[^1], > but it is absent from setuptools' `packages` configuration. > > This leads to an ambiguous overall configuration. If you want to > distribute this > package, please make sure that > 'django_celery_results.locale.zh_Hans.LC_MESSAGES' is explicitly added > to the `packages` configuration field. > > Alternatively, you can also rely on setuptools' discovery methods > (for example by using `find_namespace_packages(...)`/`find_namespace:` > instead of `find_packages(...)`/`find:`). > > You can read more about "package discovery" on setuptools > documentation page: > > - > https://setuptools.pypa.io/en/latest/userguide/package_discovery.html > > If you don't want 'django_celery_results.locale.zh_Hans.LC_MESSAGES' > to be distributed and are > already explicitly excluding > 'django_celery_results.locale.zh_Hans.LC_MESSAGES' via > `find_namespace_packages(...)/find_namespace` or > `find_packages(...)/find`, > you can try to use `exclude_package_data`, or > `include-package-data=False` in > combination with a more fine grained `package-data` configuration. > > You can read more about "package data files" on setuptools > documentation page: > > - https://setuptools.pypa.io/en/latest/userguide/datafiles.html > > > [^1]: For Python, any directory (with suitable naming) can be > imported, > even if it does not contain any `.py` files. > On the other hand, currently there is no concept of package data > directory, all directories are treated like packages. > > ******************************************************************************** > > !! > check.warn(importable) > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/es > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/es/LC_MESSAGES > copying django_celery_results/locale/es/LC_MESSAGES/django.po -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/es/LC_MESSAGES > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/pt_BR > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/pt_BR/LC_MESSAGES > copying django_celery_results/locale/pt_BR/LC_MESSAGES/django.po -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/pt_BR/LC_MESSAGES > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/ru > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/ru/LC_MESSAGES > copying django_celery_results/locale/ru/LC_MESSAGES/django.po -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/ru/LC_MESSAGES > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/zh_Hans > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/zh_Hans/LC_MESSAGES > copying django_celery_results/locale/zh_Hans/LC_MESSAGES/django.po -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-results/build/django_celery_results/locale/zh_Hans/LC_MESSAGES > PYTHONPATH=. python3 -m sphinx -b html -d docs/.build/.doctrees -N docs > docs/.build/html > Running Sphinx v7.1.1 > making output directory... done > > Extension error (sphinx.config): > Handler <function correct_copyright_year at 0x7fa87f538360> for event > 'config-inited' threw an exception (exception: string index out of range) > make[1]: *** [debian/rules:14: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2023/07/30/exp/python-django-celery-results_2.5.1-1_unstable_sphinx-exp.log Please see [1] for Sphinx changelog and [2] for Docutils changelog. Also see [3] for the list of deprecated/removed APIs in Sphinx and possible alternatives to them. Some notable changes in Sphinx 6 and Sphinx 7: - Sphinx no longer includes jquery.js and underscore.js by default. Please use python3-sphinxcontrib.jquery package if you are using a custom template and it still needs jquery. - The setup.py build_sphinx command was removed. Please instead call sphinx-build or "python3 -m sphinx" directly. - For packages using the extlinks extension, the caption should contain exactly one "%s" placeholder (if caption is not None). In case you have questions, please Cc sph...@packages.debian.org on reply. [1]: https://www.sphinx-doc.org/en/master/changes.html [2]: https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt [3]: https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=sphinx7.1;users=python-modules-t...@lists.alioth.debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=sphinx7.1&fusertaguser=python-modules-t...@lists.alioth.debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects
--- End Message ---
--- Begin Message ---Source: python-django-celery-results Source-Version: 2.5.1-2 Done: Michael Fladischer <fl...@debian.org> We believe that the bug you reported is fixed in the latest version of python-django-celery-results, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Fladischer <fl...@debian.org> (supplier of updated python-django-celery-results package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 19 Nov 2023 17:37:09 +0000 Source: python-django-celery-results Architecture: source Version: 2.5.1-2 Distribution: unstable Urgency: low Maintainer: Debian Python Team <team+pyt...@tracker.debian.org> Changed-By: Michael Fladischer <fl...@debian.org> Closes: 1042693 Changes: python-django-celery-results (2.5.1-2) unstable; urgency=low . * Add patch to satisfy assinine sphinx 7.x parsing logic for copyright year substitution (Closes: #1042693). * Build using pybuild-plugin-pyproject. * Use python3-psycopg (3.x) instead of older python3-psycopg2 to pass Django requirements when running tests. * Copy conftest.py instead of manage.py when running autopkgtests to avoid triggering the benchmarks. Checksums-Sha1: 3d788733bb251917380d3ce13a6a201ddbfbf601 2279 python-django-celery-results_2.5.1-2.dsc 2015f9c59ba2632d80c36c2102eaaeb7093a1368 5136 python-django-celery-results_2.5.1-2.debian.tar.xz 56a0af008cce390873f47caf474848a44239b1ca 9313 python-django-celery-results_2.5.1-2_arm64.buildinfo Checksums-Sha256: 9416ce061a1d6f7e47de57630c7cde6c1344cdbab417e53923588282f6ca044c 2279 python-django-celery-results_2.5.1-2.dsc a6be1c9a3fe7bd898c5b20d7b194eb2e6380dacab88f72fa9b2ee66f545bef39 5136 python-django-celery-results_2.5.1-2.debian.tar.xz 1f2f54c065ec1cbfc814eff4c773abb216d117440e2738e10b6997bbd729374a 9313 python-django-celery-results_2.5.1-2_arm64.buildinfo Files: 417609eb48c90971d94d3a28824ed2d6 2279 python optional python-django-celery-results_2.5.1-2.dsc 25b1a147a007e44d28ef0fa35606ecb6 5136 python optional python-django-celery-results_2.5.1-2.debian.tar.xz 3a3223ad7e19272943f9a5d39f06a701 9313 python optional python-django-celery-results_2.5.1-2_arm64.buildinfo -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmVaST4ACgkQ/9PIi5l9 0WrPtAgAgZrfHESGOHDjV0YUxlLrTCOV4PCN3wh1XduvMblXJNZjgxzWBBXAud5z 7PFNk0qDIsfSYcFvhBwGy98HVElq2sg7vxWXRfuknbaE+E7vtOS5FKEMfRyaB21I YRaq4dy+tGevnGHS/8DrDvRgjRJ98Ux060Nwt4HxcqycCZUzdlMuyk24K+Cnqa2Y frtoF2pHxaFW71shmpQ04H2n//wOo51WjcuRV3ZtKNQDdJ/bKszVcbCBzbc8pBVT ptXY0UWCT1YNLtbLeVBkJu7rS/vMXsyxz20CKV9O7nRt/55fH123VeUx++JQkL1C oTxD/Lj5CiSmP2lGuw8mkmml6ZCAIg== =7wbA -----END PGP SIGNATURE-----
--- End Message ---
