:: Synchronizing package databases... build-support-manual downloading... build-support downloading... core-staging downloading... extra-staging downloading... core-testing downloading... core downloading... extra-testing downloading... extra downloading... :: Starting full system upgrade... there is nothing to do ==> Building in chroot for [extra-staging-with-build-support] (pentium4)... ==> Synchronizing chroot copy [/var/lib/archbuild/extra-staging-with-build-support-pentium4/root] -> [build]...done ==> Making package: python-openstackdocstheme 3.4.1-1.0 (Sun Apr 20 06:10:52 2025) ==> Retrieving sources... -> Updating openstackdocstheme git repo... ==> Validating source files with sha512sums... openstackdocstheme ... Passed gpg: Warning: using insecure memory! ==> Appending keys from archlinux32.gpg... gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! gpg: Warning: using insecure memory! ==> Updating trust database... gpg: Warning: using insecure memory! gpg: next trustdb check due at 2025-06-16 ==> Making package: python-openstackdocstheme 3.4.1-1.0 (Sun Apr 20 06:10:55 2025) ==> Checking runtime dependencies... ==> Installing missing dependencies... resolving dependencies... looking for conflicting packages... Packages (23) python-babel-2.15.0-1.0 python-charset-normalizer-3.4.0-1.0 python-docutils-1:0.21.2-1.1 python-idna-3.10-1.0 python-imagesize-1.4.1-5.1 python-jinja-1:3.1.4-1.0 python-markupsafe-2.1.5-2.2 python-pygments-2.18.0-1.0 python-pytz-2024.2-1.0 python-requests-2.32.3-1.0 python-setuptools-1-1.3 python-snowballstemmer-2.2.0-6.1 python-sphinx-alabaster-theme-1.0.0-1.0 python-sphinxcontrib-applehelp-2.0.0-1.0 python-sphinxcontrib-devhelp-2.0.0-2.0 python-sphinxcontrib-htmlhelp-2.1.0-3.0 python-sphinxcontrib-jsmath-1.0.1-19.0 python-sphinxcontrib-qthelp-2.0.0-1.0 python-sphinxcontrib-serializinghtml-2.0.0-1.0 python-urllib3-1.26.20-3.0 python-dulwich-0.22.6-1.0 python-pbr-6.1.1-1.0 python-sphinx-8.1.3-1.0 Total Installed Size: 91.91 MiB :: Proceed with installation? [Y/n] checking keyring... checking package integrity... loading package files... checking for file conflicts... :: Processing package changes... installing python-setuptools... installing python-pbr... installing python-urllib3... Optional dependencies for python-urllib3 python-brotli: Brotli support python-certifi: security support python-cryptography: security support python-idna: security support [pending] python-pyopenssl: security support python-pysocks: SOCKS support installing python-dulwich... Optional dependencies for python-dulwich python-fastimport: for fast-import support python-gpgme: for PGP signature support python-idna: for HTTPS support via urllib3 [pending] python-paramiko: for use as the SSH implementation python-pyopenssl: for HTTPS support via urllib3 python-pyinotify: to watch for changes to refs installing python-pytz... installing python-babel... installing python-docutils... Optional dependencies for python-docutils python-myst-parser: to parse input in "Markdown" (CommonMark) format python-pillow: for some image manipulation operations python-pygments: for syntax highlighting of code directives and roles [pending] installing python-imagesize... installing python-markupsafe... installing python-jinja... Optional dependencies for python-jinja python-babel: for i18n support [installed] installing python-pygments... installing python-charset-normalizer... installing python-idna... installing python-requests... installing python-snowballstemmer... Optional dependencies for python-snowballstemmer python-pystemmer: for improved performance installing python-sphinx-alabaster-theme... installing python-sphinxcontrib-applehelp... installing python-sphinxcontrib-devhelp... installing python-sphinxcontrib-htmlhelp... installing python-sphinxcontrib-jsmath... installing python-sphinxcontrib-qthelp... installing python-sphinxcontrib-serializinghtml... installing python-sphinx... Optional dependencies for python-sphinx imagemagick: for ext.imgconverter texlive-fontsextra: for the default admonition title icons in PDF output texlive-latexextra: for generation of PDF documentation :: Running post-transaction hooks... (1/1) Arming ConditionNeedsUpdate... ==> Checking buildtime dependencies... ==> Installing missing dependencies... resolving dependencies... looking for conflicting packages... Packages (4) perl-error-0.17029-7.0 perl-mailtools-2.22-1.0 perl-timedate-2.33-7.0 git-2.47.1-1.0 Total Installed Size: 28.55 MiB :: Proceed with installation? [Y/n] checking keyring... checking package integrity... loading package files... checking for file conflicts... :: Processing package changes... installing perl-error... installing perl-timedate... installing perl-mailtools... installing git... Optional dependencies for git tk: gitk and git gui openssh: ssh transport and crypto perl-libwww: git svn perl-term-readkey: git svn and interactive.singlekey setting perl-io-socket-ssl: git send-email TLS support perl-authen-sasl: git send-email TLS support perl-mediawiki-api: git mediawiki support perl-datetime-format-iso8601: git mediawiki support perl-lwp-protocol-https: git mediawiki https support perl-cgi: gitweb (web interface) support python: git svn & git p4 [installed] subversion: git svn org.freedesktop.secrets: keyring credential helper libsecret: libsecret credential helper [installed] :: Running post-transaction hooks... (1/4) Creating system user accounts... Creating group 'git' with GID 972. Creating user 'git' (git daemon user) with UID 972 and GID 972. (2/4) Reloading system manager configuration... Skipped: Current root is not booted. (3/4) Arming ConditionNeedsUpdate... (4/4) Warn about old perl modules ==> Retrieving sources... ==> WARNING: Skipping all source file integrity checks. ==> Extracting sources... -> Creating working copy of openstackdocstheme git repo... Cloning into 'openstackdocstheme'... done. Switched to a new branch 'makepkg' ==> Starting build()... ERROR:root:code for hash blake2b was not found. Traceback (most recent call last): File "/usr/lib/python3.13/hashlib.py", line 245, in globals()[__func_name] = __get_hash(__func_name) ~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib/python3.13/hashlib.py", line 129, in __get_openssl_constructor return __get_builtin_constructor(name) File "/usr/lib/python3.13/hashlib.py", line 123, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type blake2b ERROR:root:code for hash blake2s was not found. Traceback (most recent call last): File "/usr/lib/python3.13/hashlib.py", line 245, in globals()[__func_name] = __get_hash(__func_name) ~~~~~~~~~~^^^^^^^^^^^^^ File "/usr/lib/python3.13/hashlib.py", line 129, in __get_openssl_constructor return __get_builtin_constructor(name) File "/usr/lib/python3.13/hashlib.py", line 123, in __get_builtin_constructor raise ValueError('unsupported hash type ' + name) ValueError: unsupported hash type blake2s /usr/lib/python3.13/site-packages/setuptools/__init__.py:94: _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) /usr/lib/python3.13/site-packages/setuptools/command/develop.py:41: EasyInstallDeprecationWarning: easy_install command is deprecated. !! ******************************************************************************** Please avoid running ``setup.py`` and ``easy_install``. Instead, use pypa/build, pypa/installer or other standards-based tools. See https://github.com/pypa/setuptools/issues/917 for details. ******************************************************************************** !! easy_install.initialize_options(self) /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() INFO:root:running build INFO:root:running build_py INFO:root:creating build/lib/openstackdocstheme INFO:root:copying openstackdocstheme/version.py -> build/lib/openstackdocstheme INFO:root:copying openstackdocstheme/paths.py -> build/lib/openstackdocstheme INFO:root:copying openstackdocstheme/page_context.py -> build/lib/openstackdocstheme INFO:root:copying openstackdocstheme/__init__.py -> build/lib/openstackdocstheme INFO:root:copying openstackdocstheme/ext.py -> build/lib/openstackdocstheme INFO:root:running egg_info INFO:root:creating openstackdocstheme.egg-info INFO:root:writing pbr to openstackdocstheme.egg-info/pbr.json INFO:root:writing openstackdocstheme.egg-info/PKG-INFO INFO:root:writing dependency_links to openstackdocstheme.egg-info/dependency_links.txt INFO:root:writing requirements to openstackdocstheme.egg-info/requires.txt INFO:root:writing top-level names to openstackdocstheme.egg-info/top_level.txt INFO:root:[pbr] Processing SOURCES.txt INFO:root:writing manifest file 'openstackdocstheme.egg-info/SOURCES.txt' INFO:root:[pbr] In git context, generating filelist from git WARNING:root:warning: no files found matching 'AUTHORS' WARNING:root:warning: no files found matching 'ChangeLog' WARNING:root:warning: no previously-included files matching '*.pyc' found anywhere in distribution INFO:root:adding license file 'LICENSE' INFO:root:writing manifest file 'openstackdocstheme.egg-info/SOURCES.txt' /usr/lib/python3.13/site-packages/setuptools/command/build_py.py:218: _Warning: Package 'openstackdocstheme.theme.openstackdocs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.openstackdocs' 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 'openstackdocstheme.theme.openstackdocs' 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 'openstackdocstheme.theme.openstackdocs' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.openstackdocs' 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 'openstackdocstheme.theme.openstackdocs.static' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.openstackdocs.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 'openstackdocstheme.theme.openstackdocs.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 'openstackdocstheme.theme.openstackdocs.static' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.openstackdocs.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 'openstackdocstheme.theme.openstackdocs.static.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.openstackdocs.static.css' 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 'openstackdocstheme.theme.openstackdocs.static.css' 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 'openstackdocstheme.theme.openstackdocs.static.css' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.openstackdocs.static.css' 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 'openstackdocstheme.theme.openstackdocs.static.fonts' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.openstackdocs.static.fonts' 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 'openstackdocstheme.theme.openstackdocs.static.fonts' 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 'openstackdocstheme.theme.openstackdocs.static.fonts' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.openstackdocs.static.fonts' 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 'openstackdocstheme.theme.openstackdocs.static.images' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.openstackdocs.static.images' 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 'openstackdocstheme.theme.openstackdocs.static.images' 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 'openstackdocstheme.theme.openstackdocs.static.images' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.openstackdocs.static.images' 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 'openstackdocstheme.theme.openstackdocs.static.images.docs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.openstackdocs.static.images.docs' 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 'openstackdocstheme.theme.openstackdocs.static.images.docs' 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 'openstackdocstheme.theme.openstackdocs.static.images.docs' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.openstackdocs.static.images.docs' 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 'openstackdocstheme.theme.openstackdocs.static.js' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.openstackdocs.static.js' 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 'openstackdocstheme.theme.openstackdocs.static.js' 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 'openstackdocstheme.theme.openstackdocs.static.js' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.openstackdocs.static.js' 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 'openstackdocstheme.theme.openstackdocs_pdf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.openstackdocs_pdf' 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 'openstackdocstheme.theme.openstackdocs_pdf' 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 'openstackdocstheme.theme.openstackdocs_pdf' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.openstackdocs_pdf' 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 'openstackdocstheme.theme.starlingxdocs' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.starlingxdocs' 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 'openstackdocstheme.theme.starlingxdocs' 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 'openstackdocstheme.theme.starlingxdocs' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.starlingxdocs' 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 'openstackdocstheme.theme.starlingxdocs.static.css' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.starlingxdocs.static.css' 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 'openstackdocstheme.theme.starlingxdocs.static.css' 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 'openstackdocstheme.theme.starlingxdocs.static.css' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.starlingxdocs.static.css' 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 'openstackdocstheme.theme.starlingxdocs.static.images' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.starlingxdocs.static.images' 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 'openstackdocstheme.theme.starlingxdocs.static.images' 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 'openstackdocstheme.theme.starlingxdocs.static.images' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.starlingxdocs.static.images' 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 'openstackdocstheme.theme.starlingxdocs_pdf' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'openstackdocstheme.theme.starlingxdocs_pdf' 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 'openstackdocstheme.theme.starlingxdocs_pdf' 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 'openstackdocstheme.theme.starlingxdocs_pdf' to be distributed and are already explicitly excluding 'openstackdocstheme.theme.starlingxdocs_pdf' 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) INFO:root:creating build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/css.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/footer.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/header.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/layout.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/license_cc.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/localtoc.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/os_search.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/os_search_install.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/os_search_mobile.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/script_footer.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/script_search.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/search.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/sidebartoc.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/sidebartoc_menu.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/sidebartoc_menu_apiref.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/theme.conf -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:copying openstackdocstheme/theme/openstackdocs/titlerow.html -> build/lib/openstackdocstheme/theme/openstackdocs INFO:root:creating build/lib/openstackdocstheme/theme/openstackdocs/static INFO:root:copying openstackdocstheme/theme/openstackdocs/static/favicon.ico -> build/lib/openstackdocstheme/theme/openstackdocs/static INFO:root:creating build/lib/openstackdocstheme/theme/openstackdocs/static/css INFO:root:copying openstackdocstheme/theme/openstackdocs/static/css/bootstrap.css -> build/lib/openstackdocstheme/theme/openstackdocs/static/css INFO:root:copying openstackdocstheme/theme/openstackdocs/static/css/bootstrap.min.css -> build/lib/openstackdocstheme/theme/openstackdocs/static/css INFO:root:copying openstackdocstheme/theme/openstackdocs/static/css/combined.css -> build/lib/openstackdocstheme/theme/openstackdocs/static/css INFO:root:copying openstackdocstheme/theme/openstackdocs/static/css/font-awesome.css -> build/lib/openstackdocstheme/theme/openstackdocs/static/css INFO:root:copying openstackdocstheme/theme/openstackdocs/static/css/font-awesome.min.css -> build/lib/openstackdocstheme/theme/openstackdocs/static/css INFO:root:copying openstackdocstheme/theme/openstackdocs/static/css/search.css -> build/lib/openstackdocstheme/theme/openstackdocs/static/css INFO:root:creating build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/.gitkeep -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/FontAwesome.otf -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/fontawesome-webfont.eot -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/fontawesome-webfont.svg -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/fontawesome-webfont.ttf -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/fontawesome-webfont.woff -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/fontawesome-webfont.woff2 -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/glyphicons-halflings-regular.eot -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/glyphicons-halflings-regular.svg -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/glyphicons-halflings-regular.ttf -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/glyphicons-halflings-regular.woff -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:copying openstackdocstheme/theme/openstackdocs/static/fonts/glyphicons-halflings-regular.woff2 -> build/lib/openstackdocstheme/theme/openstackdocs/static/fonts INFO:root:creating build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/footer-facebook-hover.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/footer-facebook.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/footer-linkedin-hover.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/footer-linkedin.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/footer-twitter-hover.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/footer-twitter.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/footer-youtube-hover.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/footer-youtube.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/loading.gif -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/logo-full.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/logo-full.svg -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/logo-vert.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/logo-vert.svg -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/openstack-logo-full.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/openstack-logo-full.svg -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/openstack-logo-vert.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/openstack-logo-vert.svg -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/search-icon.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images INFO:root:creating build/lib/openstackdocstheme/theme/openstackdocs/static/images/docs INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/docs/license.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images/docs INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/docs/superuser1.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images/docs INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/docs/superuser2.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images/docs INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/docs/superuser3.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images/docs INFO:root:copying openstackdocstheme/theme/openstackdocs/static/images/docs/superuser4.png -> build/lib/openstackdocstheme/theme/openstackdocs/static/images/docs INFO:root:creating build/lib/openstackdocstheme/theme/openstackdocs/static/js INFO:root:copying openstackdocstheme/theme/openstackdocs/static/js/bootstrap.js -> build/lib/openstackdocstheme/theme/openstackdocs/static/js INFO:root:copying openstackdocstheme/theme/openstackdocs/static/js/bootstrap.min.js -> build/lib/openstackdocstheme/theme/openstackdocs/static/js INFO:root:copying openstackdocstheme/theme/openstackdocs/static/js/docs.js -> build/lib/openstackdocstheme/theme/openstackdocs/static/js INFO:root:copying openstackdocstheme/theme/openstackdocs/static/js/jquery-3.2.1.js -> build/lib/openstackdocstheme/theme/openstackdocs/static/js INFO:root:copying openstackdocstheme/theme/openstackdocs/static/js/jquery-3.2.1.min.js -> build/lib/openstackdocstheme/theme/openstackdocs/static/js INFO:root:copying openstackdocstheme/theme/openstackdocs/static/js/navigation.js -> build/lib/openstackdocstheme/theme/openstackdocs/static/js INFO:root:creating build/lib/openstackdocstheme/theme/openstackdocs_pdf INFO:root:copying openstackdocstheme/theme/openstackdocs_pdf/logo-full.png -> build/lib/openstackdocstheme/theme/openstackdocs_pdf INFO:root:copying openstackdocstheme/theme/openstackdocs_pdf/pdftheme.sty -> build/lib/openstackdocstheme/theme/openstackdocs_pdf INFO:root:creating build/lib/openstackdocstheme/theme/starlingxdocs INFO:root:copying openstackdocstheme/theme/starlingxdocs/footer.html -> build/lib/openstackdocstheme/theme/starlingxdocs INFO:root:copying openstackdocstheme/theme/starlingxdocs/header.html -> build/lib/openstackdocstheme/theme/starlingxdocs INFO:root:copying openstackdocstheme/theme/starlingxdocs/sidebartoc_menu.html -> build/lib/openstackdocstheme/theme/starlingxdocs INFO:root:copying openstackdocstheme/theme/starlingxdocs/sidebartoc_menu_apiref.html -> build/lib/openstackdocstheme/theme/starlingxdocs INFO:root:copying openstackdocstheme/theme/starlingxdocs/stx_search.html -> build/lib/openstackdocstheme/theme/starlingxdocs INFO:root:copying openstackdocstheme/theme/starlingxdocs/stx_search_install.html -> build/lib/openstackdocstheme/theme/starlingxdocs INFO:root:copying openstackdocstheme/theme/starlingxdocs/stx_search_mobile.html -> build/lib/openstackdocstheme/theme/starlingxdocs INFO:root:copying openstackdocstheme/theme/starlingxdocs/theme.conf -> build/lib/openstackdocstheme/theme/starlingxdocs INFO:root:copying openstackdocstheme/theme/starlingxdocs/titlerow.html -> build/lib/openstackdocstheme/theme/starlingxdocs INFO:root:creating build/lib/openstackdocstheme/theme/starlingxdocs/static/css INFO:root:copying openstackdocstheme/theme/starlingxdocs/static/css/combined.css -> build/lib/openstackdocstheme/theme/starlingxdocs/static/css INFO:root:creating build/lib/openstackdocstheme/theme/starlingxdocs/static/images INFO:root:copying openstackdocstheme/theme/starlingxdocs/static/images/StarlingX_Logo_RGB_Horizontal_2color.png -> build/lib/openstackdocstheme/theme/starlingxdocs/static/images INFO:root:copying openstackdocstheme/theme/starlingxdocs/static/images/StarlingX_Logo_RGB_Horizontal_2color.svg -> build/lib/openstackdocstheme/theme/starlingxdocs/static/images INFO:root:copying openstackdocstheme/theme/starlingxdocs/static/images/StarlingX_Logo_RGB_Stacked_2color.png -> build/lib/openstackdocstheme/theme/starlingxdocs/static/images INFO:root:copying openstackdocstheme/theme/starlingxdocs/static/images/StarlingX_Logo_RGB_Stacked_2color.svg -> build/lib/openstackdocstheme/theme/starlingxdocs/static/images INFO:root:copying openstackdocstheme/theme/starlingxdocs/static/images/logo-full.png -> build/lib/openstackdocstheme/theme/starlingxdocs/static/images INFO:root:copying openstackdocstheme/theme/starlingxdocs/static/images/logo-full.svg -> build/lib/openstackdocstheme/theme/starlingxdocs/static/images INFO:root:copying openstackdocstheme/theme/starlingxdocs/static/images/logo-vert.png -> build/lib/openstackdocstheme/theme/starlingxdocs/static/images INFO:root:copying openstackdocstheme/theme/starlingxdocs/static/images/logo-vert.svg -> build/lib/openstackdocstheme/theme/starlingxdocs/static/images INFO:root:creating build/lib/openstackdocstheme/theme/starlingxdocs_pdf INFO:root:copying openstackdocstheme/theme/starlingxdocs_pdf/logo-full.png -> build/lib/openstackdocstheme/theme/starlingxdocs_pdf INFO:root:copying openstackdocstheme/theme/starlingxdocs_pdf/logo-full.svg -> build/lib/openstackdocstheme/theme/starlingxdocs_pdf INFO:root:copying openstackdocstheme/theme/starlingxdocs_pdf/pdftheme.sty -> build/lib/openstackdocstheme/theme/starlingxdocs_pdf INFO:root:running build_scripts INFO:root:creating build/scripts-3.13 INFO:root:copying bin/docstheme-build-translated.sh -> build/scripts-3.13 INFO:root:copying and adjusting bin/docstheme-lang-display-name.py -> build/scripts-3.13 INFO:root:copying bin/docstheme-build-pdf -> build/scripts-3.13 INFO:root:changing mode of build/scripts-3.13/docstheme-lang-display-name.py from 644 to 755 Traceback (most recent call last): File "/usr/bin/sphinx-build", line 5, in from sphinx.cmd.build import main ModuleNotFoundError: No module named 'sphinx' ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Build failed, check /var/lib/archbuild/extra-staging-with-build-support-pentium4/build/build used straw: :with_build_support:without_check: build@euronuc.lan