--- Begin Message ---
Source: django-session-security
Version: 2.6.6+dfsg-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1
Hi,
django-session-security 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/build/session_security
> copying session_security/views.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/utils.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/middleware.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/__init__.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/urls.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/models.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security
> copying session_security/settings.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests
> copying session_security/tests/test_base.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests
> copying session_security/tests/__init__.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests
> copying session_security/tests/test_views.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests
> copying session_security/tests/test_middleware.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests
> copying session_security/tests/test_script.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/templatetags
> copying session_security/templatetags/__init__.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/templatetags
> copying session_security/templatetags/session_security_tags.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/templatetags
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project
> copying session_security/tests/project/__init__.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project
> copying session_security/tests/project/urls.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project
> copying session_security/tests/project/settings.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project
> copying session_security/tests/project/wsgi.py ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project
> running egg_info
> creating django_session_security.egg-info
> writing django_session_security.egg-info/PKG-INFO
> writing dependency_links to
> django_session_security.egg-info/dependency_links.txt
> writing requirements to django_session_security.egg-info/requires.txt
> writing top-level names to django_session_security.egg-info/top_level.txt
> writing manifest file 'django_session_security.egg-info/SOURCES.txt'
> reading manifest file 'django_session_security.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching '*.txt'
> warning: no files found matching 'README'
> warning: no files found matching '*.mo' under directory 'session_security'
> adding license file 'LICENSE'
> adding license file 'AUTHORS'
> writing manifest file 'django_session_security.egg-info/SOURCES.txt'
> /usr/lib/python3/dist-packages/setuptools/command/build_py.py:201: _Warning:
> Package 'session_security.locale.cs.LC_MESSAGES' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.locale.cs.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
> 'session_security.locale.cs.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 'session_security.locale.cs.LC_MESSAGES' to be
> distributed and are
> already explicitly excluding 'session_security.locale.cs.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 'session_security.locale.es.LC_MESSAGES' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.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
> 'session_security.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 'session_security.locale.es.LC_MESSAGES' to be
> distributed and are
> already explicitly excluding 'session_security.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 'session_security.locale.fr.LC_MESSAGES' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.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
> 'session_security.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 'session_security.locale.fr.LC_MESSAGES' to be
> distributed and are
> already explicitly excluding 'session_security.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 'session_security.locale.it.LC_MESSAGES' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.locale.it.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
> 'session_security.locale.it.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 'session_security.locale.it.LC_MESSAGES' to be
> distributed and are
> already explicitly excluding 'session_security.locale.it.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 'session_security.locale.nl.LC_MESSAGES' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.locale.nl.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
> 'session_security.locale.nl.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 'session_security.locale.nl.LC_MESSAGES' to be
> distributed and are
> already explicitly excluding 'session_security.locale.nl.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 'session_security.locale.pl.LC_MESSAGES' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.locale.pl.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
> 'session_security.locale.pl.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 'session_security.locale.pl.LC_MESSAGES' to be
> distributed and are
> already explicitly excluding 'session_security.locale.pl.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 'session_security.locale.pt_BR.LC_MESSAGES' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.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
> 'session_security.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 'session_security.locale.pt_BR.LC_MESSAGES' to be
> distributed and are
> already explicitly excluding
> 'session_security.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 'session_security.locale.pt_PT.LC_MESSAGES' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.locale.pt_PT.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
> 'session_security.locale.pt_PT.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 'session_security.locale.pt_PT.LC_MESSAGES' to be
> distributed and are
> already explicitly excluding
> 'session_security.locale.pt_PT.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 'session_security.static.session_security' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.static.session_security' 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
> 'session_security.static.session_security' 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 'session_security.static.session_security' to be
> distributed and are
> already explicitly excluding
> 'session_security.static.session_security' 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 'session_security.templates.session_security' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.templates.session_security' 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
> 'session_security.templates.session_security' 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 'session_security.templates.session_security' to be
> distributed and are
> already explicitly excluding
> 'session_security.templates.session_security' 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 'session_security.tests.project.static' is absent from the `packages`
> configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.tests.project.static' 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
> 'session_security.tests.project.static' 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 'session_security.tests.project.static' to be
> distributed and are
> already explicitly excluding 'session_security.tests.project.static'
> 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 'session_security.tests.project.templates' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.tests.project.templates' 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
> 'session_security.tests.project.templates' 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 'session_security.tests.project.templates' to be
> distributed and are
> already explicitly excluding
> 'session_security.tests.project.templates' 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 'session_security.tests.project.templates.admin' is absent from the
> `packages` configuration.
> !!
>
>
> ********************************************************************************
> ############################
> # Package would be ignored #
> ############################
> Python recognizes 'session_security.tests.project.templates.admin' 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
> 'session_security.tests.project.templates.admin' 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 'session_security.tests.project.templates.admin' to
> be distributed and are
> already explicitly excluding
> 'session_security.tests.project.templates.admin' 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/build/session_security/locale
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/cs
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/cs/LC_MESSAGES
> copying session_security/locale/cs/LC_MESSAGES/django.po ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/cs/LC_MESSAGES
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/es
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/es/LC_MESSAGES
> copying session_security/locale/es/LC_MESSAGES/django.po ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/es/LC_MESSAGES
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/fr
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/fr/LC_MESSAGES
> copying session_security/locale/fr/LC_MESSAGES/django.po ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/fr/LC_MESSAGES
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/it
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/it/LC_MESSAGES
> copying session_security/locale/it/LC_MESSAGES/django.po ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/it/LC_MESSAGES
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/nl
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/nl/LC_MESSAGES
> copying session_security/locale/nl/LC_MESSAGES/django.po ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/nl/LC_MESSAGES
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/pl
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/pl/LC_MESSAGES
> copying session_security/locale/pl/LC_MESSAGES/django.po ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/pl/LC_MESSAGES
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/pt_BR
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/pt_BR/LC_MESSAGES
> copying session_security/locale/pt_BR/LC_MESSAGES/django.po ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/pt_BR/LC_MESSAGES
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/pt_PT
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/pt_PT/LC_MESSAGES
> copying session_security/locale/pt_PT/LC_MESSAGES/django.po ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/locale/pt_PT/LC_MESSAGES
> creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/static
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/static/session_security
> copying session_security/static/session_security/script.js ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/static/session_security
> copying session_security/static/session_security/style.css ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/static/session_security
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/templates
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/templates/session_security
> copying session_security/templates/session_security/all.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/templates/session_security
> copying session_security/templates/session_security/dialog.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/templates/session_security
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project/static
> copying session_security/tests/project/static/jquery.js ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project/static
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project/templates
> copying session_security/tests/project/templates/404.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project/templates
> copying session_security/tests/project/templates/500.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project/templates
> copying session_security/tests/project/templates/home.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project/templates
> creating
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project/templates/admin
> copying session_security/tests/project/templates/admin/base_site.html ->
> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11/build/session_security/tests/project/templates/admin
> python3 setup.py build_sphinx
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
> or: setup.py --help [cmd1 cmd2 ...]
> or: setup.py --help-commands
> or: setup.py cmd --help
>
> error: invalid command 'build_sphinx'
> make[1]: *** [debian/rules:8: override_dh_auto_build] Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/django-session-security_2.6.6+dfsg-2_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 ---
