>>> py3-boto3: Building community/py3-boto3 1.35.71-r0 (using abuild 3.14.1-r3) started Sun, 01 Dec 2024 19:43:30 +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.6-r0)
(3/38) Installing gdbm (1.24-r0)
(4/38) Installing xz-libs (5.6.3-r0)
(5/38) Installing mpdecimal (4.0.0-r0)
(6/38) Installing libpanelw (6.5_p20241006-r3)
(7/38) Installing sqlite-libs (3.47.1-r0)
(8/38) Installing python3 (3.12.7-r1)
(9/38) Installing python3-pycache-pyc0 (3.12.7-r1)
(10/38) Installing pyc (3.12.7-r1)
(11/38) Installing py3-certifi-pyc (2024.8.30-r0)
(12/38) Installing py3-six (1.16.0-r9)
(13/38) Installing py3-six-pyc (1.16.0-r9)
(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-r3)
(17/38) Installing py3-jmespath-pyc (1.0.1-r3)
(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.35.71-r0)
(21/38) Installing python3-pyc (3.12.7-r1)
(22/38) Installing py3-certifi (2024.8.30-r0)
(23/38) Installing py3-botocore (1.35.71-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.1.4-r0)
(31/38) Installing py3-parsing-pyc (3.1.4-r0)
(32/38) Installing py3-packaging (24.2-r0)
(33/38) Installing py3-packaging-pyc (24.2-r0)
(34/38) Installing py3-setuptools (70.3.0-r0)
(35/38) Installing py3-setuptools-pyc (70.3.0-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 (20241201.194331)
Executing busybox-1.37.0-r8.trigger
OK: 417 MiB in 139 packages
>>> py3-boto3: Cleaning up srcdir
>>> py3-boto3: Cleaning up pkgdir
>>> py3-boto3: Cleaning up tmpdir
>>> py3-boto3: Fetching https://distfiles.alpinelinux.org/distfiles/edge/boto3-1.35.71.tar.gz
>>> py3-boto3: Fetching https://distfiles.alpinelinux.org/distfiles/edge/boto3-1.35.71.tar.gz
>>> py3-boto3: Checking sha512sums...
boto3-1.35.71.tar.gz: OK
>>> py3-boto3: Unpacking /var/cache/distfiles/edge/boto3-1.35.71.tar.gz...
2024-12-01 19:43:32,640 gpep517 INFO Building wheel via backend setuptools.build_meta:__legacy__
2024-12-01 19:43:32,655 root INFO running bdist_wheel
2024-12-01 19:43:32,671 root INFO running build
2024-12-01 19:43:32,671 root INFO running build_py
2024-12-01 19:43:32,674 root INFO creating build
2024-12-01 19:43:32,674 root INFO creating build/lib
2024-12-01 19:43:32,674 root INFO creating build/lib/boto3
2024-12-01 19:43:32,674 root INFO copying boto3/__init__.py -> build/lib/boto3
2024-12-01 19:43:32,674 root INFO copying boto3/exceptions.py -> build/lib/boto3
2024-12-01 19:43:32,675 root INFO copying boto3/session.py -> build/lib/boto3
2024-12-01 19:43:32,675 root INFO copying boto3/utils.py -> build/lib/boto3
2024-12-01 19:43:32,675 root INFO copying boto3/crt.py -> build/lib/boto3
2024-12-01 19:43:32,675 root INFO copying boto3/compat.py -> build/lib/boto3
2024-12-01 19:43:32,676 root INFO creating build/lib/boto3/resources
2024-12-01 19:43:32,676 root INFO copying boto3/resources/__init__.py -> build/lib/boto3/resources
2024-12-01 19:43:32,676 root INFO copying boto3/resources/response.py -> build/lib/boto3/resources
2024-12-01 19:43:32,676 root INFO copying boto3/resources/collection.py -> build/lib/boto3/resources
2024-12-01 19:43:32,676 root INFO copying boto3/resources/action.py -> build/lib/boto3/resources
2024-12-01 19:43:32,676 root INFO copying boto3/resources/params.py -> build/lib/boto3/resources
2024-12-01 19:43:32,677 root INFO copying boto3/resources/model.py -> build/lib/boto3/resources
2024-12-01 19:43:32,677 root INFO copying boto3/resources/factory.py -> build/lib/boto3/resources
2024-12-01 19:43:32,677 root INFO copying boto3/resources/base.py -> build/lib/boto3/resources
2024-12-01 19:43:32,677 root INFO creating build/lib/boto3/ec2
2024-12-01 19:43:32,677 root INFO copying boto3/ec2/__init__.py -> build/lib/boto3/ec2
2024-12-01 19:43:32,678 root INFO copying boto3/ec2/createtags.py -> build/lib/boto3/ec2
2024-12-01 19:43:32,678 root INFO copying boto3/ec2/deletetags.py -> build/lib/boto3/ec2
2024-12-01 19:43:32,678 root INFO creating build/lib/boto3/dynamodb
2024-12-01 19:43:32,678 root INFO copying boto3/dynamodb/__init__.py -> build/lib/boto3/dynamodb
2024-12-01 19:43:32,678 root INFO copying boto3/dynamodb/conditions.py -> build/lib/boto3/dynamodb
2024-12-01 19:43:32,679 root INFO copying boto3/dynamodb/transform.py -> build/lib/boto3/dynamodb
2024-12-01 19:43:32,679 root INFO copying boto3/dynamodb/types.py -> build/lib/boto3/dynamodb
2024-12-01 19:43:32,679 root INFO copying boto3/dynamodb/table.py -> build/lib/boto3/dynamodb
2024-12-01 19:43:32,679 root INFO creating build/lib/boto3/s3
2024-12-01 19:43:32,679 root INFO copying boto3/s3/__init__.py -> build/lib/boto3/s3
2024-12-01 19:43:32,680 root INFO copying boto3/s3/transfer.py -> build/lib/boto3/s3
2024-12-01 19:43:32,680 root INFO copying boto3/s3/inject.py -> build/lib/boto3/s3
2024-12-01 19:43:32,680 root INFO copying boto3/s3/constants.py -> build/lib/boto3/s3
2024-12-01 19:43:32,680 root INFO creating build/lib/boto3/docs
2024-12-01 19:43:32,680 root INFO copying boto3/docs/__init__.py -> build/lib/boto3/docs
2024-12-01 19:43:32,681 root INFO copying boto3/docs/resource.py -> build/lib/boto3/docs
2024-12-01 19:43:32,681 root INFO copying boto3/docs/collection.py -> build/lib/boto3/docs
2024-12-01 19:43:32,681 root INFO copying boto3/docs/action.py -> build/lib/boto3/docs
2024-12-01 19:43:32,681 root INFO copying boto3/docs/attr.py -> build/lib/boto3/docs
2024-12-01 19:43:32,681 root INFO copying boto3/docs/utils.py -> build/lib/boto3/docs
2024-12-01 19:43:32,681 root INFO copying boto3/docs/method.py -> build/lib/boto3/docs
2024-12-01 19:43:32,682 root INFO copying boto3/docs/subresource.py -> build/lib/boto3/docs
2024-12-01 19:43:32,682 root INFO copying boto3/docs/waiter.py -> build/lib/boto3/docs
2024-12-01 19:43:32,682 root INFO copying boto3/docs/service.py -> build/lib/boto3/docs
2024-12-01 19:43:32,682 root INFO copying boto3/docs/base.py -> build/lib/boto3/docs
2024-12-01 19:43:32,682 root INFO copying boto3/docs/docstring.py -> build/lib/boto3/docs
2024-12-01 19:43:32,682 root INFO copying boto3/docs/client.py -> build/lib/boto3/docs
2024-12-01 19:43:32,683 root INFO running egg_info
2024-12-01 19:43:32,684 root INFO writing boto3.egg-info/PKG-INFO
2024-12-01 19:43:32,685 root INFO writing dependency_links to boto3.egg-info/dependency_links.txt
2024-12-01 19:43:32,685 root INFO writing requirements to boto3.egg-info/requires.txt
2024-12-01 19:43:32,686 root INFO writing top-level names to boto3.egg-info/top_level.txt
2024-12-01 19:43:32,689 root INFO reading manifest file 'boto3.egg-info/SOURCES.txt'
2024-12-01 19:43:32,689 root INFO reading manifest template 'MANIFEST.in'
2024-12-01 19:43:32,690 root INFO adding license file 'LICENSE'
2024-12-01 19:43:32,690 root INFO adding license file 'NOTICE'
2024-12-01 19:43:32,692 root INFO writing manifest file 'boto3.egg-info/SOURCES.txt'
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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:215: _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)
2024-12-01 19:43:32,694 root INFO creating build/lib/boto3/data
2024-12-01 19:43:32,694 root INFO creating build/lib/boto3/data/cloudformation
2024-12-01 19:43:32,694 root INFO creating build/lib/boto3/data/cloudformation/2010-05-15
2024-12-01 19:43:32,695 root INFO copying boto3/data/cloudformation/2010-05-15/resources-1.json -> build/lib/boto3/data/cloudformation/2010-05-15
2024-12-01 19:43:32,695 root INFO creating build/lib/boto3/data/cloudwatch
2024-12-01 19:43:32,695 root INFO creating build/lib/boto3/data/cloudwatch/2010-08-01
2024-12-01 19:43:32,695 root INFO copying boto3/data/cloudwatch/2010-08-01/resources-1.json -> build/lib/boto3/data/cloudwatch/2010-08-01
2024-12-01 19:43:32,695 root INFO creating build/lib/boto3/data/dynamodb
2024-12-01 19:43:32,695 root INFO creating build/lib/boto3/data/dynamodb/2012-08-10
2024-12-01 19:43:32,695 root INFO copying boto3/data/dynamodb/2012-08-10/resources-1.json -> build/lib/boto3/data/dynamodb/2012-08-10
2024-12-01 19:43:32,696 root INFO creating build/lib/boto3/data/ec2
2024-12-01 19:43:32,696 root INFO creating build/lib/boto3/data/ec2/2014-10-01
2024-12-01 19:43:32,696 root INFO copying boto3/data/ec2/2014-10-01/resources-1.json -> build/lib/boto3/data/ec2/2014-10-01
2024-12-01 19:43:32,696 root INFO creating build/lib/boto3/data/ec2/2015-03-01
2024-12-01 19:43:32,696 root INFO copying boto3/data/ec2/2015-03-01/resources-1.json -> build/lib/boto3/data/ec2/2015-03-01
2024-12-01 19:43:32,697 root INFO creating build/lib/boto3/data/ec2/2015-04-15
2024-12-01 19:43:32,697 root INFO copying boto3/data/ec2/2015-04-15/resources-1.json -> build/lib/boto3/data/ec2/2015-04-15
2024-12-01 19:43:32,697 root INFO creating build/lib/boto3/data/ec2/2015-10-01
2024-12-01 19:43:32,697 root INFO copying boto3/data/ec2/2015-10-01/resources-1.json -> build/lib/boto3/data/ec2/2015-10-01
2024-12-01 19:43:32,697 root INFO creating build/lib/boto3/data/ec2/2016-04-01
2024-12-01 19:43:32,698 root INFO copying boto3/data/ec2/2016-04-01/resources-1.json -> build/lib/boto3/data/ec2/2016-04-01
2024-12-01 19:43:32,698 root INFO creating build/lib/boto3/data/ec2/2016-09-15
2024-12-01 19:43:32,698 root INFO copying boto3/data/ec2/2016-09-15/resources-1.json -> build/lib/boto3/data/ec2/2016-09-15
2024-12-01 19:43:32,698 root INFO creating build/lib/boto3/data/ec2/2016-11-15
2024-12-01 19:43:32,698 root INFO copying boto3/data/ec2/2016-11-15/resources-1.json -> build/lib/boto3/data/ec2/2016-11-15
2024-12-01 19:43:32,699 root INFO creating build/lib/boto3/data/glacier
2024-12-01 19:43:32,699 root INFO creating build/lib/boto3/data/glacier/2012-06-01
2024-12-01 19:43:32,699 root INFO copying boto3/data/glacier/2012-06-01/resources-1.json -> build/lib/boto3/data/glacier/2012-06-01
2024-12-01 19:43:32,699 root INFO creating build/lib/boto3/data/iam
2024-12-01 19:43:32,699 root INFO creating build/lib/boto3/data/iam/2010-05-08
2024-12-01 19:43:32,699 root INFO copying boto3/data/iam/2010-05-08/resources-1.json -> build/lib/boto3/data/iam/2010-05-08
2024-12-01 19:43:32,699 root INFO creating build/lib/boto3/data/opsworks
2024-12-01 19:43:32,700 root INFO creating build/lib/boto3/data/opsworks/2013-02-18
2024-12-01 19:43:32,700 root INFO copying boto3/data/opsworks/2013-02-18/resources-1.json -> build/lib/boto3/data/opsworks/2013-02-18
2024-12-01 19:43:32,700 root INFO creating build/lib/boto3/data/s3
2024-12-01 19:43:32,700 root INFO creating build/lib/boto3/data/s3/2006-03-01
2024-12-01 19:43:32,700 root INFO copying boto3/data/s3/2006-03-01/resources-1.json -> build/lib/boto3/data/s3/2006-03-01
2024-12-01 19:43:32,700 root INFO creating build/lib/boto3/data/sns
2024-12-01 19:43:32,700 root INFO creating build/lib/boto3/data/sns/2010-03-31
2024-12-01 19:43:32,700 root INFO copying boto3/data/sns/2010-03-31/resources-1.json -> build/lib/boto3/data/sns/2010-03-31
2024-12-01 19:43:32,701 root INFO creating build/lib/boto3/data/sqs
2024-12-01 19:43:32,701 root INFO creating build/lib/boto3/data/sqs/2012-11-05
2024-12-01 19:43:32,701 root INFO copying boto3/data/sqs/2012-11-05/resources-1.json -> build/lib/boto3/data/sqs/2012-11-05
2024-12-01 19:43:32,701 root INFO creating build/lib/boto3/examples
2024-12-01 19:43:32,701 root INFO copying boto3/examples/cloudfront.rst -> build/lib/boto3/examples
2024-12-01 19:43:32,701 root INFO copying boto3/examples/s3.rst -> build/lib/boto3/examples
2024-12-01 19:43:32,706 root INFO installing to build/bdist.linux-armv8l/wheel
2024-12-01 19:43:32,706 root INFO running install
2024-12-01 19:43:32,715 root INFO running install_lib
2024-12-01 19:43:32,717 root INFO creating build/bdist.linux-armv8l
2024-12-01 19:43:32,717 root INFO creating build/bdist.linux-armv8l/wheel
2024-12-01 19:43:32,717 root INFO creating build/bdist.linux-armv8l/wheel/boto3
2024-12-01 19:43:32,717 root INFO copying build/lib/boto3/__init__.py -> build/bdist.linux-armv8l/wheel/boto3
2024-12-01 19:43:32,717 root INFO creating build/bdist.linux-armv8l/wheel/boto3/resources
2024-12-01 19:43:32,717 root INFO copying build/lib/boto3/resources/__init__.py -> build/bdist.linux-armv8l/wheel/boto3/resources
2024-12-01 19:43:32,718 root INFO copying build/lib/boto3/resources/response.py -> build/bdist.linux-armv8l/wheel/boto3/resources
2024-12-01 19:43:32,718 root INFO copying build/lib/boto3/resources/collection.py -> build/bdist.linux-armv8l/wheel/boto3/resources
2024-12-01 19:43:32,718 root INFO copying build/lib/boto3/resources/action.py -> build/bdist.linux-armv8l/wheel/boto3/resources
2024-12-01 19:43:32,718 root INFO copying build/lib/boto3/resources/params.py -> build/bdist.linux-armv8l/wheel/boto3/resources
2024-12-01 19:43:32,718 root INFO copying build/lib/boto3/resources/model.py -> build/bdist.linux-armv8l/wheel/boto3/resources
2024-12-01 19:43:32,718 root INFO copying build/lib/boto3/resources/factory.py -> build/bdist.linux-armv8l/wheel/boto3/resources
2024-12-01 19:43:32,719 root INFO copying build/lib/boto3/resources/base.py -> build/bdist.linux-armv8l/wheel/boto3/resources
2024-12-01 19:43:32,719 root INFO copying build/lib/boto3/exceptions.py -> build/bdist.linux-armv8l/wheel/boto3
2024-12-01 19:43:32,719 root INFO copying build/lib/boto3/session.py -> build/bdist.linux-armv8l/wheel/boto3
2024-12-01 19:43:32,719 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data
2024-12-01 19:43:32,719 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/sqs
2024-12-01 19:43:32,719 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/sqs/2012-11-05
2024-12-01 19:43:32,720 root INFO copying build/lib/boto3/data/sqs/2012-11-05/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/sqs/2012-11-05
2024-12-01 19:43:32,720 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/glacier
2024-12-01 19:43:32,720 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/glacier/2012-06-01
2024-12-01 19:43:32,720 root INFO copying build/lib/boto3/data/glacier/2012-06-01/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/glacier/2012-06-01
2024-12-01 19:43:32,720 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/ec2
2024-12-01 19:43:32,720 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/ec2/2015-04-15
2024-12-01 19:43:32,720 root INFO copying build/lib/boto3/data/ec2/2015-04-15/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/ec2/2015-04-15
2024-12-01 19:43:32,721 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/ec2/2016-11-15
2024-12-01 19:43:32,721 root INFO copying build/lib/boto3/data/ec2/2016-11-15/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/ec2/2016-11-15
2024-12-01 19:43:32,721 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/ec2/2015-10-01
2024-12-01 19:43:32,721 root INFO copying build/lib/boto3/data/ec2/2015-10-01/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/ec2/2015-10-01
2024-12-01 19:43:32,722 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/ec2/2016-04-01
2024-12-01 19:43:32,722 root INFO copying build/lib/boto3/data/ec2/2016-04-01/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/ec2/2016-04-01
2024-12-01 19:43:32,722 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/ec2/2014-10-01
2024-12-01 19:43:32,722 root INFO copying build/lib/boto3/data/ec2/2014-10-01/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/ec2/2014-10-01
2024-12-01 19:43:32,722 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/ec2/2015-03-01
2024-12-01 19:43:32,722 root INFO copying build/lib/boto3/data/ec2/2015-03-01/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/ec2/2015-03-01
2024-12-01 19:43:32,723 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/ec2/2016-09-15
2024-12-01 19:43:32,723 root INFO copying build/lib/boto3/data/ec2/2016-09-15/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/ec2/2016-09-15
2024-12-01 19:43:32,723 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/dynamodb
2024-12-01 19:43:32,723 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/dynamodb/2012-08-10
2024-12-01 19:43:32,723 root INFO copying build/lib/boto3/data/dynamodb/2012-08-10/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/dynamodb/2012-08-10
2024-12-01 19:43:32,724 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/sns
2024-12-01 19:43:32,724 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/sns/2010-03-31
2024-12-01 19:43:32,724 root INFO copying build/lib/boto3/data/sns/2010-03-31/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/sns/2010-03-31
2024-12-01 19:43:32,724 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/cloudwatch
2024-12-01 19:43:32,724 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/cloudwatch/2010-08-01
2024-12-01 19:43:32,724 root INFO copying build/lib/boto3/data/cloudwatch/2010-08-01/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/cloudwatch/2010-08-01
2024-12-01 19:43:32,724 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/iam
2024-12-01 19:43:32,724 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/iam/2010-05-08
2024-12-01 19:43:32,725 root INFO copying build/lib/boto3/data/iam/2010-05-08/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/iam/2010-05-08
2024-12-01 19:43:32,725 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/s3
2024-12-01 19:43:32,725 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/s3/2006-03-01
2024-12-01 19:43:32,725 root INFO copying build/lib/boto3/data/s3/2006-03-01/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/s3/2006-03-01
2024-12-01 19:43:32,725 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/opsworks
2024-12-01 19:43:32,725 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/opsworks/2013-02-18
2024-12-01 19:43:32,725 root INFO copying build/lib/boto3/data/opsworks/2013-02-18/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/opsworks/2013-02-18
2024-12-01 19:43:32,726 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/cloudformation
2024-12-01 19:43:32,726 root INFO creating build/bdist.linux-armv8l/wheel/boto3/data/cloudformation/2010-05-15
2024-12-01 19:43:32,726 root INFO copying build/lib/boto3/data/cloudformation/2010-05-15/resources-1.json -> build/bdist.linux-armv8l/wheel/boto3/data/cloudformation/2010-05-15
2024-12-01 19:43:32,726 root INFO copying build/lib/boto3/utils.py -> build/bdist.linux-armv8l/wheel/boto3
2024-12-01 19:43:32,726 root INFO creating build/bdist.linux-armv8l/wheel/boto3/ec2
2024-12-01 19:43:32,726 root INFO copying build/lib/boto3/ec2/__init__.py -> build/bdist.linux-armv8l/wheel/boto3/ec2
2024-12-01 19:43:32,727 root INFO copying build/lib/boto3/ec2/createtags.py -> build/bdist.linux-armv8l/wheel/boto3/ec2
2024-12-01 19:43:32,727 root INFO copying build/lib/boto3/ec2/deletetags.py -> build/bdist.linux-armv8l/wheel/boto3/ec2
2024-12-01 19:43:32,727 root INFO creating build/bdist.linux-armv8l/wheel/boto3/examples
2024-12-01 19:43:32,727 root INFO copying build/lib/boto3/examples/cloudfront.rst -> build/bdist.linux-armv8l/wheel/boto3/examples
2024-12-01 19:43:32,727 root INFO copying build/lib/boto3/examples/s3.rst -> build/bdist.linux-armv8l/wheel/boto3/examples
2024-12-01 19:43:32,727 root INFO creating build/bdist.linux-armv8l/wheel/boto3/dynamodb
2024-12-01 19:43:32,727 root INFO copying build/lib/boto3/dynamodb/__init__.py -> build/bdist.linux-armv8l/wheel/boto3/dynamodb
2024-12-01 19:43:32,727 root INFO copying build/lib/boto3/dynamodb/conditions.py -> build/bdist.linux-armv8l/wheel/boto3/dynamodb
2024-12-01 19:43:32,728 root INFO copying build/lib/boto3/dynamodb/transform.py -> build/bdist.linux-armv8l/wheel/boto3/dynamodb
2024-12-01 19:43:32,728 root INFO copying build/lib/boto3/dynamodb/types.py -> build/bdist.linux-armv8l/wheel/boto3/dynamodb
2024-12-01 19:43:32,728 root INFO copying build/lib/boto3/dynamodb/table.py -> build/bdist.linux-armv8l/wheel/boto3/dynamodb
2024-12-01 19:43:32,728 root INFO copying build/lib/boto3/crt.py -> build/bdist.linux-armv8l/wheel/boto3
2024-12-01 19:43:32,728 root INFO copying build/lib/boto3/compat.py -> build/bdist.linux-armv8l/wheel/boto3
2024-12-01 19:43:32,728 root INFO creating build/bdist.linux-armv8l/wheel/boto3/s3
2024-12-01 19:43:32,729 root INFO copying build/lib/boto3/s3/__init__.py -> build/bdist.linux-armv8l/wheel/boto3/s3
2024-12-01 19:43:32,729 root INFO copying build/lib/boto3/s3/transfer.py -> build/bdist.linux-armv8l/wheel/boto3/s3
2024-12-01 19:43:32,729 root INFO copying build/lib/boto3/s3/inject.py -> build/bdist.linux-armv8l/wheel/boto3/s3
2024-12-01 19:43:32,729 root INFO copying build/lib/boto3/s3/constants.py -> build/bdist.linux-armv8l/wheel/boto3/s3
2024-12-01 19:43:32,729 root INFO creating build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,729 root INFO copying build/lib/boto3/docs/__init__.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,730 root INFO copying build/lib/boto3/docs/resource.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,730 root INFO copying build/lib/boto3/docs/collection.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,730 root INFO copying build/lib/boto3/docs/action.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,730 root INFO copying build/lib/boto3/docs/attr.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,730 root INFO copying build/lib/boto3/docs/utils.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,730 root INFO copying build/lib/boto3/docs/method.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,730 root INFO copying build/lib/boto3/docs/subresource.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,731 root INFO copying build/lib/boto3/docs/waiter.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,731 root INFO copying build/lib/boto3/docs/service.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,731 root INFO copying build/lib/boto3/docs/base.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,731 root INFO copying build/lib/boto3/docs/docstring.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,731 root INFO copying build/lib/boto3/docs/client.py -> build/bdist.linux-armv8l/wheel/boto3/docs
2024-12-01 19:43:32,731 root INFO running install_egg_info
2024-12-01 19:43:32,733 root INFO Copying boto3.egg-info to build/bdist.linux-armv8l/wheel/boto3-1.35.71-py3.12.egg-info
2024-12-01 19:43:32,734 root INFO running install_scripts
2024-12-01 19:43:32,737 root INFO creating build/bdist.linux-armv8l/wheel/boto3-1.35.71.dist-info/WHEEL
2024-12-01 19:43:32,737 wheel INFO creating '/home/buildozer/aports/community/py3-boto3/src/boto3-1.35.71/.dist/.tmp-ftp6rs9u/boto3-1.35.71-py3-none-any.whl' and adding 'build/bdist.linux-armv8l/wheel' to it
2024-12-01 19:43:32,738 wheel INFO adding 'boto3/__init__.py'
2024-12-01 19:43:32,738 wheel INFO adding 'boto3/compat.py'
2024-12-01 19:43:32,738 wheel INFO adding 'boto3/crt.py'
2024-12-01 19:43:32,738 wheel INFO adding 'boto3/exceptions.py'
2024-12-01 19:43:32,739 wheel INFO adding 'boto3/session.py'
2024-12-01 19:43:32,739 wheel INFO adding 'boto3/utils.py'
2024-12-01 19:43:32,739 wheel INFO adding 'boto3/data/cloudformation/2010-05-15/resources-1.json'
2024-12-01 19:43:32,739 wheel INFO adding 'boto3/data/cloudwatch/2010-08-01/resources-1.json'
2024-12-01 19:43:32,740 wheel INFO adding 'boto3/data/dynamodb/2012-08-10/resources-1.json'
2024-12-01 19:43:32,740 wheel INFO adding 'boto3/data/ec2/2014-10-01/resources-1.json'
2024-12-01 19:43:32,740 wheel INFO adding 'boto3/data/ec2/2015-03-01/resources-1.json'
2024-12-01 19:43:32,741 wheel INFO adding 'boto3/data/ec2/2015-04-15/resources-1.json'
2024-12-01 19:43:32,741 wheel INFO adding 'boto3/data/ec2/2015-10-01/resources-1.json'
2024-12-01 19:43:32,742 wheel INFO adding 'boto3/data/ec2/2016-04-01/resources-1.json'
2024-12-01 19:43:32,742 wheel INFO adding 'boto3/data/ec2/2016-09-15/resources-1.json'
2024-12-01 19:43:32,743 wheel INFO adding 'boto3/data/ec2/2016-11-15/resources-1.json'
2024-12-01 19:43:32,743 wheel INFO adding 'boto3/data/glacier/2012-06-01/resources-1.json'
2024-12-01 19:43:32,743 wheel INFO adding 'boto3/data/iam/2010-05-08/resources-1.json'
2024-12-01 19:43:32,744 wheel INFO adding 'boto3/data/opsworks/2013-02-18/resources-1.json'
2024-12-01 19:43:32,744 wheel INFO adding 'boto3/data/s3/2006-03-01/resources-1.json'
2024-12-01 19:43:32,744 wheel INFO adding 'boto3/data/sns/2010-03-31/resources-1.json'
2024-12-01 19:43:32,744 wheel INFO adding 'boto3/data/sqs/2012-11-05/resources-1.json'
2024-12-01 19:43:32,745 wheel INFO adding 'boto3/docs/__init__.py'
2024-12-01 19:43:32,745 wheel INFO adding 'boto3/docs/action.py'
2024-12-01 19:43:32,745 wheel INFO adding 'boto3/docs/attr.py'
2024-12-01 19:43:32,745 wheel INFO adding 'boto3/docs/base.py'
2024-12-01 19:43:32,745 wheel INFO adding 'boto3/docs/client.py'
2024-12-01 19:43:32,746 wheel INFO adding 'boto3/docs/collection.py'
2024-12-01 19:43:32,746 wheel INFO adding 'boto3/docs/docstring.py'
2024-12-01 19:43:32,746 wheel INFO adding 'boto3/docs/method.py'
2024-12-01 19:43:32,746 wheel INFO adding 'boto3/docs/resource.py'
2024-12-01 19:43:32,746 wheel INFO adding 'boto3/docs/service.py'
2024-12-01 19:43:32,747 wheel INFO adding 'boto3/docs/subresource.py'
2024-12-01 19:43:32,747 wheel INFO adding 'boto3/docs/utils.py'
2024-12-01 19:43:32,747 wheel INFO adding 'boto3/docs/waiter.py'
2024-12-01 19:43:32,747 wheel INFO adding 'boto3/dynamodb/__init__.py'
2024-12-01 19:43:32,747 wheel INFO adding 'boto3/dynamodb/conditions.py'
2024-12-01 19:43:32,748 wheel INFO adding 'boto3/dynamodb/table.py'
2024-12-01 19:43:32,748 wheel INFO adding 'boto3/dynamodb/transform.py'
2024-12-01 19:43:32,748 wheel INFO adding 'boto3/dynamodb/types.py'
2024-12-01 19:43:32,748 wheel INFO adding 'boto3/ec2/__init__.py'
2024-12-01 19:43:32,748 wheel INFO adding 'boto3/ec2/createtags.py'
2024-12-01 19:43:32,749 wheel INFO adding 'boto3/ec2/deletetags.py'
2024-12-01 19:43:32,749 wheel INFO adding 'boto3/examples/cloudfront.rst'
2024-12-01 19:43:32,749 wheel INFO adding 'boto3/examples/s3.rst'
2024-12-01 19:43:32,749 wheel INFO adding 'boto3/resources/__init__.py'
2024-12-01 19:43:32,749 wheel INFO adding 'boto3/resources/action.py'
2024-12-01 19:43:32,750 wheel INFO adding 'boto3/resources/base.py'
2024-12-01 19:43:32,750 wheel INFO adding 'boto3/resources/collection.py'
2024-12-01 19:43:32,750 wheel INFO adding 'boto3/resources/factory.py'
2024-12-01 19:43:32,750 wheel INFO adding 'boto3/resources/model.py'
2024-12-01 19:43:32,750 wheel INFO adding 'boto3/resources/params.py'
2024-12-01 19:43:32,751 wheel INFO adding 'boto3/resources/response.py'
2024-12-01 19:43:32,751 wheel INFO adding 'boto3/s3/__init__.py'
2024-12-01 19:43:32,751 wheel INFO adding 'boto3/s3/constants.py'
2024-12-01 19:43:32,751 wheel INFO adding 'boto3/s3/inject.py'
2024-12-01 19:43:32,751 wheel INFO adding 'boto3/s3/transfer.py'
2024-12-01 19:43:32,752 wheel INFO adding 'boto3-1.35.71.dist-info/LICENSE'
2024-12-01 19:43:32,752 wheel INFO adding 'boto3-1.35.71.dist-info/METADATA'
2024-12-01 19:43:32,752 wheel INFO adding 'boto3-1.35.71.dist-info/NOTICE'
2024-12-01 19:43:32,752 wheel INFO adding 'boto3-1.35.71.dist-info/WHEEL'
2024-12-01 19:43:32,752 wheel INFO adding 'boto3-1.35.71.dist-info/top_level.txt'
2024-12-01 19:43:32,752 wheel INFO adding 'boto3-1.35.71.dist-info/RECORD'
2024-12-01 19:43:32,753 root INFO removing build/bdist.linux-armv8l/wheel
2024-12-01 19:43:32,755 gpep517 INFO The backend produced .dist/boto3-1.35.71-py3-none-any.whl
boto3-1.35.71-py3-none-any.whl
>>> py3-boto3: Entering fakeroot...
>>> py3-boto3-pyc*: Running split function pyc...
'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/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/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/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/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: 306.3 KB
>>> py3-boto3-pyc*: Compressing data...
>>> py3-boto3-pyc*: Create checksum...
>>> py3-boto3-pyc*: Create py3-boto3-pyc-1.35.71-r0.apk
>>> py3-boto3*: Tracing dependencies...
	py3-botocore
	py3-jmespath
	py3-s3transfer
	python3~3.12
