>>> py3-boto3: Building community/py3-boto3 1.34.95-r0 (using abuild 3.13.0-r3) started Wed, 01 May 2024 16:23:37 +0000
>>> py3-boto3: Checking sanity of /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/37) Installing libffi (3.4.6-r0)
(2/37) Installing gdbm (1.23-r1)
(3/37) Installing mpdecimal (4.0.0-r0)
(4/37) Installing libpanelw (6.4_p20240330-r0)
(5/37) Installing readline (8.2.10-r0)
(6/37) Installing sqlite-libs (3.45.3-r0)
(7/37) Installing python3 (3.12.3-r1)
(8/37) Installing python3-pycache-pyc0 (3.12.3-r1)
(9/37) Installing pyc (3.12.3-r1)
(10/37) Installing py3-certifi-pyc (2024.2.2-r1)
(11/37) Installing py3-six (1.16.0-r9)
(12/37) Installing py3-six-pyc (1.16.0-r9)
(13/37) Installing py3-dateutil (2.9.0-r1)
(14/37) Installing py3-dateutil-pyc (2.9.0-r1)
(15/37) Installing py3-jmespath (1.0.1-r2)
(16/37) Installing py3-jmespath-pyc (1.0.1-r2)
(17/37) Installing py3-urllib3 (1.26.18-r1)
(18/37) Installing py3-urllib3-pyc (1.26.18-r1)
(19/37) Installing py3-botocore-pyc (1.34.39-r0)
(20/37) Installing python3-pyc (3.12.3-r1)
(21/37) Installing py3-certifi (2024.2.2-r1)
(22/37) Installing py3-botocore (1.34.39-r0)
(23/37) Installing py3-s3transfer (0.10.1-r0)
(24/37) Installing py3-s3transfer-pyc (0.10.1-r0)
(25/37) Installing py3-installer (0.7.0-r2)
(26/37) Installing py3-installer-pyc (0.7.0-r2)
(27/37) Installing py3-gpep517 (15-r2)
(28/37) Installing py3-gpep517-pyc (15-r2)
(29/37) Installing py3-parsing (3.1.2-r1)
(30/37) Installing py3-parsing-pyc (3.1.2-r1)
(31/37) Installing py3-packaging (24.0-r1)
(32/37) Installing py3-packaging-pyc (24.0-r1)
(33/37) Installing py3-setuptools (69.5.1-r0)
(34/37) Installing py3-setuptools-pyc (69.5.1-r0)
(35/37) Installing py3-wheel (0.42.0-r1)
(36/37) Installing py3-wheel-pyc (0.42.0-r1)
(37/37) Installing .makedepends-py3-boto3 (20240501.162339)
Executing busybox-1.36.1-r26.trigger
OK: 529 MiB in 150 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.34.95.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0   146    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (56) The requested URL returned error: 404
>>> py3-boto3: Fetching https://files.pythonhosted.org/packages/source/b/boto3/boto3-1.34.95.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0

