Source: python-django-celery-beat Version: 2.5.0-1 Severity: important Tags: ftbfs User: [email protected] Usertags: sphinx7.1
Hi, python-django-celery-beat 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-beat/build/django_celery_beat > copying django_celery_beat/utils.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat > copying django_celery_beat/schedulers.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat > copying django_celery_beat/apps.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat > copying django_celery_beat/querysets.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat > copying django_celery_beat/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat > copying django_celery_beat/clockedschedule.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat > copying django_celery_beat/admin.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat > copying django_celery_beat/models.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat > copying django_celery_beat/signals.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat > copying django_celery_beat/tzcrontab.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat > copying django_celery_beat/validators.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0006_auto_20180322_0932.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying > django_celery_beat/migrations/0015_edit_solarschedule_events_choices.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0010_auto_20190429_0326.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0002_auto_20161118_0346.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0018_improve_crontab_helptext.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0008_auto_20180914_1922.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/__init__.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0006_auto_20180210_1226.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0003_auto_20161209_0049.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0011_auto_20190508_0153.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0006_periodictask_priority.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0012_periodictask_expire_seconds.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0016_alter_crontabschedule_timezone.py > -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0004_auto_20170221_0000.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0001_initial.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0013_auto_20200609_0727.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0007_auto_20180521_0826.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0014_remove_clockedschedule_enabled.py > -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying > django_celery_beat/migrations/0017_alter_crontabschedule_month_of_year.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying > django_celery_beat/migrations/0005_add_solarschedule_events_choices.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > copying django_celery_beat/migrations/0009_periodictask_headers.py -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/migrations > running egg_info > creating django_celery_beat.egg-info > writing django_celery_beat.egg-info/PKG-INFO > writing dependency_links to django_celery_beat.egg-info/dependency_links.txt > writing entry points to django_celery_beat.egg-info/entry_points.txt > writing requirements to django_celery_beat.egg-info/requires.txt > writing top-level names to django_celery_beat.egg-info/top_level.txt > writing manifest file 'django_celery_beat.egg-info/SOURCES.txt' > reading manifest file 'django_celery_beat.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 files found matching '*.mo' under directory 'django_celery_beat' > 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[a-z]' found under > directory '*' > adding license file 'LICENSE' > adding license file 'AUTHORS' > writing manifest file 'django_celery_beat.egg-info/SOURCES.txt' > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'django_celery_beat.locale.de.LC_MESSAGES' is absent from the > `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'django_celery_beat.locale.de.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_beat.locale.de.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_beat.locale.de.LC_MESSAGES' to be > distributed and are > already explicitly excluding > 'django_celery_beat.locale.de.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_beat.locale.es.LC_MESSAGES' is absent from the > `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'django_celery_beat.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_beat.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_beat.locale.es.LC_MESSAGES' to be > distributed and are > already explicitly excluding > 'django_celery_beat.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_beat.locale.fr.LC_MESSAGES' is absent from the > `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'django_celery_beat.locale.fr.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_beat.locale.fr.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_beat.locale.fr.LC_MESSAGES' to be > distributed and are > already explicitly excluding > 'django_celery_beat.locale.fr.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_beat.locale.ko.LC_MESSAGES' is absent from the > `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'django_celery_beat.locale.ko.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_beat.locale.ko.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_beat.locale.ko.LC_MESSAGES' to be > distributed and are > already explicitly excluding > 'django_celery_beat.locale.ko.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_beat.locale.ru.LC_MESSAGES' is absent from the > `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'django_celery_beat.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_beat.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_beat.locale.ru.LC_MESSAGES' to be > distributed and are > already explicitly excluding > 'django_celery_beat.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_beat.locale.zh_Hans.LC_MESSAGES' is absent from the > `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'django_celery_beat.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_beat.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_beat.locale.zh_Hans.LC_MESSAGES' to > be distributed and are > already explicitly excluding > 'django_celery_beat.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) > /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning: > Package 'django_celery_beat.templates.admin.djcelery' is absent from the > `packages` configuration. > !! > > > ******************************************************************************** > ############################ > # Package would be ignored # > ############################ > Python recognizes 'django_celery_beat.templates.admin.djcelery' 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_beat.templates.admin.djcelery' 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_beat.templates.admin.djcelery' to be > distributed and are > already explicitly excluding > 'django_celery_beat.templates.admin.djcelery' 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-beat/build/django_celery_beat/locale > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/de > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/de/LC_MESSAGES > copying django_celery_beat/locale/de/LC_MESSAGES/django.po -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/de/LC_MESSAGES > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/es > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/es/LC_MESSAGES > copying django_celery_beat/locale/es/LC_MESSAGES/django.po -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/es/LC_MESSAGES > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/fr > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/fr/LC_MESSAGES > copying django_celery_beat/locale/fr/LC_MESSAGES/django.po -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/fr/LC_MESSAGES > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/ko > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/ko/LC_MESSAGES > copying django_celery_beat/locale/ko/LC_MESSAGES/django.po -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/ko/LC_MESSAGES > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/ru > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/ru/LC_MESSAGES > copying django_celery_beat/locale/ru/LC_MESSAGES/django.po -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/ru/LC_MESSAGES > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/zh_Hans > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/zh_Hans/LC_MESSAGES > copying django_celery_beat/locale/zh_Hans/LC_MESSAGES/django.po -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/locale/zh_Hans/LC_MESSAGES > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/templates > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/templates/admin > creating > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/templates/admin/djcelery > copying django_celery_beat/templates/admin/djcelery/change_list.html -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/templates/admin/djcelery > copying > django_celery_beat/templates/admin/djcelery/change_periodictask_form.html -> > /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_django-celery-beat/build/django_celery_beat/templates/admin/djcelery > 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 0x7f5df15605e0> 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-beat_2.5.0-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 [email protected] 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;[email protected] or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=sphinx7.1&[email protected]&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
