>>> py3-pyroma: Building testing/py3-pyroma 2.6-r4 (using abuild 3.11.0_rc13-r0) started Mon, 01 May 2023 12:01:56 +0000 >>> py3-pyroma: Checking sanity of /home/buildozer/aports/testing/py3-pyroma/APKBUILD... >>> py3-pyroma: Analyzing dependencies... >>> py3-pyroma: Installing for build: build-base py3-pygments py3-setuptools py3-docutils python3-dev (1/22) Installing libbz2 (1.0.8-r5) (2/22) Installing gdbm (1.23-r1) (3/22) Installing mpdecimal (2.5.1-r2) (4/22) Installing libpanelw (6.4_p20230429-r0) (5/22) Installing readline (8.2.1-r1) (6/22) Installing sqlite-libs (3.41.2-r2) (7/22) Installing python3 (3.11.3-r10) (8/22) Installing python3-pycache-pyc0 (3.11.3-r10) (9/22) Installing pyc (0.1-r0) (10/22) Installing py3-pygments-pyc (2.15.1-r0) (11/22) Installing python3-pyc (3.11.3-r10) (12/22) Installing py3-pygments (2.15.1-r0) (13/22) Installing py3-parsing (3.0.9-r2) (14/22) Installing py3-parsing-pyc (3.0.9-r2) (15/22) Installing py3-packaging (23.1-r1) (16/22) Installing py3-packaging-pyc (23.1-r1) (17/22) Installing py3-setuptools (67.7.2-r0) (18/22) Installing py3-setuptools-pyc (67.7.2-r0) (19/22) Installing py3-docutils (0.19-r4) (20/22) Installing py3-docutils-pyc (0.19-r4) (21/22) Installing python3-dev (3.11.3-r10) (22/22) Installing .makedepends-py3-pyroma (20230501.120201) Executing busybox-1.36.0-r8.trigger OK: 1178 MiB in 125 packages >>> py3-pyroma: Cleaning up srcdir >>> py3-pyroma: Cleaning up pkgdir >>> py3-pyroma: Fetching https://distfiles.alpinelinux.org/distfiles/edge/py3-pyroma-2.6.tar.gz >>> py3-pyroma: Fetching https://distfiles.alpinelinux.org/distfiles/edge/py3-pyroma-2.6.tar.gz >>> py3-pyroma: Checking sha512sums... py3-pyroma-2.6.tar.gz: OK >>> py3-pyroma: Unpacking /var/cache/distfiles/py3-pyroma-2.6.tar.gz... running build running build_py creating build creating build/lib creating build/lib/pyroma copying pyroma/distributiondata.py -> build/lib/pyroma copying pyroma/projectdata.py -> build/lib/pyroma copying pyroma/tests.py -> build/lib/pyroma copying pyroma/pypidata.py -> build/lib/pyroma copying pyroma/__init__.py -> build/lib/pyroma copying pyroma/classifiers.py -> build/lib/pyroma copying pyroma/ratings.py -> build/lib/pyroma running egg_info creating pyroma.egg-info writing pyroma.egg-info/PKG-INFO writing dependency_links to pyroma.egg-info/dependency_links.txt writing entry points to pyroma.egg-info/entry_points.txt writing requirements to pyroma.egg-info/requires.txt writing top-level names to pyroma.egg-info/top_level.txt writing manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'pyroma/testdata/complete/*.egg' warning: no files found matching 'tox.ini' adding license file 'LICENSE.txt' writing manifest file 'pyroma.egg-info/SOURCES.txt' /usr/lib/python3.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete' 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 'pyroma.testdata.complete' 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 'pyroma.testdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.complete.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.complete.complete' 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 'pyroma.testdata.complete.complete' 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 'pyroma.testdata.complete.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.complete.complete' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.custom_test' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_test' 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 'pyroma.testdata.custom_test' 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 'pyroma.testdata.custom_test' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_test' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.custom_test.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.custom_test.minimal' 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 'pyroma.testdata.custom_test.minimal' 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 'pyroma.testdata.custom_test.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.custom_test.minimal' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.distributions' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.distributions' 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 'pyroma.testdata.distributions' 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 'pyroma.testdata.distributions' to be distributed and are already explicitly excluding 'pyroma.testdata.distributions' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking' 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 'pyroma.testdata.lacking' 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 'pyroma.testdata.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.lacking.lacking' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.lacking.lacking' 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 'pyroma.testdata.lacking.lacking' 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 'pyroma.testdata.lacking.lacking' to be distributed and are already explicitly excluding 'pyroma.testdata.lacking.lacking' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal' 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 'pyroma.testdata.minimal' 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 'pyroma.testdata.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.minimal.minimal' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.minimal.minimal' 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 'pyroma.testdata.minimal.minimal' 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 'pyroma.testdata.minimal.minimal' to be distributed and are already explicitly excluding 'pyroma.testdata.minimal.minimal' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config' 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 'pyroma.testdata.only_config' 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 'pyroma.testdata.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.only_config.only_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.only_config.only_config' 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 'pyroma.testdata.only_config.only_config' 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 'pyroma.testdata.only_config.only_config' to be distributed and are already explicitly excluding 'pyroma.testdata.only_config.only_config' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config' 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 'pyroma.testdata.setup_config' 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 'pyroma.testdata.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.setup_config.setup_config' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.setup_config.setup_config' 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 'pyroma.testdata.setup_config.setup_config' 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 'pyroma.testdata.setup_config.setup_config' to be distributed and are already explicitly excluding 'pyroma.testdata.setup_config.setup_config' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.xmlrpcdata' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata' 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 'pyroma.testdata.xmlrpcdata' 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 'pyroma.testdata.xmlrpcdata' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.xmlrpcdata.complete' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.complete' 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 'pyroma.testdata.xmlrpcdata.complete' 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 'pyroma.testdata.xmlrpcdata.complete' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.complete' 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.11/site-packages/setuptools/command/build_py.py:201: _Warning: Package 'pyroma.testdata.xmlrpcdata.distribute' is absent from the `packages` configuration. !! ******************************************************************************** ############################ # Package would be ignored # ############################ Python recognizes 'pyroma.testdata.xmlrpcdata.distribute' 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 'pyroma.testdata.xmlrpcdata.distribute' 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 'pyroma.testdata.xmlrpcdata.distribute' to be distributed and are already explicitly excluding 'pyroma.testdata.xmlrpcdata.distribute' 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/pyroma/testdata creating build/lib/pyroma/testdata/complete copying pyroma/testdata/complete/README.txt -> build/lib/pyroma/testdata/complete copying pyroma/testdata/complete/setup.cfg -> build/lib/pyroma/testdata/complete copying pyroma/testdata/complete/setup.py -> build/lib/pyroma/testdata/complete creating build/lib/pyroma/testdata/complete/complete copying pyroma/testdata/complete/complete/__init__.py -> build/lib/pyroma/testdata/complete/complete copying pyroma/testdata/complete/complete/tests.py -> build/lib/pyroma/testdata/complete/complete creating build/lib/pyroma/testdata/custom_test copying pyroma/testdata/custom_test/setup.cfg -> build/lib/pyroma/testdata/custom_test copying pyroma/testdata/custom_test/setup.py -> build/lib/pyroma/testdata/custom_test creating build/lib/pyroma/testdata/custom_test/minimal copying pyroma/testdata/custom_test/minimal/__init__.py -> build/lib/pyroma/testdata/custom_test/minimal creating build/lib/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar -> build/lib/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar.bz2 -> build/lib/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.tar.gz -> build/lib/pyroma/testdata/distributions copying pyroma/testdata/distributions/complete-1.0.dev1.zip -> build/lib/pyroma/testdata/distributions copying pyroma/testdata/distributions/distribute-0.6.15.tar.gz -> build/lib/pyroma/testdata/distributions creating build/lib/pyroma/testdata/lacking copying pyroma/testdata/lacking/setup.cfg -> build/lib/pyroma/testdata/lacking copying pyroma/testdata/lacking/setup.py -> build/lib/pyroma/testdata/lacking creating build/lib/pyroma/testdata/lacking/lacking copying pyroma/testdata/lacking/lacking/__init__.py -> build/lib/pyroma/testdata/lacking/lacking creating build/lib/pyroma/testdata/minimal copying pyroma/testdata/minimal/setup.cfg -> build/lib/pyroma/testdata/minimal copying pyroma/testdata/minimal/setup.py -> build/lib/pyroma/testdata/minimal creating build/lib/pyroma/testdata/minimal/minimal copying pyroma/testdata/minimal/minimal/__init__.py -> build/lib/pyroma/testdata/minimal/minimal creating build/lib/pyroma/testdata/only_config copying pyroma/testdata/only_config/README.txt -> build/lib/pyroma/testdata/only_config copying pyroma/testdata/only_config/setup.cfg -> build/lib/pyroma/testdata/only_config creating build/lib/pyroma/testdata/only_config/only_config copying pyroma/testdata/only_config/only_config/__init__.py -> build/lib/pyroma/testdata/only_config/only_config creating build/lib/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/README.txt -> build/lib/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/setup.cfg -> build/lib/pyroma/testdata/setup_config copying pyroma/testdata/setup_config/setup.py -> build/lib/pyroma/testdata/setup_config creating build/lib/pyroma/testdata/setup_config/setup_config copying pyroma/testdata/setup_config/setup_config/__init__.py -> build/lib/pyroma/testdata/setup_config/setup_config creating build/lib/pyroma/testdata/xmlrpcdata copying pyroma/testdata/xmlrpcdata/completedata.py -> build/lib/pyroma/testdata/xmlrpcdata copying pyroma/testdata/xmlrpcdata/distributedata.py -> build/lib/pyroma/testdata/xmlrpcdata creating build/lib/pyroma/testdata/xmlrpcdata/complete copying pyroma/testdata/xmlrpcdata/complete/1.0.dev1.html -> build/lib/pyroma/testdata/xmlrpcdata/complete creating build/lib/pyroma/testdata/xmlrpcdata/distribute copying pyroma/testdata/xmlrpcdata/distribute/0.6.15.html -> build/lib/pyroma/testdata/xmlrpcdata/distribute >>> py3-pyroma: Entering fakeroot... running install /usr/lib/python3.11/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, pypa/build or other standards-based tools. See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details. ******************************************************************************** !! self.initialize_options() running install_lib creating /home/buildozer/aports/testing/py3-pyroma/pkg creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11 creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma copying build/lib/pyroma/distributiondata.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma copying build/lib/pyroma/projectdata.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma copying build/lib/pyroma/tests.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma copying build/lib/pyroma/pypidata.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma copying build/lib/pyroma/__init__.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma copying build/lib/pyroma/classifiers.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/only_config creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/only_config/only_config copying build/lib/pyroma/testdata/only_config/only_config/__init__.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/only_config/only_config copying build/lib/pyroma/testdata/only_config/setup.cfg -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/only_config copying build/lib/pyroma/testdata/only_config/README.txt -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/only_config creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/distributions copying build/lib/pyroma/testdata/distributions/complete-1.0.dev1.zip -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/distributions copying build/lib/pyroma/testdata/distributions/distribute-0.6.15.tar.gz -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/distributions copying build/lib/pyroma/testdata/distributions/complete-1.0.dev1.tar -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/distributions copying build/lib/pyroma/testdata/distributions/complete-1.0.dev1.tar.bz2 -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/distributions copying build/lib/pyroma/testdata/distributions/complete-1.0.dev1.tar.gz -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/distributions creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/xmlrpcdata copying build/lib/pyroma/testdata/xmlrpcdata/completedata.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/xmlrpcdata creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/xmlrpcdata/distribute copying build/lib/pyroma/testdata/xmlrpcdata/distribute/0.6.15.html -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/xmlrpcdata/distribute creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/xmlrpcdata/complete copying build/lib/pyroma/testdata/xmlrpcdata/complete/1.0.dev1.html -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/xmlrpcdata/complete copying build/lib/pyroma/testdata/xmlrpcdata/distributedata.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/xmlrpcdata creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config copying build/lib/pyroma/testdata/setup_config/setup.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config copying build/lib/pyroma/testdata/setup_config/setup.cfg -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config/setup_config copying build/lib/pyroma/testdata/setup_config/setup_config/__init__.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config/setup_config copying build/lib/pyroma/testdata/setup_config/README.txt -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/minimal copying build/lib/pyroma/testdata/minimal/setup.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/minimal copying build/lib/pyroma/testdata/minimal/setup.cfg -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/minimal creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/minimal/minimal copying build/lib/pyroma/testdata/minimal/minimal/__init__.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/minimal/minimal creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete copying build/lib/pyroma/testdata/complete/setup.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete copying build/lib/pyroma/testdata/complete/setup.cfg -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete/complete copying build/lib/pyroma/testdata/complete/complete/tests.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete/complete copying build/lib/pyroma/testdata/complete/complete/__init__.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete/complete copying build/lib/pyroma/testdata/complete/README.txt -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/custom_test copying build/lib/pyroma/testdata/custom_test/setup.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/custom_test copying build/lib/pyroma/testdata/custom_test/setup.cfg -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/custom_test creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/custom_test/minimal copying build/lib/pyroma/testdata/custom_test/minimal/__init__.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/custom_test/minimal creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/lacking copying build/lib/pyroma/testdata/lacking/setup.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/lacking copying build/lib/pyroma/testdata/lacking/setup.cfg -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/lacking creating /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/lacking/lacking copying build/lib/pyroma/testdata/lacking/lacking/__init__.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/lacking/lacking copying build/lib/pyroma/ratings.py -> /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/distributiondata.py to distributiondata.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/projectdata.py to projectdata.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/tests.py to tests.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/pypidata.py to pypidata.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/classifiers.py to classifiers.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/only_config/only_config/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/xmlrpcdata/completedata.py to completedata.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/xmlrpcdata/distributedata.py to distributedata.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config/setup.py to setup.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config/setup_config/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/minimal/setup.py to setup.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/minimal/minimal/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete/setup.py to setup.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete/complete/tests.py to tests.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete/complete/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/custom_test/setup.py to setup.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/custom_test/minimal/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/lacking/setup.py to setup.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/lacking/lacking/__init__.py to __init__.cpython-311.pyc byte-compiling /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/ratings.py to ratings.cpython-311.pyc running install_egg_info running egg_info writing pyroma.egg-info/PKG-INFO writing dependency_links to pyroma.egg-info/dependency_links.txt writing entry points to pyroma.egg-info/entry_points.txt writing requirements to pyroma.egg-info/requires.txt writing top-level names to pyroma.egg-info/top_level.txt reading manifest file 'pyroma.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' no previously-included directories found matching 'pyroma/testdata/complete/*.egg' warning: no files found matching 'tox.ini' adding license file 'LICENSE.txt' writing manifest file 'pyroma.egg-info/SOURCES.txt' Copying pyroma.egg-info to /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma-2.6-py3.11.egg-info running install_scripts Installing pyroma script to /home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/bin >>> py3-pyroma-pyc*: Running split function pyc... '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/only_config/only_config/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/only_config/only_config/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/xmlrpcdata/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/xmlrpcdata/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config/setup_config/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/setup_config/setup_config/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/minimal/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/minimal/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/minimal/minimal/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/minimal/minimal/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/complete/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/complete/complete/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/complete/complete/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/custom_test/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/custom_test/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/custom_test/minimal/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/custom_test/minimal/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/lacking/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/lacking/__pycache__' '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma/usr/lib/python3.11/site-packages/pyroma/testdata/lacking/lacking/__pycache__' -> '/home/buildozer/aports/testing/py3-pyroma/pkg/py3-pyroma-pyc/usr/lib/python3.11/site-packages/pyroma/testdata/lacking/lacking/__pycache__' >>> py3-pyroma-pyc*: Preparing subpackage py3-pyroma-pyc... >>> py3-pyroma-pyc*: Running postcheck for py3-pyroma-pyc >>> py3-pyroma*: Running postcheck for py3-pyroma >>> py3-pyroma*: Preparing package py3-pyroma... >>> py3-pyroma-pyc*: Tracing dependencies... py3-pygments py3-setuptools py3-docutils python3~3.11 >>> py3-pyroma-pyc*: Package size: 288.0 KB >>> py3-pyroma-pyc*: Compressing data... >>> py3-pyroma-pyc*: Create checksum... >>> py3-pyroma-pyc*: Create py3-pyroma-pyc-2.6-r4.apk >>> py3-pyroma*: Tracing dependencies... py3-pygments py3-setuptools py3-docutils python3~3.11 >>> py3-pyroma*: Package size: 736.0 KB >>> py3-pyroma*: Compressing data... >>> py3-pyroma*: Create checksum... >>> py3-pyroma*: Create py3-pyroma-2.6-r4.apk >>> py3-pyroma: Build complete at Mon, 01 May 2023 12:02:12 +0000 elapsed time 0h 0m 16s >>> py3-pyroma: Cleaning up srcdir >>> py3-pyroma: Cleaning up pkgdir >>> py3-pyroma: Uninstalling dependencies... (1/22) Purging .makedepends-py3-pyroma (20230501.120201) (2/22) Purging py3-pygments-pyc (2.15.1-r0) (3/22) Purging py3-pygments (2.15.1-r0) (4/22) Purging py3-setuptools-pyc (67.7.2-r0) (5/22) Purging py3-setuptools (67.7.2-r0) (6/22) Purging py3-packaging-pyc (23.1-r1) (7/22) Purging py3-packaging (23.1-r1) (8/22) Purging py3-parsing-pyc (3.0.9-r2) (9/22) Purging py3-parsing (3.0.9-r2) (10/22) Purging py3-docutils-pyc (0.19-r4) (11/22) Purging py3-docutils (0.19-r4) (12/22) Purging python3-dev (3.11.3-r10) (13/22) Purging python3-pyc (3.11.3-r10) (14/22) Purging python3-pycache-pyc0 (3.11.3-r10) (15/22) Purging pyc (0.1-r0) (16/22) Purging python3 (3.11.3-r10) (17/22) Purging gdbm (1.23-r1) (18/22) Purging libbz2 (1.0.8-r5) (19/22) Purging libpanelw (6.4_p20230429-r0) (20/22) Purging mpdecimal (2.5.1-r2) (21/22) Purging readline (8.2.1-r1) (22/22) Purging sqlite-libs (3.41.2-r2) Executing busybox-1.36.0-r8.trigger OK: 966 MiB in 103 packages >>> py3-pyroma: Updating the testing/riscv64 repository index... >>> py3-pyroma: Signing the index...