==> Synchronizing chroot copy [/home/leming/armv7/root] -> [leming]...done
==> Making package: python-pylons-sphinx-themes 1.0.13-5 (Mon Dec 23 02:21:39 2024)
==> Retrieving sources...
-> Found python-pylons-sphinx-themes-1.0.13.tar.gz
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha512sums...
python-pylons-sphinx-themes-1.0.13.tar.gz ... Passed
==> Making package: python-pylons-sphinx-themes 1.0.13-5 (Mon Dec 23 02:21:58 2024)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Installing missing dependencies...
[?25lresolving dependencies...
looking for conflicting packages...
Packages (10) python-autocommand-2.2.2-7 python-jaraco.collections-5.0.1-2
python-jaraco.context-5.3.0-3 python-jaraco.functools-4.1.0-1
python-jaraco.text-4.0.0-2 python-more-itertools-10.5.0-1
python-packaging-24.2-3 python-platformdirs-4.3.6-2
python-wheel-0.45.0-3 python-setuptools-1:75.2.0-4
Total Installed Size: 10.25 MiB
:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing python-more-itertools...
installing python-jaraco.functools...
installing python-jaraco.context...
installing python-autocommand...
installing python-jaraco.text...
Optional dependencies for python-jaraco.text
python-inflect: for show-newlines script
installing python-jaraco.collections...
installing python-packaging...
installing python-platformdirs...
installing python-wheel...
Optional dependencies for python-wheel
python-keyring: for wheel.signatures
python-xdg: for wheel.signatures
python-setuptools: for legacy bdist_wheel subcommand [pending]
installing python-setuptools...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[?25h==> Retrieving sources...
-> Found python-pylons-sphinx-themes-1.0.13.tar.gz
==> WARNING: Skipping all source file integrity checks.
==> Extracting sources...
-> Extracting python-pylons-sphinx-themes-1.0.13.tar.gz with bsdtar
==> Starting build()...
running build
running build_py
creating build/lib/pylons_sphinx_themes
copying pylons_sphinx_themes/__init__.py -> build/lib/pylons_sphinx_themes
copying pylons_sphinx_themes/pylons_theme_support.py -> build/lib/pylons_sphinx_themes
running egg_info
creating pylons_sphinx_themes.egg-info
writing pylons_sphinx_themes.egg-info/PKG-INFO
writing dependency_links to pylons_sphinx_themes.egg-info/dependency_links.txt
writing top-level names to pylons_sphinx_themes.egg-info/top_level.txt
writing manifest file 'pylons_sphinx_themes.egg-info/SOURCES.txt'
reading manifest file 'pylons_sphinx_themes.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE.txt'
writing manifest file 'pylons_sphinx_themes.egg-info/SOURCES.txt'
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pylons' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pylons' 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 'pylons_sphinx_themes.pylons' 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 'pylons_sphinx_themes.pylons' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pylons' 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.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pylons.static' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pylons.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 'pylons_sphinx_themes.pylons.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 'pylons_sphinx_themes.pylons.static' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pylons.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.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pylonsfw' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pylonsfw' 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 'pylons_sphinx_themes.pylonsfw' 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 'pylons_sphinx_themes.pylonsfw' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pylonsfw' 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.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pylonsfw.static' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pylonsfw.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 'pylons_sphinx_themes.pylonsfw.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 'pylons_sphinx_themes.pylonsfw.static' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pylonsfw.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.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pyramid' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pyramid' 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 'pylons_sphinx_themes.pyramid' 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 'pylons_sphinx_themes.pyramid' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pyramid' 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.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pyramid.static' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pyramid.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 'pylons_sphinx_themes.pyramid.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 'pylons_sphinx_themes.pyramid.static' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pyramid.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)
creating build/lib/pylons_sphinx_themes/pylons
copying pylons_sphinx_themes/pylons/ethicalads.html -> build/lib/pylons_sphinx_themes/pylons
copying pylons_sphinx_themes/pylons/layout.html -> build/lib/pylons_sphinx_themes/pylons
copying pylons_sphinx_themes/pylons/theme.conf -> build/lib/pylons_sphinx_themes/pylons
creating build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/dialog-note.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/dialog-seealso.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/dialog-topic.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/dialog-warning.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/edit-me-on-github.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/epub.css -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/footerbg.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/headerbg.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/ie6.css -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/in_progress.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/middlebg.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/outdated.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/pylons-latex.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/pylons-small.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/pylons.css_t -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/pylons.ico -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/pylons.png -> build/lib/pylons_sphinx_themes/pylons/static
copying pylons_sphinx_themes/pylons/static/transparent.gif -> build/lib/pylons_sphinx_themes/pylons/static
creating build/lib/pylons_sphinx_themes/pylonsfw
copying pylons_sphinx_themes/pylonsfw/theme.conf -> build/lib/pylons_sphinx_themes/pylonsfw
creating build/lib/pylons_sphinx_themes/pylonsfw/static
copying pylons_sphinx_themes/pylonsfw/static/pylons.ico -> build/lib/pylons_sphinx_themes/pylonsfw/static
copying pylons_sphinx_themes/pylonsfw/static/pylonsfw-small.png -> build/lib/pylons_sphinx_themes/pylonsfw/static
creating build/lib/pylons_sphinx_themes/pyramid
copying pylons_sphinx_themes/pyramid/theme.conf -> build/lib/pylons_sphinx_themes/pyramid
creating build/lib/pylons_sphinx_themes/pyramid/static
copying pylons_sphinx_themes/pyramid/static/pyramid-latex.png -> build/lib/pylons_sphinx_themes/pyramid/static
copying pylons_sphinx_themes/pyramid/static/pyramid-small.png -> build/lib/pylons_sphinx_themes/pyramid/static
copying pylons_sphinx_themes/pyramid/static/pyramid.ico -> build/lib/pylons_sphinx_themes/pyramid/static
copying pylons_sphinx_themes/pyramid/static/pyramid.png -> build/lib/pylons_sphinx_themes/pyramid/static
==> Entering fakeroot environment...
==> Starting package()...
running install
/usr/lib/python3.13/site-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!
********************************************************************************
Please avoid running ``setup.py`` directly.
Instead, use pypa/build, pypa/installer or other
standards-based tools.
See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
********************************************************************************
!!
self.initialize_options()
running build
running build_py
running egg_info
writing pylons_sphinx_themes.egg-info/PKG-INFO
writing dependency_links to pylons_sphinx_themes.egg-info/dependency_links.txt
writing top-level names to pylons_sphinx_themes.egg-info/top_level.txt
reading manifest file 'pylons_sphinx_themes.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE.txt'
writing manifest file 'pylons_sphinx_themes.egg-info/SOURCES.txt'
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pylons' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pylons' 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 'pylons_sphinx_themes.pylons' 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 'pylons_sphinx_themes.pylons' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pylons' 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.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pylons.static' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pylons.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 'pylons_sphinx_themes.pylons.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 'pylons_sphinx_themes.pylons.static' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pylons.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.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pylonsfw' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pylonsfw' 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 'pylons_sphinx_themes.pylonsfw' 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 'pylons_sphinx_themes.pylonsfw' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pylonsfw' 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.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pylonsfw.static' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pylonsfw.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 'pylons_sphinx_themes.pylonsfw.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 'pylons_sphinx_themes.pylonsfw.static' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pylonsfw.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.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pyramid' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pyramid' 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 'pylons_sphinx_themes.pyramid' 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 'pylons_sphinx_themes.pyramid' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pyramid' 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.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'pylons_sphinx_themes.pyramid.static' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'pylons_sphinx_themes.pyramid.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 'pylons_sphinx_themes.pyramid.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 'pylons_sphinx_themes.pyramid.static' to be distributed and are
already explicitly excluding 'pylons_sphinx_themes.pyramid.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)
running install_lib
creating /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages
creating /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes
creating /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons
copying build/lib/pylons_sphinx_themes/pylons/ethicalads.html -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons
copying build/lib/pylons_sphinx_themes/pylons/theme.conf -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons
copying build/lib/pylons_sphinx_themes/pylons/layout.html -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons
creating /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/middlebg.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/pylons.ico -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/headerbg.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/footerbg.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/dialog-topic.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/edit-me-on-github.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/in_progress.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/dialog-seealso.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/dialog-note.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/pylons-small.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/transparent.gif -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/pylons.css_t -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/dialog-warning.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/pylons-latex.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/ie6.css -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/pylons.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/outdated.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
copying build/lib/pylons_sphinx_themes/pylons/static/epub.css -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons/static
creating /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylonsfw
copying build/lib/pylons_sphinx_themes/pylonsfw/theme.conf -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylonsfw
creating /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylonsfw/static
copying build/lib/pylons_sphinx_themes/pylonsfw/static/pylons.ico -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylonsfw/static
copying build/lib/pylons_sphinx_themes/pylonsfw/static/pylonsfw-small.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylonsfw/static
copying build/lib/pylons_sphinx_themes/__init__.py -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes
copying build/lib/pylons_sphinx_themes/pylons_theme_support.py -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes
creating /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pyramid
copying build/lib/pylons_sphinx_themes/pyramid/theme.conf -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pyramid
creating /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pyramid/static
copying build/lib/pylons_sphinx_themes/pyramid/static/pyramid.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pyramid/static
copying build/lib/pylons_sphinx_themes/pyramid/static/pyramid-small.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pyramid/static
copying build/lib/pylons_sphinx_themes/pyramid/static/pyramid.ico -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pyramid/static
copying build/lib/pylons_sphinx_themes/pyramid/static/pyramid-latex.png -> /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pyramid/static
byte-compiling /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/__init__.py to __init__.cpython-313.pyc
byte-compiling /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes/pylons_theme_support.py to pylons_theme_support.cpython-313.pyc
writing byte-compilation script '/tmp/tmpy9venhc3.py'
/usr/bin/python /tmp/tmpy9venhc3.py
removing /tmp/tmpy9venhc3.py
running install_egg_info
Copying pylons_sphinx_themes.egg-info to /build/python-pylons-sphinx-themes/pkg/python-pylons-sphinx-themes/usr/lib/python3.13/site-packages/pylons_sphinx_themes-1.0.13-py3.13.egg-info
running install_scripts
==> Tidying install...
-> Removing libtool files...
-> Purging unwanted files...
-> Removing static library files...
-> Stripping unneeded symbols from binaries and libraries...
-> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "python-pylons-sphinx-themes"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: python-pylons-sphinx-themes 1.0.13-5 (Mon Dec 23 02:22:10 2024)
==> Cleaning up...