>>> py3-boto3: Building community/py3-boto3 1.37.28-r0 (using abuild 3.15.0_rc3-r1) started Mon, 28 Apr 2025 08:30:39 +0000
>>> py3-boto3: Validating /home/buildozer/aports/community/py3-boto3/APKBUILD...
>>> py3-boto3: Analyzing dependencies...
>>> py3-boto3: Installing for build: build-base py3-botocore py3-jmespath py3-s3transfer py3-gpep517 py3-setuptools py3-wheel
(1/38) Installing libbz2 (1.0.8-r6)
(2/38) Installing libffi (3.4.8-r0)
(3/38) Installing gdbm (1.24-r0)
(4/38) Installing xz-libs (5.8.1-r0)
(5/38) Installing mpdecimal (4.0.0-r0)
(6/38) Installing libpanelw (6.5_p20250412-r0)
(7/38) Installing sqlite-libs (3.49.1-r0)
(8/38) Installing python3 (3.12.10-r0)
(9/38) Installing python3-pycache-pyc0 (3.12.10-r0)
(10/38) Installing pyc (3.12.10-r0)
(11/38) Installing py3-certifi-pyc (2024.12.14-r0)
(12/38) Installing py3-six (1.17.0-r0)
(13/38) Installing py3-six-pyc (1.17.0-r0)
(14/38) Installing py3-dateutil (2.9.0-r1)
(15/38) Installing py3-dateutil-pyc (2.9.0-r1)
(16/38) Installing py3-jmespath (1.0.1-r4)
(17/38) Installing py3-jmespath-pyc (1.0.1-r4)
(18/38) Installing py3-urllib3 (1.26.20-r0)
(19/38) Installing py3-urllib3-pyc (1.26.20-r0)
(20/38) Installing py3-botocore-pyc (1.37.28-r0)
(21/38) Installing python3-pyc (3.12.10-r0)
(22/38) Installing py3-certifi (2024.12.14-r0)
(23/38) Installing py3-botocore (1.37.28-r0)
(24/38) Installing py3-s3transfer (0.10.1-r0)
(25/38) Installing py3-s3transfer-pyc (0.10.1-r0)
(26/38) Installing py3-installer (0.7.0-r2)
(27/38) Installing py3-installer-pyc (0.7.0-r2)
(28/38) Installing py3-gpep517 (16-r0)
(29/38) Installing py3-gpep517-pyc (16-r0)
(30/38) Installing py3-parsing (3.2.0-r0)
(31/38) Installing py3-parsing-pyc (3.2.0-r0)
(32/38) Installing py3-packaging (25.0-r0)
(33/38) Installing py3-packaging-pyc (25.0-r0)
(34/38) Installing py3-setuptools (77.0.3-r0)
(35/38) Installing py3-setuptools-pyc (77.0.3-r0)
(36/38) Installing py3-wheel (0.43.0-r0)
(37/38) Installing py3-wheel-pyc (0.43.0-r0)
(38/38) Installing .makedepends-py3-boto3 (20250428.083045)
Executing busybox-1.37.0-r16.trigger
OK: 486 MiB in 137 packages
>>> py3-boto3: Cleaning up srcdir
>>> py3-boto3: Cleaning up pkgdir
>>> py3-boto3: Cleaning up tmpdir
>>> py3-boto3: Fetching https://distfiles.alpinelinux.org/distfiles/v3.22/boto3-1.37.28.tar.gz
Connecting to distfiles.alpinelinux.org (172.105.82.32:443)
saving to '/var/cache/distfiles/v3.22/boto3-1.37.28.tar.gz.part'
boto3-1.37.28.tar.gz 100% |********************************|  108k  0:00:00 ETA
'/var/cache/distfiles/v3.22/boto3-1.37.28.tar.gz.part' saved
>>> py3-boto3: Fetching https://distfiles.alpinelinux.org/distfiles/v3.22/boto3-1.37.28.tar.gz
>>> py3-boto3: Checking sha512sums...
boto3-1.37.28.tar.gz: OK
>>> py3-boto3: Unpacking /var/cache/distfiles/v3.22/boto3-1.37.28.tar.gz...
2025-04-28 08:30:50,764 gpep517 INFO Building wheel via backend setuptools.build_meta:__legacy__
/usr/lib/python3.12/site-packages/setuptools/dist.py:760: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

        ********************************************************************************
        Please consider removing the following classifiers in favor of a SPDX license expression:

        License :: OSI Approved :: Apache Software License

        See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
        ********************************************************************************

!!
  self._finalize_license_expression()