>>> py3-boto3*: Package size: 965.9 KB
>>> py3-boto3*: Compressing data...
>>> py3-boto3*: Create checksum...
>>> py3-boto3*: Create py3-boto3-1.35.71-r0.apk
>>> py3-boto3: Build complete at Sun, 01 Dec 2024 19:43:33 +0000 elapsed time 0h 0m 3s
>>> py3-boto3: Cleaning up srcdir
>>> py3-boto3: Cleaning up pkgdir
>>> py3-boto3: Uninstalling dependencies...
(1/38) Purging .makedepends-py3-boto3 (20241201.194331)
(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.35.71-r0)
(5/38) Purging py3-botocore (1.35.71-r0)
(6/38) Purging py3-certifi-pyc (2024.8.30-r0)
(7/38) Purging py3-certifi (2024.8.30-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.16.0-r9)
(11/38) Purging py3-six (1.16.0-r9)
(12/38) Purging py3-jmespath-pyc (1.0.1-r3)
(13/38) Purging py3-jmespath (1.0.1-r3)
(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 (70.3.0-r0)
(21/38) Purging py3-setuptools (70.3.0-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 (24.2-r0)
(25/38) Purging py3-packaging (24.2-r0)
(26/38) Purging py3-parsing-pyc (3.1.4-r0)
(27/38) Purging py3-parsing (3.1.4-r0)
(28/38) Purging python3-pyc (3.12.7-r1)
(29/38) Purging python3-pycache-pyc0 (3.12.7-r1)
(30/38) Purging pyc (3.12.7-r1)
(31/38) Purging python3 (3.12.7-r1)
(32/38) Purging gdbm (1.24-r0)
(33/38) Purging libbz2 (1.0.8-r6)
(34/38) Purging libffi (3.4.6-r0)
(35/38) Purging libpanelw (6.5_p20241006-r3)
(36/38) Purging mpdecimal (4.0.0-r0)
(37/38) Purging sqlite-libs (3.47.1-r0)
(38/38) Purging xz-libs (5.6.3-r0)
Executing busybox-1.37.0-r8.trigger
OK: 274 MiB in 101 packages
>>> py3-boto3: Updating the community/armv7 repository index...
>>> py3-boto3: Signing the index...