Source: python-pint
Version: 0.19.2-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lucas@debian.org
Usertags: ftbfs-20240319 ftbfs-trixie

Hi,

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


Relevant part (hopefully):

debian/rules binary
dh binary --with python3,sphinxdoc --buildsystem=pybuild
dh_update_autotools_config -O--buildsystem=pybuild
dh_autoreconf -O--buildsystem=pybuild
dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:305: python3.12 setup.py config /usr/lib/python3/dist-packages/setuptools/__init__.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

********************************************************************************
Requirements should be satisfied by a PEP 517 installer.
If you are using pip, you can try `pip install --use-pep517`.
********************************************************************************

!!
dist.fetch_build_eggs(dist.setup_requires)
WARNING: The wheel package is not available.
running config
I: pybuild base:305: python3.11 setup.py config /usr/lib/python3/dist-packages/setuptools/__init__.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

********************************************************************************
Requirements should be satisfied by a PEP 517 installer.
If you are using pip, you can try `pip install --use-pep517`.
********************************************************************************

!!
dist.fetch_build_eggs(dist.setup_requires)
WARNING: The wheel package is not available.
running config
dh_auto_build -O--buildsystem=pybuild
I: pybuild base:305: /usr/bin/python3.12 setup.py build /usr/lib/python3/dist-packages/setuptools/__init__.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

********************************************************************************
Requirements should be satisfied by a PEP 517 installer.
If you are using pip, you can try `pip install --use-pep517`.
********************************************************************************

!!
dist.fetch_build_eggs(dist.setup_requires)
WARNING: The wheel package is not available.
running build
running build_py
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/compat.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/converters.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/parser.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/testing.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/numpy_func.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/registry_helpers.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/errors.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/registry.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/context.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/pint_eval.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/systems.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/matplotlib.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/_typing.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/measurement.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/util.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/formatting.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/quantity.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/definitions.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/babel_names.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/unit.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
running egg_info
creating Pint.egg-info
writing Pint.egg-info/PKG-INFO
writing dependency_links to Pint.egg-info/dependency_links.txt
writing requirements to Pint.egg-info/requires.txt
writing top-level names to Pint.egg-info/top_level.txt
writing manifest file 'Pint.egg-info/SOURCES.txt'
reading manifest file 'Pint.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'BADGES.rst'
warning: no files found matching 'version.txt'
warning: no files found matching '*' under directory 'bench'
no previously-included directories found matching 'docs/_build'
no previously-included directories found matching 'docs/_themes/.git' warning: no previously-included files found matching '.editorconfig'
warning: no previously-included files found matching 'bors.toml'
warning: no previously-included files found matching 'pull_request_template.md'
warning: no previously-included files found matching 'requirements_docs.txt' warning: no previously-included files found matching 'version.py'
warning: no previously-included files matching '*.pyc' found anywhere in distribution
warning: no previously-included files matching '*~' found anywhere in distribution
warning: no previously-included files matching '.DS_Store' found anywhere in distribution
warning: no previously-included files matching '*__pycache__*' found anywhere in distribution
warning: no previously-included files matching '*.pyo' found anywhere in distribution
warning: no previously-included files matching '.travis-exclude.yml' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'AUTHORS'
writing manifest file 'Pint.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pint._vendor' is absent from the `packages` configuration.
!!

********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pint._vendor' 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 'pint._vendor' 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 'pint._vendor' to be distributed and are
already explicitly excluding 'pint._vendor' 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:204: _Warning: Package 'pint.testsuite' is absent from the `packages` configuration.
!!

********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pint.testsuite' 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 'pint.testsuite' 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 'pint.testsuite' to be distributed and are
already explicitly excluding 'pint.testsuite' 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:204: _Warning: Package 'pint.testsuite.baseline' is absent from the `packages` configuration.
!!

********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pint.testsuite.baseline' 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 'pint.testsuite.baseline' 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 'pint.testsuite.baseline' to be distributed and are
already explicitly excluding 'pint.testsuite.baseline' 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)
copying pint/constants_en.txt -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/default_en.txt -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/pint-convert -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/py.typed -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
copying pint/xtranslated.txt -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/_vendor copying pint/_vendor/appdirs.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/_vendor
copying pint/_vendor/flexcache.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/_vendor
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite copying pint/testsuite/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/conftest.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/helpers.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_application_registry.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_babel.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_compat.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_compat_downcast.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_compat_upcast.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_contexts.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_converters.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_dask.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_definitions.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_diskcache.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_errors.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_formatter.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_formatting.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_infer_base_unit.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_issues.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_log_units.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_matplotlib.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_measurement.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_non_int.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_numpy.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_numpy_func.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_pint_eval.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_pitheorem.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_quantity.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_systems.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_testing.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_umath.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_unit.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
copying pint/testsuite/test_util.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite/baseline
copying pint/testsuite/baseline/test_basic_plot.png -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite/baseline
copying pint/testsuite/baseline/test_plot_with_set_units.png -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.12_pint/build/pint/testsuite/baseline
running build_scripts
creating build
creating build/scripts-3.12
copying and adjusting pint/pint-convert -> build/scripts-3.12
changing mode of build/scripts-3.12/pint-convert from 644 to 755
I: pybuild base:305: /usr/bin/python3 setup.py build /usr/lib/python3/dist-packages/setuptools/__init__.py:84: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated.
!!