2025-04-28 08:30:50,910 root INFO running bdist_wheel
2025-04-28 08:30:51,000 root INFO running build
2025-04-28 08:30:51,000 root INFO running build_py
2025-04-28 08:30:51,021 root INFO creating build/lib/boto3
2025-04-28 08:30:51,022 root INFO copying boto3/__init__.py -> build/lib/boto3
2025-04-28 08:30:51,024 root INFO copying boto3/exceptions.py -> build/lib/boto3
2025-04-28 08:30:51,026 root INFO copying boto3/session.py -> build/lib/boto3
2025-04-28 08:30:51,028 root INFO copying boto3/crt.py -> build/lib/boto3
2025-04-28 08:30:51,030 root INFO copying boto3/utils.py -> build/lib/boto3
2025-04-28 08:30:51,032 root INFO copying boto3/compat.py -> build/lib/boto3
2025-04-28 08:30:51,034 root INFO creating build/lib/boto3/ec2
2025-04-28 08:30:51,035 root INFO copying boto3/ec2/__init__.py -> build/lib/boto3/ec2
2025-04-28 08:30:51,036 root INFO copying boto3/ec2/deletetags.py -> build/lib/boto3/ec2
2025-04-28 08:30:51,038 root INFO copying boto3/ec2/createtags.py -> build/lib/boto3/ec2
2025-04-28 08:30:51,040 root INFO creating build/lib/boto3/dynamodb
2025-04-28 08:30:51,041 root INFO copying boto3/dynamodb/__init__.py -> build/lib/boto3/dynamodb
2025-04-28 08:30:51,043 root INFO copying boto3/dynamodb/conditions.py -> build/lib/boto3/dynamodb
2025-04-28 08:30:51,045 root INFO copying boto3/dynamodb/transform.py -> build/lib/boto3/dynamodb
2025-04-28 08:30:51,047 root INFO copying boto3/dynamodb/table.py -> build/lib/boto3/dynamodb
2025-04-28 08:30:51,048 root INFO copying boto3/dynamodb/types.py -> build/lib/boto3/dynamodb
2025-04-28 08:30:51,051 root INFO creating build/lib/boto3/resources
2025-04-28 08:30:51,052 root INFO copying boto3/resources/__init__.py -> build/lib/boto3/resources
2025-04-28 08:30:51,053 root INFO copying boto3/resources/params.py -> build/lib/boto3/resources
2025-04-28 08:30:51,055 root INFO copying boto3/resources/collection.py -> build/lib/boto3/resources
2025-04-28 08:30:51,057 root INFO copying boto3/resources/factory.py -> build/lib/boto3/resources
2025-04-28 08:30:51,058 root INFO copying boto3/resources/response.py -> build/lib/boto3/resources
2025-04-28 08:30:51,060 root INFO copying boto3/resources/action.py -> build/lib/boto3/resources
2025-04-28 08:30:51,062 root INFO copying boto3/resources/model.py -> build/lib/boto3/resources
2025-04-28 08:30:51,063 root INFO copying boto3/resources/base.py -> build/lib/boto3/resources
2025-04-28 08:30:51,065 root INFO creating build/lib/boto3/s3
2025-04-28 08:30:51,066 root INFO copying boto3/s3/__init__.py -> build/lib/boto3/s3
2025-04-28 08:30:51,068 root INFO copying boto3/s3/transfer.py -> build/lib/boto3/s3
2025-04-28 08:30:51,070 root INFO copying boto3/s3/constants.py -> build/lib/boto3/s3
2025-04-28 08:30:51,071 root INFO copying boto3/s3/inject.py -> build/lib/boto3/s3
2025-04-28 08:30:51,074 root INFO creating build/lib/boto3/docs
2025-04-28 08:30:51,075 root INFO copying boto3/docs/attr.py -> build/lib/boto3/docs
2025-04-28 08:30:51,076 root INFO copying boto3/docs/__init__.py -> build/lib/boto3/docs
2025-04-28 08:30:51,078 root INFO copying boto3/docs/subresource.py -> build/lib/boto3/docs
2025-04-28 08:30:51,080 root INFO copying boto3/docs/collection.py -> build/lib/boto3/docs
2025-04-28 08:30:51,081 root INFO copying boto3/docs/resource.py -> build/lib/boto3/docs
2025-04-28 08:30:51,083 root INFO copying boto3/docs/waiter.py -> build/lib/boto3/docs
2025-04-28 08:30:51,084 root INFO copying boto3/docs/service.py -> build/lib/boto3/docs
2025-04-28 08:30:51,086 root INFO copying boto3/docs/method.py -> build/lib/boto3/docs
2025-04-28 08:30:51,088 root INFO copying boto3/docs/utils.py -> build/lib/boto3/docs
2025-04-28 08:30:51,089 root INFO copying boto3/docs/action.py -> build/lib/boto3/docs
2025-04-28 08:30:51,091 root INFO copying boto3/docs/base.py -> build/lib/boto3/docs
2025-04-28 08:30:51,092 root INFO copying boto3/docs/client.py -> build/lib/boto3/docs
2025-04-28 08:30:51,094 root INFO copying boto3/docs/docstring.py -> build/lib/boto3/docs
2025-04-28 08:30:51,095 root INFO running egg_info
2025-04-28 08:30:51,112 root INFO writing boto3.egg-info/PKG-INFO
2025-04-28 08:30:51,117 root INFO writing dependency_links to boto3.egg-info/dependency_links.txt
2025-04-28 08:30:51,121 root INFO writing requirements to boto3.egg-info/requires.txt
2025-04-28 08:30:51,122 root INFO writing top-level names to boto3.egg-info/top_level.txt
2025-04-28 08:30:51,150 root INFO reading manifest file 'boto3.egg-info/SOURCES.txt'
2025-04-28 08:30:51,159 root INFO reading manifest template 'MANIFEST.in'
2025-04-28 08:30:51,167 root INFO adding license file 'LICENSE'
2025-04-28 08:30:51,168 root INFO adding license file 'NOTICE'
2025-04-28 08:30:51,176 root INFO writing manifest file 'boto3.egg-info/SOURCES.txt'
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.cloudformation' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'boto3.data.cloudformation' 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 'boto3.data.cloudformation' 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 'boto3.data.cloudformation' to be distributed and are
        already explicitly excluding 'boto3.data.cloudformation' 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.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.cloudwatch' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'boto3.data.cloudwatch' 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 'boto3.data.cloudwatch' 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 'boto3.data.cloudwatch' to be distributed and are
        already explicitly excluding 'boto3.data.cloudwatch' 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.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.dynamodb' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'boto3.data.dynamodb' 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 'boto3.data.dynamodb' 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 'boto3.data.dynamodb' to be distributed and are
        already explicitly excluding 'boto3.data.dynamodb' 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.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.ec2' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'boto3.data.ec2' 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 'boto3.data.ec2' 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 'boto3.data.ec2' to be distributed and are
        already explicitly excluding 'boto3.data.ec2' 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.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.glacier' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'boto3.data.glacier' 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 'boto3.data.glacier' 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 'boto3.data.glacier' to be distributed and are
        already explicitly excluding 'boto3.data.glacier' 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.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.iam' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'boto3.data.iam' 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 'boto3.data.iam' 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 'boto3.data.iam' to be distributed and are
        already explicitly excluding 'boto3.data.iam' 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.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.opsworks' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'boto3.data.opsworks' 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 'boto3.data.opsworks' 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 'boto3.data.opsworks' to be distributed and are
        already explicitly excluding 'boto3.data.opsworks' 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.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.s3' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'boto3.data.s3' 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 'boto3.data.s3' 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 'boto3.data.s3' to be distributed and are
        already explicitly excluding 'boto3.data.s3' 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.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.sns' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'boto3.data.sns' 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 'boto3.data.sns' 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 'boto3.data.sns' to be distributed and are
        already explicitly excluding 'boto3.data.sns' 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.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.sqs' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'boto3.data.sqs' 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 'boto3.data.sqs' 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 'boto3.data.sqs' to be distributed and are
        already explicitly excluding 'boto3.data.sqs' 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.12/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.examples' is absent from the `packages` configuration.