100  105k  100  105k    0     0   710k      0 --:--:-- --:--:-- --:--:--  710k
>>> py3-boto3: Fetching https://distfiles.alpinelinux.org/distfiles/edge/boto3-1.34.95.tar.gz
>>> py3-boto3: Checking sha512sums...
boto3-1.34.95.tar.gz: OK
>>> py3-boto3: Unpacking /var/cache/distfiles/edge/boto3-1.34.95.tar.gz...
2024-05-01 16:23:42,670 gpep517 INFO Building wheel via backend setuptools.build_meta:__legacy__
2024-05-01 16:23:42,752 root INFO running bdist_wheel
2024-05-01 16:23:42,799 root INFO running build
2024-05-01 16:23:42,799 root INFO running build_py
2024-05-01 16:23:42,807 root INFO creating build
2024-05-01 16:23:42,808 root INFO creating build/lib
2024-05-01 16:23:42,808 root INFO creating build/lib/boto3
2024-05-01 16:23:42,808 root INFO copying boto3/utils.py -> build/lib/boto3
2024-05-01 16:23:42,809 root INFO copying boto3/session.py -> build/lib/boto3
2024-05-01 16:23:42,809 root INFO copying boto3/__init__.py -> build/lib/boto3
2024-05-01 16:23:42,810 root INFO copying boto3/compat.py -> build/lib/boto3
2024-05-01 16:23:42,810 root INFO copying boto3/crt.py -> build/lib/boto3
2024-05-01 16:23:42,811 root INFO copying boto3/exceptions.py -> build/lib/boto3
2024-05-01 16:23:42,812 root INFO creating build/lib/boto3/docs
2024-05-01 16:23:42,812 root INFO copying boto3/docs/utils.py -> build/lib/boto3/docs
2024-05-01 16:23:42,813 root INFO copying boto3/docs/action.py -> build/lib/boto3/docs
2024-05-01 16:23:42,813 root INFO copying boto3/docs/method.py -> build/lib/boto3/docs
2024-05-01 16:23:42,814 root INFO copying boto3/docs/__init__.py -> build/lib/boto3/docs
2024-05-01 16:23:42,814 root INFO copying boto3/docs/collection.py -> build/lib/boto3/docs
2024-05-01 16:23:42,815 root INFO copying boto3/docs/waiter.py -> build/lib/boto3/docs
2024-05-01 16:23:42,815 root INFO copying boto3/docs/docstring.py -> build/lib/boto3/docs
2024-05-01 16:23:42,816 root INFO copying boto3/docs/attr.py -> build/lib/boto3/docs
2024-05-01 16:23:42,816 root INFO copying boto3/docs/client.py -> build/lib/boto3/docs
2024-05-01 16:23:42,817 root INFO copying boto3/docs/resource.py -> build/lib/boto3/docs
2024-05-01 16:23:42,818 root INFO copying boto3/docs/base.py -> build/lib/boto3/docs
2024-05-01 16:23:42,818 root INFO copying boto3/docs/service.py -> build/lib/boto3/docs
2024-05-01 16:23:42,819 root INFO copying boto3/docs/subresource.py -> build/lib/boto3/docs
2024-05-01 16:23:42,819 root INFO creating build/lib/boto3/ec2
2024-05-01 16:23:42,820 root INFO copying boto3/ec2/createtags.py -> build/lib/boto3/ec2
2024-05-01 16:23:42,820 root INFO copying boto3/ec2/__init__.py -> build/lib/boto3/ec2
2024-05-01 16:23:42,821 root INFO copying boto3/ec2/deletetags.py -> build/lib/boto3/ec2
2024-05-01 16:23:42,822 root INFO creating build/lib/boto3/dynamodb
2024-05-01 16:23:42,822 root INFO copying boto3/dynamodb/__init__.py -> build/lib/boto3/dynamodb
2024-05-01 16:23:42,822 root INFO copying boto3/dynamodb/table.py -> build/lib/boto3/dynamodb
2024-05-01 16:23:42,823 root INFO copying boto3/dynamodb/transform.py -> build/lib/boto3/dynamodb
2024-05-01 16:23:42,823 root INFO copying boto3/dynamodb/conditions.py -> build/lib/boto3/dynamodb
2024-05-01 16:23:42,824 root INFO copying boto3/dynamodb/types.py -> build/lib/boto3/dynamodb
2024-05-01 16:23:42,825 root INFO creating build/lib/boto3/resources
2024-05-01 16:23:42,825 root INFO copying boto3/resources/action.py -> build/lib/boto3/resources
2024-05-01 16:23:42,826 root INFO copying boto3/resources/__init__.py -> build/lib/boto3/resources
2024-05-01 16:23:42,826 root INFO copying boto3/resources/collection.py -> build/lib/boto3/resources
2024-05-01 16:23:42,827 root INFO copying boto3/resources/response.py -> build/lib/boto3/resources
2024-05-01 16:23:42,827 root INFO copying boto3/resources/model.py -> build/lib/boto3/resources
2024-05-01 16:23:42,828 root INFO copying boto3/resources/params.py -> build/lib/boto3/resources
2024-05-01 16:23:42,828 root INFO copying boto3/resources/base.py -> build/lib/boto3/resources
2024-05-01 16:23:42,829 root INFO copying boto3/resources/factory.py -> build/lib/boto3/resources
2024-05-01 16:23:42,830 root INFO creating build/lib/boto3/s3
2024-05-01 16:23:42,830 root INFO copying boto3/s3/transfer.py -> build/lib/boto3/s3
2024-05-01 16:23:42,831 root INFO copying boto3/s3/__init__.py -> build/lib/boto3/s3
2024-05-01 16:23:42,831 root INFO copying boto3/s3/inject.py -> build/lib/boto3/s3
2024-05-01 16:23:42,832 root INFO copying boto3/s3/constants.py -> build/lib/boto3/s3
2024-05-01 16:23:42,832 root INFO running egg_info
2024-05-01 16:23:42,838 root INFO writing boto3.egg-info/PKG-INFO
2024-05-01 16:23:42,840 root INFO writing dependency_links to boto3.egg-info/dependency_links.txt
2024-05-01 16:23:42,841 root INFO writing requirements to boto3.egg-info/requires.txt
2024-05-01 16:23:42,842 root INFO writing top-level names to boto3.egg-info/top_level.txt
2024-05-01 16:23:42,852 root INFO reading manifest file 'boto3.egg-info/SOURCES.txt'
2024-05-01 16:23:42,854 root INFO reading manifest template 'MANIFEST.in'
2024-05-01 16:23:42,858 root INFO adding license file 'LICENSE'
2024-05-01 16:23:42,859 root INFO adding license file 'NOTICE'
2024-05-01 16:23:42,862 root INFO writing manifest file 'boto3.egg-info/SOURCES.txt'
/usr/lib/python3.12/site-packages/setuptools/command/build_py.py:207: _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:207: _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:207: _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:207: _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:207: _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:207: _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:207: _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:207: _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:207: _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:207: _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)
2024-05-01 16:23:42,871 root INFO creating build/lib/boto3/data
2024-05-01 16:23:42,871 root INFO creating build/lib/boto3/data/cloudformation
2024-05-01 16:23:42,871 root INFO creating build/lib/boto3/data/cloudformation/2010-05-15
2024-05-01 16:23:42,872 root INFO copying boto3/data/cloudformation/2010-05-15/resources-1.json -> build/lib/boto3/data/cloudformation/2010-05-15
2024-05-01 16:23:42,872 root INFO creating build/lib/boto3/data/cloudwatch
2024-05-01 16:23:42,873 root INFO creating build/lib/boto3/data/cloudwatch/2010-08-01
2024-05-01 16:23:42,873 root INFO copying boto3/data/cloudwatch/2010-08-01/resources-1.json -> build/lib/boto3/data/cloudwatch/2010-08-01
2024-05-01 16:23:42,873 root INFO creating build/lib/boto3/data/dynamodb
2024-05-01 16:23:42,874 root INFO creating build/lib/boto3/data/dynamodb/2012-08-10
2024-05-01 16:23:42,874 root INFO copying boto3/data/dynamodb/2012-08-10/resources-1.json -> build/lib/boto3/data/dynamodb/2012-08-10
2024-05-01 16:23:42,875 root INFO creating build/lib/boto3/data/ec2
2024-05-01 16:23:42,875 root INFO creating build/lib/boto3/data/ec2/2014-10-01
2024-05-01 16:23:42,875 root INFO copying boto3/data/ec2/2014-10-01/resources-1.json -> build/lib/boto3/data/ec2/2014-10-01
2024-05-01 16:23:42,876 root INFO creating build/lib/boto3/data/ec2/2015-03-01
2024-05-01 16:23:42,876 root INFO copying boto3/data/ec2/2015-03-01/resources-1.json -> build/lib/boto3/data/ec2/2015-03-01
2024-05-01 16:23:42,877 root INFO creating build/lib/boto3/data/ec2/2015-04-15
2024-05-01 16:23:42,877 root INFO copying boto3/data/ec2/2015-04-15/resources-1.json -> build/lib/boto3/data/ec2/2015-04-15
2024-05-01 16:23:42,878 root INFO creating build/lib/boto3/data/ec2/2015-10-01
2024-05-01 16:23:42,878 root INFO copying boto3/data/ec2/2015-10-01/resources-1.json -> build/lib/boto3/data/ec2/2015-10-01
2024-05-01 16:23:42,879 root INFO creating build/lib/boto3/data/ec2/2016-04-01
2024-05-01 16:23:42,879 root INFO copying boto3/data/ec2/2016-04-01/resources-1.json -> build/lib/boto3/data/ec2/2016-04-01
2024-05-01 16:23:42,880 root INFO creating build/lib/boto3/data/ec2/2016-09-15
2024-05-01 16:23:42,880 root INFO copying boto3/data/ec2/2016-09-15/resources-1.json -> build/lib/boto3/data/ec2/2016-09-15
2024-05-01 16:23:42,881 root INFO creating build/lib/boto3/data/ec2/2016-11-15
2024-05-01 16:23:42,881 root INFO copying boto3/data/ec2/2016-11-15/resources-1.json -> build/lib/boto3/data/ec2/2016-11-15
2024-05-01 16:23:42,882 root INFO creating build/lib/boto3/data/glacier
2024-05-01 16:23:42,882 root INFO creating build/lib/boto3/data/glacier/2012-06-01
2024-05-01 16:23:42,883 root INFO copying boto3/data/glacier/2012-06-01/resources-1.json -> build/lib/boto3/data/glacier/2012-06-01
2024-05-01 16:23:42,883 root INFO creating build/lib/boto3/data/iam
2024-05-01 16:23:42,883 root INFO creating build/lib/boto3/data/iam/2010-05-08
2024-05-01 16:23:42,884 root INFO copying boto3/data/iam/2010-05-08/resources-1.json -> build/lib/boto3/data/iam/2010-05-08
2024-05-01 16:23:42,884 root INFO creating build/lib/boto3/data/opsworks
2024-05-01 16:23:42,885 root INFO creating build/lib/boto3/data/opsworks/2013-02-18
2024-05-01 16:23:42,885 root INFO copying boto3/data/opsworks/2013-02-18/resources-1.json -> build/lib/boto3/data/opsworks/2013-02-18
2024-05-01 16:23:42,885 root INFO creating build/lib/boto3/data/s3
2024-05-01 16:23:42,886 root INFO creating build/lib/boto3/data/s3/2006-03-01
2024-05-01 16:23:42,886 root INFO copying boto3/data/s3/2006-03-01/resources-1.json -> build/lib/boto3/data/s3/2006-03-01
2024-05-01 16:23:42,887 root INFO creating build/lib/boto3/data/sns
2024-05-01 16:23:42,887 root INFO creating build/lib/boto3/data/sns/2010-03-31
2024-05-01 16:23:42,887 root INFO copying boto3/data/sns/2010-03-31/resources-1.json -> build/lib/boto3/data/sns/2010-03-31
2024-05-01 16:23:42,888 root INFO creating build/lib/boto3/data/sqs
2024-05-01 16:23:42,888 root INFO creating build/lib/boto3/data/sqs/2012-11-05
2024-05-01 16:23:42,888 root INFO copying boto3/data/sqs/2012-11-05/resources-1.json -> build/lib/boto3/data/sqs/2012-11-05
2024-05-01 16:23:42,905 wheel INFO installing to build/bdist.linux-i686/wheel
2024-05-01 16:23:42,906 root INFO running install
2024-05-01 16:23:42,935 root INFO running install_lib
2024-05-01 16:23:42,942 root INFO creating build/bdist.linux-i686
2024-05-01 16:23:42,942 root INFO creating build/bdist.linux-i686/wheel
2024-05-01 16:23:42,942 root INFO creating build/bdist.linux-i686/wheel/boto3
2024-05-01 16:23:42,943 root INFO creating build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,943 root INFO copying build/lib/boto3/docs/utils.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,944 root INFO copying build/lib/boto3/docs/action.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,944 root INFO copying build/lib/boto3/docs/method.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,945 root INFO copying build/lib/boto3/docs/__init__.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,945 root INFO copying build/lib/boto3/docs/collection.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,945 root INFO copying build/lib/boto3/docs/waiter.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,946 root INFO copying build/lib/boto3/docs/docstring.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,946 root INFO copying build/lib/boto3/docs/attr.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,947 root INFO copying build/lib/boto3/docs/client.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,947 root INFO copying build/lib/boto3/docs/resource.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,948 root INFO copying build/lib/boto3/docs/base.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,948 root INFO copying build/lib/boto3/docs/service.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,949 root INFO copying build/lib/boto3/docs/subresource.py -> build/bdist.linux-i686/wheel/boto3/docs
2024-05-01 16:23:42,949 root INFO copying build/lib/boto3/utils.py -> build/bdist.linux-i686/wheel/boto3
2024-05-01 16:23:42,950 root INFO creating build/bdist.linux-i686/wheel/boto3/ec2
2024-05-01 16:23:42,950 root INFO copying build/lib/boto3/ec2/createtags.py -> build/bdist.linux-i686/wheel/boto3/ec2
2024-05-01 16:23:42,950 root INFO copying build/lib/boto3/ec2/__init__.py -> build/bdist.linux-i686/wheel/boto3/ec2
2024-05-01 16:23:42,951 root INFO copying build/lib/boto3/ec2/deletetags.py -> build/bdist.linux-i686/wheel/boto3/ec2
2024-05-01 16:23:42,951 root INFO copying build/lib/boto3/session.py -> build/bdist.linux-i686/wheel/boto3
2024-05-01 16:23:42,952 root INFO copying build/lib/boto3/__init__.py -> build/bdist.linux-i686/wheel/boto3
2024-05-01 16:23:42,952 root INFO creating build/bdist.linux-i686/wheel/boto3/dynamodb
2024-05-01 16:23:42,953 root INFO copying build/lib/boto3/dynamodb/__init__.py -> build/bdist.linux-i686/wheel/boto3/dynamodb
2024-05-01 16:23:42,953 root INFO copying build/lib/boto3/dynamodb/table.py -> build/bdist.linux-i686/wheel/boto3/dynamodb
2024-05-01 16:23:42,953 root INFO copying build/lib/boto3/dynamodb/transform.py -> build/bdist.linux-i686/wheel/boto3/dynamodb
2024-05-01 16:23:42,954 root INFO copying build/lib/boto3/dynamodb/conditions.py -> build/bdist.linux-i686/wheel/boto3/dynamodb
2024-05-01 16:23:42,954 root INFO copying build/lib/boto3/dynamodb/types.py -> build/bdist.linux-i686/wheel/boto3/dynamodb
2024-05-01 16:23:42,955 root INFO creating build/bdist.linux-i686/wheel/boto3/resources
2024-05-01 16:23:42,955 root INFO copying build/lib/boto3/resources/action.py -> build/bdist.linux-i686/wheel/boto3/resources
2024-05-01 16:23:42,956 root INFO copying build/lib/boto3/resources/__init__.py -> build/bdist.linux-i686/wheel/boto3/resources
2024-05-01 16:23:42,956 root INFO copying build/lib/boto3/resources/collection.py -> build/bdist.linux-i686/wheel/boto3/resources
2024-05-01 16:23:42,957 root INFO copying build/lib/boto3/resources/response.py -> build/bdist.linux-i686/wheel/boto3/resources
2024-05-01 16:23:42,957 root INFO copying build/lib/boto3/resources/model.py -> build/bdist.linux-i686/wheel/boto3/resources
2024-05-01 16:23:42,958 root INFO copying build/lib/boto3/resources/params.py -> build/bdist.linux-i686/wheel/boto3/resources
2024-05-01 16:23:42,958 root INFO copying build/lib/boto3/resources/base.py -> build/bdist.linux-i686/wheel/boto3/resources
2024-05-01 16:23:42,959 root INFO copying build/lib/boto3/resources/factory.py -> build/bdist.linux-i686/wheel/boto3/resources
2024-05-01 16:23:42,959 root INFO creating build/bdist.linux-i686/wheel/boto3/data
2024-05-01 16:23:42,960 root INFO creating build/bdist.linux-i686/wheel/boto3/data/ec2
2024-05-01 16:23:42,960 root INFO creating build/bdist.linux-i686/wheel/boto3/data/ec2/2015-10-01
2024-05-01 16:23:42,960 root INFO copying build/lib/boto3/data/ec2/2015-10-01/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/ec2/2015-10-01
2024-05-01 16:23:42,961 root INFO creating build/bdist.linux-i686/wheel/boto3/data/ec2/2015-04-15
2024-05-01 16:23:42,961 root INFO copying build/lib/boto3/data/ec2/2015-04-15/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/ec2/2015-04-15
2024-05-01 16:23:42,962 root INFO creating build/bdist.linux-i686/wheel/boto3/data/ec2/2016-11-15
2024-05-01 16:23:42,962 root INFO copying build/lib/boto3/data/ec2/2016-11-15/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/ec2/2016-11-15
2024-05-01 16:23:42,963 root INFO creating build/bdist.linux-i686/wheel/boto3/data/ec2/2015-03-01
2024-05-01 16:23:42,963 root INFO copying build/lib/boto3/data/ec2/2015-03-01/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/ec2/2015-03-01
2024-05-01 16:23:42,964 root INFO creating build/bdist.linux-i686/wheel/boto3/data/ec2/2016-04-01
2024-05-01 16:23:42,964 root INFO copying build/lib/boto3/data/ec2/2016-04-01/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/ec2/2016-04-01
2024-05-01 16:23:42,965 root INFO creating build/bdist.linux-i686/wheel/boto3/data/ec2/2014-10-01
2024-05-01 16:23:42,965 root INFO copying build/lib/boto3/data/ec2/2014-10-01/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/ec2/2014-10-01
2024-05-01 16:23:42,966 root INFO creating build/bdist.linux-i686/wheel/boto3/data/ec2/2016-09-15
2024-05-01 16:23:42,966 root INFO copying build/lib/boto3/data/ec2/2016-09-15/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/ec2/2016-09-15
2024-05-01 16:23:42,967 root INFO creating build/bdist.linux-i686/wheel/boto3/data/sqs
2024-05-01 16:23:42,968 root INFO creating build/bdist.linux-i686/wheel/boto3/data/sqs/2012-11-05
2024-05-01 16:23:42,968 root INFO copying build/lib/boto3/data/sqs/2012-11-05/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/sqs/2012-11-05
2024-05-01 16:23:42,968 root INFO creating build/bdist.linux-i686/wheel/boto3/data/cloudformation
2024-05-01 16:23:42,969 root INFO creating build/bdist.linux-i686/wheel/boto3/data/cloudformation/2010-05-15
2024-05-01 16:23:42,969 root INFO copying build/lib/boto3/data/cloudformation/2010-05-15/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/cloudformation/2010-05-15
2024-05-01 16:23:42,970 root INFO creating build/bdist.linux-i686/wheel/boto3/data/sns
2024-05-01 16:23:42,970 root INFO creating build/bdist.linux-i686/wheel/boto3/data/sns/2010-03-31
2024-05-01 16:23:42,971 root INFO copying build/lib/boto3/data/sns/2010-03-31/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/sns/2010-03-31
2024-05-01 16:23:42,971 root INFO creating build/bdist.linux-i686/wheel/boto3/data/iam
2024-05-01 16:23:42,971 root INFO creating build/bdist.linux-i686/wheel/boto3/data/iam/2010-05-08
2024-05-01 16:23:42,972 root INFO copying build/lib/boto3/data/iam/2010-05-08/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/iam/2010-05-08
2024-05-01 16:23:42,972 root INFO creating build/bdist.linux-i686/wheel/boto3/data/opsworks
2024-05-01 16:23:42,973 root INFO creating build/bdist.linux-i686/wheel/boto3/data/opsworks/2013-02-18
2024-05-01 16:23:42,973 root INFO copying build/lib/boto3/data/opsworks/2013-02-18/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/opsworks/2013-02-18
2024-05-01 16:23:42,974 root INFO creating build/bdist.linux-i686/wheel/boto3/data/dynamodb
2024-05-01 16:23:42,974 root INFO creating build/bdist.linux-i686/wheel/boto3/data/dynamodb/2012-08-10
2024-05-01 16:23:42,975 root INFO copying build/lib/boto3/data/dynamodb/2012-08-10/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/dynamodb/2012-08-10
2024-05-01 16:23:42,975 root INFO creating build/bdist.linux-i686/wheel/boto3/data/cloudwatch
2024-05-01 16:23:42,975 root INFO creating build/bdist.linux-i686/wheel/boto3/data/cloudwatch/2010-08-01
2024-05-01 16:23:42,976 root INFO copying build/lib/boto3/data/cloudwatch/2010-08-01/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/cloudwatch/2010-08-01
2024-05-01 16:23:42,976 root INFO creating build/bdist.linux-i686/wheel/boto3/data/glacier
2024-05-01 16:23:42,977 root INFO creating build/bdist.linux-i686/wheel/boto3/data/glacier/2012-06-01
2024-05-01 16:23:42,977 root INFO copying build/lib/boto3/data/glacier/2012-06-01/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/glacier/2012-06-01
2024-05-01 16:23:42,978 root INFO creating build/bdist.linux-i686/wheel/boto3/data/s3
2024-05-01 16:23:42,978 root INFO creating build/bdist.linux-i686/wheel/boto3/data/s3/2006-03-01
2024-05-01 16:23:42,978 root INFO copying build/lib/boto3/data/s3/2006-03-01/resources-1.json -> build/bdist.linux-i686/wheel/boto3/data/s3/2006-03-01
2024-05-01 16:23:42,979 root INFO copying build/lib/boto3/compat.py -> build/bdist.linux-i686/wheel/boto3
2024-05-01 16:23:42,979 root INFO creating build/bdist.linux-i686/wheel/boto3/s3
2024-05-01 16:23:42,980 root INFO copying build/lib/boto3/s3/transfer.py -> build/bdist.linux-i686/wheel/boto3/s3
2024-05-01 16:23:42,980 root INFO copying build/lib/boto3/s3/__init__.py -> build/bdist.linux-i686/wheel/boto3/s3
2024-05-01 16:23:42,981 root INFO copying build/lib/boto3/s3/inject.py -> build/bdist.linux-i686/wheel/boto3/s3
2024-05-01 16:23:42,981 root INFO copying build/lib/boto3/s3/constants.py -> build/bdist.linux-i686/wheel/boto3/s3
2024-05-01 16:23:42,982 root INFO copying build/lib/boto3/crt.py -> build/bdist.linux-i686/wheel/boto3
2024-05-01 16:23:42,982 root INFO copying build/lib/boto3/exceptions.py -> build/bdist.linux-i686/wheel/boto3
2024-05-01 16:23:42,982 root INFO running install_egg_info
2024-05-01 16:23:42,990 root INFO Copying boto3.egg-info to build/bdist.linux-i686/wheel/boto3-1.34.95-py3.12.egg-info
2024-05-01 16:23:42,992 root INFO running install_scripts
2024-05-01 16:23:42,999 wheel INFO creating build/bdist.linux-i686/wheel/boto3-1.34.95.dist-info/WHEEL
2024-05-01 16:23:43,000 wheel INFO creating '/home/buildozer/aports/community/py3-boto3/src/boto3-1.34.95/.dist/.tmp-9ydimuxt/boto3-1.34.95-py3-none-any.whl' and adding 'build/bdist.linux-i686/wheel' to it
2024-05-01 16:23:43,001 wheel INFO adding 'boto3/__init__.py'
2024-05-01 16:23:43,001 wheel INFO adding 'boto3/compat.py'
2024-05-01 16:23:43,002 wheel INFO adding 'boto3/crt.py'
2024-05-01 16:23:43,002 wheel INFO adding 'boto3/exceptions.py'
2024-05-01 16:23:43,003 wheel INFO adding 'boto3/session.py'
2024-05-01 16:23:43,004 wheel INFO adding 'boto3/utils.py'
2024-05-01 16:23:43,005 wheel INFO adding 'boto3/data/cloudformation/2010-05-15/resources-1.json'
2024-05-01 16:23:43,005 wheel INFO adding 'boto3/data/cloudwatch/2010-08-01/resources-1.json'
2024-05-01 16:23:43,006 wheel INFO adding 'boto3/data/dynamodb/2012-08-10/resources-1.json'
2024-05-01 16:23:43,007 wheel INFO adding 'boto3/data/ec2/2014-10-01/resources-1.json'
2024-05-01 16:23:43,009 wheel INFO adding 'boto3/data/ec2/2015-03-01/resources-1.json'
2024-05-01 16:23:43,010 wheel INFO adding 'boto3/data/ec2/2015-04-15/resources-1.json'
2024-05-01 16:23:43,012 wheel INFO adding 'boto3/data/ec2/2015-10-01/resources-1.json'
2024-05-01 16:23:43,013 wheel INFO adding 'boto3/data/ec2/2016-04-01/resources-1.json'
2024-05-01 16:23:43,015 wheel INFO adding 'boto3/data/ec2/2016-09-15/resources-1.json'
2024-05-01 16:23:43,016 wheel INFO adding 'boto3/data/ec2/2016-11-15/resources-1.json'
2024-05-01 16:23:43,018 wheel INFO adding 'boto3/data/glacier/2012-06-01/resources-1.json'
2024-05-01 16:23:43,019 wheel INFO adding 'boto3/data/iam/2010-05-08/resources-1.json'
2024-05-01 16:23:43,020 wheel INFO adding 'boto3/data/opsworks/2013-02-18/resources-1.json'
2024-05-01 16:23:43,021 wheel INFO adding 'boto3/data/s3/2006-03-01/resources-1.json'
2024-05-01 16:23:43,022 wheel INFO adding 'boto3/data/sns/2010-03-31/resources-1.json'
2024-05-01 16:23:43,022 wheel INFO adding 'boto3/data/sqs/2012-11-05/resources-1.json'
2024-05-01 16:23:43,023 wheel INFO adding 'boto3/docs/__init__.py'
2024-05-01 16:23:43,023 wheel INFO adding 'boto3/docs/action.py'
2024-05-01 16:23:43,024 wheel INFO adding 'boto3/docs/attr.py'
2024-05-01 16:23:43,024 wheel INFO adding 'boto3/docs/base.py'
2024-05-01 16:23:43,025 wheel INFO adding 'boto3/docs/client.py'
2024-05-01 16:23:43,025 wheel INFO adding 'boto3/docs/collection.py'
2024-05-01 16:23:43,026 wheel INFO adding 'boto3/docs/docstring.py'
2024-05-01 16:23:43,026 wheel INFO adding 'boto3/docs/method.py'
2024-05-01 16:23:43,027 wheel INFO adding 'boto3/docs/resource.py'
2024-05-01 16:23:43,027 wheel INFO adding 'boto3/docs/service.py'
2024-05-01 16:23:43,028 wheel INFO adding 'boto3/docs/subresource.py'
2024-05-01 16:23:43,028 wheel INFO adding 'boto3/docs/utils.py'
2024-05-01 16:23:43,029 wheel INFO adding 'boto3/docs/waiter.py'
2024-05-01 16:23:43,029 wheel INFO adding 'boto3/dynamodb/__init__.py'
2024-05-01 16:23:43,030 wheel INFO adding 'boto3/dynamodb/conditions.py'
2024-05-01 16:23:43,030 wheel INFO adding 'boto3/dynamodb/table.py'
2024-05-01 16:23:43,031 wheel INFO adding 'boto3/dynamodb/transform.py'
2024-05-01 16:23:43,031 wheel INFO adding 'boto3/dynamodb/types.py'
2024-05-01 16:23:43,032 wheel INFO adding 'boto3/ec2/__init__.py'
2024-05-01 16:23:43,032 wheel INFO adding 'boto3/ec2/createtags.py'
2024-05-01 16:23:43,033 wheel INFO adding 'boto3/ec2/deletetags.py'
2024-05-01 16:23:43,033 wheel INFO adding 'boto3/resources/__init__.py'
2024-05-01 16:23:43,034 wheel INFO adding 'boto3/resources/action.py'
2024-05-01 16:23:43,034 wheel INFO adding 'boto3/resources/base.py'
2024-05-01 16:23:43,035 wheel INFO adding 'boto3/resources/collection.py'
2024-05-01 16:23:43,035 wheel INFO adding 'boto3/resources/factory.py'
2024-05-01 16:23:43,036 wheel INFO adding 'boto3/resources/model.py'
2024-05-01 16:23:43,037 wheel INFO adding 'boto3/resources/params.py'
2024-05-01 16:23:43,038 wheel INFO adding 'boto3/resources/response.py'
2024-05-01 16:23:43,038 wheel INFO adding 'boto3/s3/__init__.py'
2024-05-01 16:23:43,039 wheel INFO adding 'boto3/s3/constants.py'
2024-05-01 16:23:43,039 wheel INFO adding 'boto3/s3/inject.py'
2024-05-01 16:23:43,040 wheel INFO adding 'boto3/s3/transfer.py'
2024-05-01 16:23:43,041 wheel INFO adding 'boto3-1.34.95.dist-info/LICENSE'
2024-05-01 16:23:43,042 wheel INFO adding 'boto3-1.34.95.dist-info/METADATA'
2024-05-01 16:23:43,042 wheel INFO adding 'boto3-1.34.95.dist-info/NOTICE'
2024-05-01 16:23:43,042 wheel INFO adding 'boto3-1.34.95.dist-info/WHEEL'
2024-05-01 16:23:43,043 wheel INFO adding 'boto3-1.34.95.dist-info/top_level.txt'
2024-05-01 16:23:43,044 wheel INFO adding 'boto3-1.34.95.dist-info/RECORD'
2024-05-01 16:23:43,045 wheel INFO removing build/bdist.linux-i686/wheel
2024-05-01 16:23:43,053 gpep517 INFO The backend produced .dist/boto3-1.34.95-py3-none-any.whl
boto3-1.34.95-py3-none-any.whl
>>> py3-boto3: Entering fakeroot...
>>> py3-boto3-pyc*: Running split function pyc...
'/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3/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__'
'/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3/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__'
'/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3/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__'
'/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3/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__'
'/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3/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__'
'/home/buildozer/aports/community/py3-boto3/pkg/py3-boto3/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__'
>>> 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: 460.0 KB
>>> py3-boto3-pyc*: Compressing data...
>>> py3-boto3-pyc*: Create checksum...
>>> py3-boto3-pyc*: Create py3-boto3-pyc-1.34.95-r0.apk
>>> py3-boto3*: Tracing dependencies...
	py3-botocore
	py3-jmespath
	py3-s3transfer
	python3~3.12