********************************************************************************
Requirements should be satisfied by a PEP 517 installer.
If you are using pip, you can try `pip install --use-pep517`.
********************************************************************************

!!
dist.fetch_build_eggs(dist.setup_requires)
WARNING: The wheel package is not available.
running build
running build_py
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/compat.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/converters.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/parser.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/testing.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/numpy_func.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/registry_helpers.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/errors.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/registry.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/context.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/pint_eval.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/systems.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/matplotlib.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/_typing.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/measurement.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/util.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/formatting.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/quantity.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/definitions.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/babel_names.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/unit.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
running egg_info
writing Pint.egg-info/PKG-INFO
writing dependency_links to Pint.egg-info/dependency_links.txt
writing requirements to Pint.egg-info/requires.txt
writing top-level names to Pint.egg-info/top_level.txt
reading manifest file 'Pint.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'BADGES.rst'
warning: no files found matching 'version.txt'
warning: no files found matching '*' under directory 'bench'
no previously-included directories found matching 'docs/_build'
no previously-included directories found matching 'docs/_themes/.git' warning: no previously-included files found matching '.editorconfig'
warning: no previously-included files found matching 'bors.toml'
warning: no previously-included files found matching 'pull_request_template.md'
warning: no previously-included files found matching 'requirements_docs.txt' warning: no previously-included files found matching 'version.py'
warning: no previously-included files matching '*.pyc' found anywhere in distribution
warning: no previously-included files matching '*~' found anywhere in distribution
warning: no previously-included files matching '.DS_Store' found anywhere in distribution
warning: no previously-included files matching '*__pycache__*' found anywhere in distribution
warning: no previously-included files matching '*.pyo' found anywhere in distribution
warning: no previously-included files matching '.travis-exclude.yml' found anywhere in distribution
adding license file 'LICENSE'
adding license file 'AUTHORS'
writing manifest file 'Pint.egg-info/SOURCES.txt' /usr/lib/python3/dist-packages/setuptools/command/build_py.py:204: _Warning: Package 'pint._vendor' is absent from the `packages` configuration.
!!

********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pint._vendor' 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 'pint._vendor' 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 'pint._vendor' to be distributed and are
already explicitly excluding 'pint._vendor' 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:204: _Warning: Package 'pint.testsuite' is absent from the `packages` configuration.
!!

********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pint.testsuite' 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 'pint.testsuite' 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 'pint.testsuite' to be distributed and are
already explicitly excluding 'pint.testsuite' 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:204: _Warning: Package 'pint.testsuite.baseline' is absent from the `packages` configuration.
!!

********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pint.testsuite.baseline' 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 'pint.testsuite.baseline' 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 'pint.testsuite.baseline' to be distributed and are
already explicitly excluding 'pint.testsuite.baseline' 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)
copying pint/constants_en.txt -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/default_en.txt -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/pint-convert -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/py.typed -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
copying pint/xtranslated.txt -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/_vendor copying pint/_vendor/appdirs.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/_vendor
copying pint/_vendor/flexcache.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/_vendor
creating /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite copying pint/testsuite/__init__.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/conftest.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/helpers.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_application_registry.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_babel.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_compat.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_compat_downcast.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_compat_upcast.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_contexts.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_converters.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_dask.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_definitions.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_diskcache.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_errors.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_formatter.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_formatting.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_infer_base_unit.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_issues.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_log_units.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_matplotlib.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_measurement.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_non_int.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_numpy.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_numpy_func.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_pint_eval.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_pitheorem.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_quantity.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_systems.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_testing.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite
copying pint/testsuite/test_umath.py -> /<<PKGBUILDDIR>>/.pybuild/cpython3_3.11_pint/build/pint/testsuite

[continued in next message]

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Mon, 15 Apr 2024 12:51:25 +0000
with message-id <E1rwLnx-0045XK-55@fasolo.debian.org>
and subject line Bug#1067318: fixed in python-pint 0.23-1
has caused the Debian Bug report #1067318,
regarding python-pint: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
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 owner@bugs.debian.org
immediately.)


--
1067318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067318
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 20 Mar 2024 21:06:27 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-104.5 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,
FROMDEVELOPER,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE,
UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST,USER_IN_DKIM_WHITELIST,
WEIRD_PORT,WORD_WITHOUT_VOWELS autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 209; hammy, 150; neutral, 687; spammy,
0. spammytokens: hammytokens:0.000-+--python3,
0.000-+--Hx-spam-relays-external:sk:stravin, 0.000-+--H*RT:sk:stravin,
0.000-+--Hx-spam-relays-external:311, 0.000-+--H*RT:108
Return-path: <lucas@debian.org>
Received: f