!!

        ********************************************************************************
        ############################
        # Package would be ignored #
        ############################
        Python recognizes 'boto3.examples' 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 'boto3.examples' 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 'boto3.examples' to be distributed and are
        already explicitly excluding 'boto3.examples' 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)
2025-04-28 08:30:51,194 root INFO creating build/lib/boto3/data/cloudformation/2010-05-15
2025-04-28 08:30:51,196 root INFO copying boto3/data/cloudformation/2010-05-15/resources-1.json -> build/lib/boto3/data/cloudformation/2010-05-15
2025-04-28 08:30:51,197 root INFO creating build/lib/boto3/data/cloudwatch/2010-08-01
2025-04-28 08:30:51,199 root INFO copying boto3/data/cloudwatch/2010-08-01/resources-1.json -> build/lib/boto3/data/cloudwatch/2010-08-01
2025-04-28 08:30:51,200 root INFO creating build/lib/boto3/data/dynamodb/2012-08-10
2025-04-28 08:30:51,201 root INFO copying boto3/data/dynamodb/2012-08-10/resources-1.json -> build/lib/boto3/data/dynamodb/2012-08-10
2025-04-28 08:30:51,203 root INFO creating build/lib/boto3/data/ec2/2014-10-01
2025-04-28 08:30:51,204 root INFO copying boto3/data/ec2/2014-10-01/resources-1.json -> build/lib/boto3/data/ec2/2014-10-01
2025-04-28 08:30:51,206 root INFO creating build/lib/boto3/data/ec2/2015-03-01
2025-04-28 08:30:51,207 root INFO copying boto3/data/ec2/2015-03-01/resources-1.json -> build/lib/boto3/data/ec2/2015-03-01
2025-04-28 08:30:51,209 root INFO creating build/lib/boto3/data/ec2/2015-04-15
2025-04-28 08:30:51,210 root INFO copying boto3/data/ec2/2015-04-15/resources-1.json -> build/lib/boto3/data/ec2/2015-04-15
2025-04-28 08:30:51,212 root INFO creating build/lib/boto3/data/ec2/2015-10-01
2025-04-28 08:30:51,213 root INFO copying boto3/data/ec2/2015-10-01/resources-1.json -> build/lib/boto3/data/ec2/2015-10-01
2025-04-28 08:30:51,215 root INFO creating build/lib/boto3/data/ec2/2016-04-01
2025-04-28 08:30:51,216 root INFO copying boto3/data/ec2/2016-04-01/resources-1.json -> build/lib/boto3/data/ec2/2016-04-01
2025-04-28 08:30:51,218 root INFO creating build/lib/boto3/data/ec2/2016-09-15
2025-04-28 08:30:51,219 root INFO copying boto3/data/ec2/2016-09-15/resources-1.json -> build/lib/boto3/data/ec2/2016-09-15
2025-04-28 08:30:51,221 root INFO creating build/lib/boto3/data/ec2/2016-11-15
2025-04-28 08:30:51,222 root INFO copying boto3/data/ec2/2016-11-15/resources-1.json -> build/lib/boto3/data/ec2/2016-11-15
2025-04-28 08:30:51,224 root INFO creating build/lib/boto3/data/glacier/2012-06-01
2025-04-28 08:30:51,225 root INFO copying boto3/data/glacier/2012-06-01/resources-1.json -> build/lib/boto3/data/glacier/2012-06-01
2025-04-28 08:30:51,227 root INFO creating build/lib/boto3/data/iam/2010-05-08
2025-04-28 08:30:51,228 root INFO copying boto3/data/iam/2010-05-08/resources-1.json -> build/lib/boto3/data/iam/2010-05-08
2025-04-28 08:30:51,230 root INFO creating build/lib/boto3/data/opsworks/2013-02-18
2025-04-28 08:30:51,231 root INFO copying boto3/data/opsworks/2013-02-18/resources-1.json -> build/lib/boto3/data/opsworks/2013-02-18
2025-04-28 08:30:51,233 root INFO creating build/lib/boto3/data/s3/2006-03-01
2025-04-28 08:30:51,234 root INFO copying boto3/data/s3/2006-03-01/resources-1.json -> build/lib/boto3/data/s3/2006-03-01
2025-04-28 08:30:51,236 root INFO creating build/lib/boto3/data/sns/2010-03-31
2025-04-28 08:30:51,237 root INFO copying boto3/data/sns/2010-03-31/resources-1.json -> build/lib/boto3/data/sns/2010-03-31
2025-04-28 08:30:51,239 root INFO creating build/lib/boto3/data/sqs/2012-11-05
2025-04-28 08:30:51,240 root INFO copying boto3/data/sqs/2012-11-05/resources-1.json -> build/lib/boto3/data/sqs/2012-11-05
2025-04-28 08:30:51,242 root INFO creating build/lib/boto3/examples
2025-04-28 08:30:51,243 root INFO copying boto3/examples/cloudfront.rst -> build/lib/boto3/examples
2025-04-28 08:30:51,244 root INFO copying boto3/examples/s3.rst -> build/lib/boto3/examples
2025-04-28 08:30:51,283 root INFO installing to build/bdist.linux-riscv64/wheel
2025-04-28 08:30:51,284 root INFO running install
2025-04-28 08:30:51,350 root INFO running install_lib
2025-04-28 08:30:51,368 root INFO creating build/bdist.linux-riscv64/wheel
2025-04-28 08:30:51,370 root INFO creating build/bdist.linux-riscv64/wheel/boto3
2025-04-28 08:30:51,371 root INFO creating build/bdist.linux-riscv64/wheel/boto3/ec2
2025-04-28 08:30:51,372 root INFO copying build/lib/boto3/ec2/__init__.py -> build/bdist.linux-riscv64/wheel/./boto3/ec2
2025-04-28 08:30:51,374 root INFO copying build/lib/boto3/ec2/deletetags.py -> build/bdist.linux-riscv64/wheel/./boto3/ec2
2025-04-28 08:30:51,375 root INFO copying build/lib/boto3/ec2/createtags.py -> build/bdist.linux-riscv64/wheel/./boto3/ec2
2025-04-28 08:30:51,376 root INFO copying build/lib/boto3/__init__.py -> build/bdist.linux-riscv64/wheel/./boto3
2025-04-28 08:30:51,377 root INFO copying build/lib/boto3/exceptions.py -> build/bdist.linux-riscv64/wheel/./boto3
2025-04-28 08:30:51,379 root INFO creating build/bdist.linux-riscv64/wheel/boto3/dynamodb
2025-04-28 08:30:51,380 root INFO copying build/lib/boto3/dynamodb/__init__.py -> build/bdist.linux-riscv64/wheel/./boto3/dynamodb
2025-04-28 08:30:51,381 root INFO copying build/lib/boto3/dynamodb/conditions.py -> build/bdist.linux-riscv64/wheel/./boto3/dynamodb
2025-04-28 08:30:51,382 root INFO copying build/lib/boto3/dynamodb/transform.py -> build/bdist.linux-riscv64/wheel/./boto3/dynamodb
2025-04-28 08:30:51,384 root INFO copying build/lib/boto3/dynamodb/table.py -> build/bdist.linux-riscv64/wheel/./boto3/dynamodb
2025-04-28 08:30:51,385 root INFO copying build/lib/boto3/dynamodb/types.py -> build/bdist.linux-riscv64/wheel/./boto3/dynamodb
2025-04-28 08:30:51,386 root INFO copying build/lib/boto3/session.py -> build/bdist.linux-riscv64/wheel/./boto3
2025-04-28 08:30:51,388 root INFO creating build/bdist.linux-riscv64/wheel/boto3/resources
2025-04-28 08:30:51,389 root INFO copying build/lib/boto3/resources/__init__.py -> build/bdist.linux-riscv64/wheel/./boto3/resources
2025-04-28 08:30:51,390 root INFO copying build/lib/boto3/resources/params.py -> build/bdist.linux-riscv64/wheel/./boto3/resources
2025-04-28 08:30:51,391 root INFO copying build/lib/boto3/resources/collection.py -> build/bdist.linux-riscv64/wheel/./boto3/resources
2025-04-28 08:30:51,393 root INFO copying build/lib/boto3/resources/factory.py -> build/bdist.linux-riscv64/wheel/./boto3/resources
2025-04-28 08:30:51,394 root INFO copying build/lib/boto3/resources/response.py -> build/bdist.linux-riscv64/wheel/./boto3/resources
2025-04-28 08:30:51,395 root INFO copying build/lib/boto3/resources/action.py -> build/bdist.linux-riscv64/wheel/./boto3/resources
2025-04-28 08:30:51,397 root INFO copying build/lib/boto3/resources/model.py -> build/bdist.linux-riscv64/wheel/./boto3/resources
2025-04-28 08:30:51,398 root INFO copying build/lib/boto3/resources/base.py -> build/bdist.linux-riscv64/wheel/./boto3/resources
2025-04-28 08:30:51,399 root INFO copying build/lib/boto3/crt.py -> build/bdist.linux-riscv64/wheel/./boto3
2025-04-28 08:30:51,401 root INFO creating build/bdist.linux-riscv64/wheel/boto3/s3
2025-04-28 08:30:51,402 root INFO copying build/lib/boto3/s3/__init__.py -> build/bdist.linux-riscv64/wheel/./boto3/s3
2025-04-28 08:30:51,403 root INFO copying build/lib/boto3/s3/transfer.py -> build/bdist.linux-riscv64/wheel/./boto3/s3
2025-04-28 08:30:51,405 root INFO copying build/lib/boto3/s3/constants.py -> build/bdist.linux-riscv64/wheel/./boto3/s3
2025-04-28 08:30:51,406 root INFO copying build/lib/boto3/s3/inject.py -> build/bdist.linux-riscv64/wheel/./boto3/s3
2025-04-28 08:30:51,408 root INFO creating build/bdist.linux-riscv64/wheel/boto3/docs
2025-04-28 08:30:51,409 root INFO copying build/lib/boto3/docs/attr.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,410 root INFO copying build/lib/boto3/docs/__init__.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,411 root INFO copying build/lib/boto3/docs/subresource.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,412 root INFO copying build/lib/boto3/docs/collection.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,414 root INFO copying build/lib/boto3/docs/resource.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,415 root INFO copying build/lib/boto3/docs/waiter.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,416 root INFO copying build/lib/boto3/docs/service.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,417 root INFO copying build/lib/boto3/docs/method.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,419 root INFO copying build/lib/boto3/docs/utils.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,420 root INFO copying build/lib/boto3/docs/action.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,421 root INFO copying build/lib/boto3/docs/base.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,422 root INFO copying build/lib/boto3/docs/client.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,424 root INFO copying build/lib/boto3/docs/docstring.py -> build/bdist.linux-riscv64/wheel/./boto3/docs
2025-04-28 08:30:51,425 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data
2025-04-28 08:30:51,426 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/ec2
2025-04-28 08:30:51,428 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/ec2/2015-03-01
2025-04-28 08:30:51,429 root INFO copying build/lib/boto3/data/ec2/2015-03-01/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/ec2/2015-03-01
2025-04-28 08:30:51,431 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/ec2/2016-04-01
2025-04-28 08:30:51,432 root INFO copying build/lib/boto3/data/ec2/2016-04-01/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/ec2/2016-04-01
2025-04-28 08:30:51,434 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/ec2/2015-04-15
2025-04-28 08:30:51,435 root INFO copying build/lib/boto3/data/ec2/2015-04-15/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/ec2/2015-04-15
2025-04-28 08:30:51,437 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/ec2/2015-10-01
2025-04-28 08:30:51,438 root INFO copying build/lib/boto3/data/ec2/2015-10-01/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/ec2/2015-10-01
2025-04-28 08:30:51,440 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/ec2/2016-11-15
2025-04-28 08:30:51,441 root INFO copying build/lib/boto3/data/ec2/2016-11-15/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/ec2/2016-11-15
2025-04-28 08:30:51,443 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/ec2/2016-09-15
2025-04-28 08:30:51,444 root INFO copying build/lib/boto3/data/ec2/2016-09-15/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/ec2/2016-09-15
2025-04-28 08:30:51,446 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/ec2/2014-10-01
2025-04-28 08:30:51,447 root INFO copying build/lib/boto3/data/ec2/2014-10-01/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/ec2/2014-10-01
2025-04-28 08:30:51,450 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/glacier
2025-04-28 08:30:51,451 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/glacier/2012-06-01
2025-04-28 08:30:51,452 root INFO copying build/lib/boto3/data/glacier/2012-06-01/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/glacier/2012-06-01
2025-04-28 08:30:51,454 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/iam
2025-04-28 08:30:51,455 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/iam/2010-05-08
2025-04-28 08:30:51,456 root INFO copying build/lib/boto3/data/iam/2010-05-08/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/iam/2010-05-08
2025-04-28 08:30:51,458 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/sqs
2025-04-28 08:30:51,459 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/sqs/2012-11-05
2025-04-28 08:30:51,460 root INFO copying build/lib/boto3/data/sqs/2012-11-05/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/sqs/2012-11-05
2025-04-28 08:30:51,462 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/dynamodb
2025-04-28 08:30:51,463 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/dynamodb/2012-08-10
2025-04-28 08:30:51,464 root INFO copying build/lib/boto3/data/dynamodb/2012-08-10/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/dynamodb/2012-08-10
2025-04-28 08:30:51,466 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/opsworks
2025-04-28 08:30:51,467 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/opsworks/2013-02-18
2025-04-28 08:30:51,468 root INFO copying build/lib/boto3/data/opsworks/2013-02-18/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/opsworks/2013-02-18
2025-04-28 08:30:51,469 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/cloudformation
2025-04-28 08:30:51,471 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/cloudformation/2010-05-15
2025-04-28 08:30:51,472 root INFO copying build/lib/boto3/data/cloudformation/2010-05-15/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/cloudformation/2010-05-15
2025-04-28 08:30:51,473 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/s3
2025-04-28 08:30:51,475 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/s3/2006-03-01
2025-04-28 08:30:51,476 root INFO copying build/lib/boto3/data/s3/2006-03-01/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/s3/2006-03-01
2025-04-28 08:30:51,477 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/sns
2025-04-28 08:30:51,479 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/sns/2010-03-31
2025-04-28 08:30:51,480 root INFO copying build/lib/boto3/data/sns/2010-03-31/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/sns/2010-03-31
2025-04-28 08:30:51,481 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/cloudwatch
2025-04-28 08:30:51,483 root INFO creating build/bdist.linux-riscv64/wheel/boto3/data/cloudwatch/2010-08-01
2025-04-28 08:30:51,484 root INFO copying build/lib/boto3/data/cloudwatch/2010-08-01/resources-1.json -> build/bdist.linux-riscv64/wheel/./boto3/data/cloudwatch/2010-08-01
2025-04-28 08:30:51,485 root INFO copying build/lib/boto3/utils.py -> build/bdist.linux-riscv64/wheel/./boto3
2025-04-28 08:30:51,486 root INFO copying build/lib/boto3/compat.py -> build/bdist.linux-riscv64/wheel/./boto3
2025-04-28 08:30:51,488 root INFO creating build/bdist.linux-riscv64/wheel/boto3/examples
2025-04-28 08:30:51,489 root INFO copying build/lib/boto3/examples/cloudfront.rst -> build/bdist.linux-riscv64/wheel/./boto3/examples
2025-04-28 08:30:51,490 root INFO copying build/lib/boto3/examples/s3.rst -> build/bdist.linux-riscv64/wheel/./boto3/examples
2025-04-28 08:30:51,491 root INFO running install_egg_info
2025-04-28 08:30:51,512 root INFO Copying boto3.egg-info to build/bdist.linux-riscv64/wheel/./boto3-1.37.28-py3.12.egg-info
2025-04-28 08:30:51,518 root INFO running install_scripts
2025-04-28 08:30:51,525 root INFO creating build/bdist.linux-riscv64/wheel/boto3-1.37.28.dist-info/WHEEL
2025-04-28 08:30:51,528 wheel INFO creating '/home/buildozer/aports/community/py3-boto3/src/boto3-1.37.28/.dist/.tmp-l6u8tany/boto3-1.37.28-py3-none-any.whl' and adding 'build/bdist.linux-riscv64/wheel' to it
2025-04-28 08:30:51,530 wheel INFO adding 'boto3/__init__.py'
2025-04-28 08:30:51,531 wheel INFO adding 'boto3/compat.py'
2025-04-28 08:30:51,533 wheel INFO adding 'boto3/crt.py'
2025-04-28 08:30:51,534 wheel INFO adding 'boto3/exceptions.py'
2025-04-28 08:30:51,536 wheel INFO adding 'boto3/session.py'
2025-04-28 08:30:51,538 wheel INFO adding 'boto3/utils.py'
2025-04-28 08:30:51,541 wheel INFO adding 'boto3/data/cloudformation/2010-05-15/resources-1.json'
2025-04-28 08:30:51,542 wheel INFO adding 'boto3/data/cloudwatch/2010-08-01/resources-1.json'
2025-04-28 08:30:51,544 wheel INFO adding 'boto3/data/dynamodb/2012-08-10/resources-1.json'
2025-04-28 08:30:51,547 wheel INFO adding 'boto3/data/ec2/2014-10-01/resources-1.json'
2025-04-28 08:30:51,551 wheel INFO adding 'boto3/data/ec2/2015-03-01/resources-1.json'
2025-04-28 08:30:51,554 wheel INFO adding 'boto3/data/ec2/2015-04-15/resources-1.json'
2025-04-28 08:30:51,558 wheel INFO adding 'boto3/data/ec2/2015-10-01/resources-1.json'
2025-04-28 08:30:51,561 wheel INFO adding 'boto3/data/ec2/2016-04-01/resources-1.json'
2025-04-28 08:30:51,565 wheel INFO adding 'boto3/data/ec2/2016-09-15/resources-1.json'
2025-04-28 08:30:51,569 wheel INFO adding 'boto3/data/ec2/2016-11-15/resources-1.json'
2025-04-28 08:30:51,572 wheel INFO adding 'boto3/data/glacier/2012-06-01/resources-1.json'
2025-04-28 08:30:51,575 wheel INFO adding 'boto3/data/iam/2010-05-08/resources-1.json'
2025-04-28 08:30:51,577 wheel INFO adding 'boto3/data/opsworks/2013-02-18/resources-1.json'
2025-04-28 08:30:51,580 wheel INFO adding 'boto3/data/s3/2006-03-01/resources-1.json'
2025-04-28 08:30:51,582 wheel INFO adding 'boto3/data/sns/2010-03-31/resources-1.json'
2025-04-28 08:30:51,584 wheel INFO adding 'boto3/data/sqs/2012-11-05/resources-1.json'
2025-04-28 08:30:51,586 wheel INFO adding 'boto3/docs/__init__.py'
2025-04-28 08:30:51,588 wheel INFO adding 'boto3/docs/action.py'
2025-04-28 08:30:51,589 wheel INFO adding 'boto3/docs/attr.py'
2025-04-28 08:30:51,591 wheel INFO adding 'boto3/docs/base.py'
2025-04-28 08:30:51,592 wheel INFO adding 'boto3/docs/client.py'
2025-04-28 08:30:51,593 wheel INFO adding 'boto3/docs/collection.py'
2025-04-28 08:30:51,595 wheel INFO adding 'boto3/docs/docstring.py'
2025-04-28 08:30:51,596 wheel INFO adding 'boto3/docs/method.py'
2025-04-28 08:30:51,598 wheel INFO adding 'boto3/docs/resource.py'
2025-04-28 08:30:51,600 wheel INFO adding 'boto3/docs/service.py'
2025-04-28 08:30:51,601 wheel INFO adding 'boto3/docs/subresource.py'
2025-04-28 08:30:51,603 wheel INFO adding 'boto3/docs/utils.py'
2025-04-28 08:30:51,605 wheel INFO adding 'boto3/docs/waiter.py'
2025-04-28 08:30:51,606 wheel INFO adding 'boto3/dynamodb/__init__.py'
2025-04-28 08:30:51,608 wheel INFO adding 'boto3/dynamodb/conditions.py'
2025-04-28 08:30:51,610 wheel INFO adding 'boto3/dynamodb/table.py'
2025-04-28 08:30:51,612 wheel INFO adding 'boto3/dynamodb/transform.py'
2025-04-28 08:30:51,613 wheel INFO adding 'boto3/dynamodb/types.py'
2025-04-28 08:30:51,615 wheel INFO adding 'boto3/ec2/__init__.py'
2025-04-28 08:30:51,616 wheel INFO adding 'boto3/ec2/createtags.py'
2025-04-28 08:30:51,618 wheel INFO adding 'boto3/ec2/deletetags.py'
2025-04-28 08:30:51,619 wheel INFO adding 'boto3/examples/cloudfront.rst'
2025-04-28 08:30:51,621 wheel INFO adding 'boto3/examples/s3.rst'
2025-04-28 08:30:51,623 wheel INFO adding 'boto3/resources/__init__.py'
2025-04-28 08:30:51,624 wheel INFO adding 'boto3/resources/action.py'
2025-04-28 08:30:51,626 wheel INFO adding 'boto3/resources/base.py'
2025-04-28 08:30:51,627 wheel INFO adding 'boto3/resources/collection.py'
2025-04-28 08:30:51,629 wheel INFO adding 'boto3/resources/factory.py'
2025-04-28 08:30:51,632 wheel INFO adding 'boto3/resources/model.py'
2025-04-28 08:30:51,634 wheel INFO adding 'boto3/resources/params.py'
2025-04-28 08:30:51,635 wheel INFO adding 'boto3/resources/response.py'
2025-04-28 08:30:51,638 wheel INFO adding 'boto3/s3/__init__.py'
2025-04-28 08:30:51,639 wheel INFO adding 'boto3/s3/constants.py'
2025-04-28 08:30:51,640 wheel INFO adding 'boto3/s3/inject.py'
2025-04-28 08:30:51,642 wheel INFO adding 'boto3/s3/transfer.py'
2025-04-28 08:30:51,645 wheel INFO adding 'boto3-1.37.28.dist-info/licenses/LICENSE'
2025-04-28 08:30:51,646 wheel INFO adding 'boto3-1.37.28.dist-info/licenses/NOTICE'
2025-04-28 08:30:51,647 wheel INFO adding 'boto3-1.37.28.dist-info/METADATA'
2025-04-28 08:30:51,648 wheel INFO adding 'boto3-1.37.28.dist-info/WHEEL'
2025-04-28 08:30:51,649 wheel INFO adding 'boto3-1.37.28.dist-info/top_level.txt'
2025-04-28 08:30:51,651 wheel INFO adding 'boto3-1.37.28.dist-info/RECORD'
2025-04-28 08:30:51,653 root INFO removing build/bdist.linux-riscv64/wheel
2025-04-28 08:30:51,669 gpep517 INFO The backend produced .dist/boto3-1.37.28-py3-none-any.whl
boto3-1.37.28-py3-none-any.whl
>>> py3-boto3: Entering fakeroot...
>>> py3-boto3-pyc*: Running split function pyc...
'usr/lib/python3.12/site-packages/boto3/ec2/__pycache__' -> '/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3-pyc/usr/lib/python3.12/site-packages/boto3/ec2/__pycache__'
'usr/lib/python3.12/site-packages/boto3/__pycache__' -> '/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3-pyc/usr/lib/python3.12/site-packages/boto3/__pycache__'
'usr/lib/python3.12/site-packages/boto3/dynamodb/__pycache__' -> '/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3-pyc/usr/lib/python3.12/site-packages/boto3/dynamodb/__pycache__'
'usr/lib/python3.12/site-packages/boto3/resources/__pycache__' -> '/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3-pyc/usr/lib/python3.12/site-packages/boto3/resources/__pycache__'
'usr/lib/python3.12/site-packages/boto3/s3/__pycache__' -> '/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3-pyc/usr/lib/python3.12/site-packages/boto3/s3/__pycache__'
'usr/lib/python3.12/site-packages/boto3/docs/__pycache__' -> '/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3-pyc/usr/lib/python3.12/site-packages/boto3/docs/__pycache__'
>>> py3-boto3-pyc*: Preparing subpackage py3-boto3-pyc...
>>> py3-boto3-pyc*: Running postcheck for py3-boto3-pyc
>>> py3-boto3*: Running postcheck for py3-boto3
>>> py3-boto3*: Preparing package py3-boto3...
>>> py3-boto3-pyc*: Tracing dependencies...
	py3-botocore
	py3-jmespath
	py3-s3transfer
	python3~3.12