>>> py3-boto3*: Package size: 1.2 MB
>>> py3-boto3*: Compressing data...
>>> py3-boto3*: Create checksum...
>>> py3-boto3*: Create py3-boto3-1.34.95-r0.apk
>>> py3-boto3: Build complete at Wed, 01 May 2024 16:23:46 +0000 elapsed time 0h 0m 9s
>>> py3-boto3: Cleaning up srcdir
>>> py3-boto3: Cleaning up pkgdir
>>> py3-boto3: Uninstalling dependencies...
(1/37) Purging .makedepends-py3-boto3 (20240501.162339)
(2/37) Purging py3-s3transfer-pyc (0.10.1-r0)
(3/37) Purging py3-s3transfer (0.10.1-r0)
(4/37) Purging py3-botocore-pyc (1.34.39-r0)
(5/37) Purging py3-botocore (1.34.39-r0)
(6/37) Purging py3-certifi-pyc (2024.2.2-r1)
(7/37) Purging py3-certifi (2024.2.2-r1)
(8/37) Purging py3-dateutil-pyc (2.9.0-r1)
(9/37) Purging py3-dateutil (2.9.0-r1)
(10/37) Purging py3-six-pyc (1.16.0-r9)
(11/37) Purging py3-six (1.16.0-r9)
(12/37) Purging py3-jmespath-pyc (1.0.1-r2)
(13/37) Purging py3-jmespath (1.0.1-r2)
(14/37) Purging py3-urllib3-pyc (1.26.18-r1)
(15/37) Purging py3-urllib3 (1.26.18-r1)
(16/37) Purging py3-gpep517-pyc (15-r2)
(17/37) Purging py3-gpep517 (15-r2)
(18/37) Purging py3-installer-pyc (0.7.0-r2)
(19/37) Purging py3-installer (0.7.0-r2)
(20/37) Purging py3-setuptools-pyc (69.5.1-r0)
(21/37) Purging py3-setuptools (69.5.1-r0)
(22/37) Purging py3-wheel-pyc (0.42.0-r1)
(23/37) Purging py3-wheel (0.42.0-r1)
(24/37) Purging py3-packaging-pyc (24.0-r1)
(25/37) Purging py3-packaging (24.0-r1)
(26/37) Purging py3-parsing-pyc (3.1.2-r1)
(27/37) Purging py3-parsing (3.1.2-r1)
(28/37) Purging python3-pyc (3.12.3-r1)
(29/37) Purging python3-pycache-pyc0 (3.12.3-r1)
(30/37) Purging pyc (3.12.3-r1)
(31/37) Purging python3 (3.12.3-r1)
(32/37) Purging gdbm (1.23-r1)
(33/37) Purging libffi (3.4.6-r0)
(34/37) Purging libpanelw (6.4_p20240330-r0)
(35/37) Purging mpdecimal (4.0.0-r0)
(36/37) Purging readline (8.2.10-r0)
(37/37) Purging sqlite-libs (3.45.3-r0)
Executing busybox-1.36.1-r26.trigger
OK: 380 MiB in 113 packages
>>> py3-boto3: Updating the community/x86 repository index...
>>> py3-boto3: Signing the index...