>>> py3-boto3-pyc*: Package size: 308.3 KB
>>> py3-boto3-pyc*: Compressing data...
>>> py3-boto3-pyc*: Create checksum...
>>> py3-boto3-pyc*: Create py3-boto3-pyc-1.37.28-r0.apk
>>> py3-boto3*: Tracing dependencies...
	py3-botocore
	py3-jmespath
	py3-s3transfer
	python3~3.12
>>> py3-boto3*: Package size: 967.9 KB
>>> py3-boto3*: Compressing data...
>>> py3-boto3*: Create checksum...
>>> py3-boto3*: Create py3-boto3-1.37.28-r0.apk
>>> py3-boto3: Build complete at Mon, 28 Apr 2025 08:30:54 +0000 elapsed time 0h 0m 15s
>>> py3-boto3: Cleaning up srcdir
>>> py3-boto3: Cleaning up pkgdir
>>> py3-boto3: Uninstalling dependencies...
(1/38) Purging .makedepends-py3-boto3 (20250428.083045)
(2/38) Purging py3-s3transfer-pyc (0.10.1-r0)
(3/38) Purging py3-s3transfer (0.10.1-r0)
(4/38) Purging py3-botocore-pyc (1.37.28-r0)
(5/38) Purging py3-botocore (1.37.28-r0)
(6/38) Purging py3-certifi-pyc (2024.12.14-r0)
(7/38) Purging py3-certifi (2024.12.14-r0)
(8/38) Purging py3-dateutil-pyc (2.9.0-r1)
(9/38) Purging py3-dateutil (2.9.0-r1)
(10/38) Purging py3-six-pyc (1.17.0-r0)
(11/38) Purging py3-six (1.17.0-r0)
(12/38) Purging py3-jmespath-pyc (1.0.1-r4)
(13/38) Purging py3-jmespath (1.0.1-r4)
(14/38) Purging py3-urllib3-pyc (1.26.20-r0)
(15/38) Purging py3-urllib3 (1.26.20-r0)
(16/38) Purging py3-gpep517-pyc (16-r0)
(17/38) Purging py3-gpep517 (16-r0)
(18/38) Purging py3-installer-pyc (0.7.0-r2)
(19/38) Purging py3-installer (0.7.0-r2)
(20/38) Purging py3-setuptools-pyc (77.0.3-r0)
(21/38) Purging py3-setuptools (77.0.3-r0)
(22/38) Purging py3-wheel-pyc (0.43.0-r0)
(23/38) Purging py3-wheel (0.43.0-r0)
(24/38) Purging py3-packaging-pyc (25.0-r0)
(25/38) Purging py3-packaging (25.0-r0)
(26/38) Purging py3-parsing-pyc (3.2.0-r0)
(27/38) Purging py3-parsing (3.2.0-r0)
(28/38) Purging python3-pyc (3.12.10-r0)
(29/38) Purging python3-pycache-pyc0 (3.12.10-r0)
(30/38) Purging pyc (3.12.10-r0)
(31/38) Purging python3 (3.12.10-r0)
(32/38) Purging gdbm (1.24-r0)
(33/38) Purging libbz2 (1.0.8-r6)
(34/38) Purging libffi (3.4.8-r0)
(35/38) Purging libpanelw (6.5_p20250412-r0)
(36/38) Purging mpdecimal (4.0.0-r0)
(37/38) Purging sqlite-libs (3.49.1-r0)
(38/38) Purging xz-libs (5.8.1-r0)
Executing busybox-1.37.0-r16.trigger
OK: 337 MiB in 99 packages
>>> py3-boto3: Updating the community/riscv64 repository index...
>>> py3-boto3: Signing the index...