==> Synchronizing chroot copy [/home/leming/armv8/root] -> [leming]...done
==> Making package: python-boto3 1.38.41-1 (Thu Jun 26 06:48:19 2025)
==> Retrieving sources...
-> Found python-boto3-1.38.41.tar.gz
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha512sums...
python-boto3-1.38.41.tar.gz ... Passed
==> Making package: python-boto3 1.38.41-1 (Thu Jun 26 06:48:26 2025)
==> Checking runtime dependencies...
==> Installing missing dependencies...
[?25lresolving dependencies...
looking for conflicting packages...
Packages (7) python-certifi-2025.06.15-1 python-dateutil-2.9.0-6
python-six-1.17.0-1 python-urllib3-2.5.0-1
python-botocore-1.38.41-1 python-jmespath-1.0.1-5
python-s3transfer-0.13.0-1
Total Installed Size: 107.26 MiB
:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing python-certifi...
installing python-six...
installing python-dateutil...
installing python-jmespath...
installing python-urllib3...
Optional dependencies for python-urllib3
python-brotli: Brotli support
python-brotlicffi: Brotli support
python-h2: HTTP/2 support
python-pysocks: SOCKS support
python-zstandard: Zstandard support
installing python-botocore...
Optional dependencies for python-botocore
python-awscrt: use AWS Common Runtime
installing python-s3transfer...
Optional dependencies for python-s3transfer
python-awscrt: use AWS Common Runtime
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[?25h==> Checking buildtime dependencies...
==> Installing missing dependencies...
[?25lresolving dependencies...
looking for conflicting packages...
Packages (13) python-autocommand-2.2.2-7 python-jaraco.collections-5.1.0-1
python-jaraco.context-6.0.1-1 python-jaraco.functools-4.1.0-1
python-jaraco.text-4.0.0-2 python-more-itertools-10.7.0-1
python-packaging-25.0-1 python-platformdirs-4.3.6-2
python-pyproject-hooks-1.2.0-3 python-build-1.2.2-3
python-installer-0.7.0-10 python-setuptools-1:80.9.0-1
python-wheel-0.45.1-1
Total Installed Size: 10.36 MiB
:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing python-packaging...
installing python-pyproject-hooks...
installing python-build...
Optional dependencies for python-build
python-pip: to use as the Python package installer (default)
python-uv: to use as the Python package installer
python-virtualenv: to use virtualenv for build isolation
installing python-installer...
installing python-more-itertools...
installing python-jaraco.functools...
installing python-jaraco.context...
installing python-autocommand...
installing python-jaraco.text...
Optional dependencies for python-jaraco.text
python-inflect: for show-newlines script
installing python-jaraco.collections...
installing python-platformdirs...
installing python-wheel...
Optional dependencies for python-wheel
python-keyring: for wheel.signatures
python-xdg: for wheel.signatures
python-setuptools: for legacy bdist_wheel subcommand [pending]
installing python-setuptools...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
[?25h==> Retrieving sources...
-> Found python-boto3-1.38.41.tar.gz
==> WARNING: Skipping all source file integrity checks.
==> Extracting sources...
-> Extracting python-boto3-1.38.41.tar.gz with bsdtar
==> Starting build()...
* Getting build dependencies for wheel...
/usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!
********************************************************************************
Please consider removing the following classifiers in favor of a SPDX license expression:
License :: OSI Approved :: Apache Software License
See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
********************************************************************************
!!
self._finalize_license_expression()
running egg_info
creating boto3.egg-info
writing boto3.egg-info/PKG-INFO
writing dependency_links to boto3.egg-info/dependency_links.txt
writing requirements to boto3.egg-info/requires.txt
writing top-level names to boto3.egg-info/top_level.txt
writing manifest file 'boto3.egg-info/SOURCES.txt'
reading manifest file 'boto3.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
adding license file 'NOTICE'
writing manifest file 'boto3.egg-info/SOURCES.txt'
* Building wheel...
/usr/lib/python3.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!
********************************************************************************
Please consider removing the following classifiers in favor of a SPDX license expression:
License :: OSI Approved :: Apache Software License
See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details.
********************************************************************************
!!
self._finalize_license_expression()
running bdist_wheel
running build
running build_py
creating build/lib/boto3
copying boto3/session.py -> build/lib/boto3
copying boto3/crt.py -> build/lib/boto3
copying boto3/compat.py -> build/lib/boto3
copying boto3/exceptions.py -> build/lib/boto3
copying boto3/utils.py -> build/lib/boto3
copying boto3/__init__.py -> build/lib/boto3
creating build/lib/boto3/ec2
copying boto3/ec2/createtags.py -> build/lib/boto3/ec2
copying boto3/ec2/deletetags.py -> build/lib/boto3/ec2
copying boto3/ec2/__init__.py -> build/lib/boto3/ec2
creating build/lib/boto3/docs
copying boto3/docs/method.py -> build/lib/boto3/docs
copying boto3/docs/attr.py -> build/lib/boto3/docs
copying boto3/docs/action.py -> build/lib/boto3/docs
copying boto3/docs/base.py -> build/lib/boto3/docs
copying boto3/docs/subresource.py -> build/lib/boto3/docs
copying boto3/docs/collection.py -> build/lib/boto3/docs
copying boto3/docs/waiter.py -> build/lib/boto3/docs
copying boto3/docs/client.py -> build/lib/boto3/docs
copying boto3/docs/service.py -> build/lib/boto3/docs
copying boto3/docs/resource.py -> build/lib/boto3/docs
copying boto3/docs/docstring.py -> build/lib/boto3/docs
copying boto3/docs/utils.py -> build/lib/boto3/docs
copying boto3/docs/__init__.py -> build/lib/boto3/docs
creating build/lib/boto3/resources
copying boto3/resources/action.py -> build/lib/boto3/resources
copying boto3/resources/response.py -> build/lib/boto3/resources
copying boto3/resources/base.py -> build/lib/boto3/resources
copying boto3/resources/params.py -> build/lib/boto3/resources
copying boto3/resources/model.py -> build/lib/boto3/resources
copying boto3/resources/collection.py -> build/lib/boto3/resources
copying boto3/resources/factory.py -> build/lib/boto3/resources
copying boto3/resources/__init__.py -> build/lib/boto3/resources
creating build/lib/boto3/s3
copying boto3/s3/constants.py -> build/lib/boto3/s3
copying boto3/s3/transfer.py -> build/lib/boto3/s3
copying boto3/s3/inject.py -> build/lib/boto3/s3
copying boto3/s3/__init__.py -> build/lib/boto3/s3
creating build/lib/boto3/dynamodb
copying boto3/dynamodb/table.py -> build/lib/boto3/dynamodb
copying boto3/dynamodb/transform.py -> build/lib/boto3/dynamodb
copying boto3/dynamodb/types.py -> build/lib/boto3/dynamodb
copying boto3/dynamodb/__init__.py -> build/lib/boto3/dynamodb
copying boto3/dynamodb/conditions.py -> build/lib/boto3/dynamodb
running egg_info
writing boto3.egg-info/PKG-INFO
writing dependency_links to boto3.egg-info/dependency_links.txt
writing requirements to boto3.egg-info/requires.txt
writing top-level names to boto3.egg-info/top_level.txt
reading manifest file 'boto3.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE'
adding license file 'NOTICE'
writing manifest file 'boto3.egg-info/SOURCES.txt'
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.cloudformation' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'boto3.data.cloudformation' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'boto3.data.cloudformation' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'boto3.data.cloudformation' to be distributed and are
already explicitly excluding 'boto3.data.cloudformation' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.cloudwatch' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'boto3.data.cloudwatch' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'boto3.data.cloudwatch' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'boto3.data.cloudwatch' to be distributed and are
already explicitly excluding 'boto3.data.cloudwatch' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.dynamodb' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'boto3.data.dynamodb' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'boto3.data.dynamodb' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'boto3.data.dynamodb' to be distributed and are
already explicitly excluding 'boto3.data.dynamodb' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.ec2' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'boto3.data.ec2' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'boto3.data.ec2' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'boto3.data.ec2' to be distributed and are
already explicitly excluding 'boto3.data.ec2' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.glacier' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'boto3.data.glacier' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'boto3.data.glacier' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'boto3.data.glacier' to be distributed and are
already explicitly excluding 'boto3.data.glacier' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.iam' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'boto3.data.iam' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'boto3.data.iam' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'boto3.data.iam' to be distributed and are
already explicitly excluding 'boto3.data.iam' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.opsworks' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'boto3.data.opsworks' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'boto3.data.opsworks' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'boto3.data.opsworks' to be distributed and are
already explicitly excluding 'boto3.data.opsworks' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.s3' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'boto3.data.s3' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'boto3.data.s3' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'boto3.data.s3' to be distributed and are
already explicitly excluding 'boto3.data.s3' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.sns' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'boto3.data.sns' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'boto3.data.sns' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'boto3.data.sns' to be distributed and are
already explicitly excluding 'boto3.data.sns' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.data.sqs' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'boto3.data.sqs' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'boto3.data.sqs' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'boto3.data.sqs' to be distributed and are
already explicitly excluding 'boto3.data.sqs' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
/usr/lib/python3.13/site-packages/setuptools/command/build_py.py:212: _Warning: Package 'boto3.examples' is absent from the `packages` configuration.
!!
********************************************************************************
############################
# Package would be ignored #
############################
Python recognizes 'boto3.examples' as an importable package[^1],
but it is absent from setuptools' `packages` configuration.
This leads to an ambiguous overall configuration. If you want to distribute this
package, please make sure that 'boto3.examples' is explicitly added
to the `packages` configuration field.
Alternatively, you can also rely on setuptools' discovery methods
(for example by using `find_namespace_packages(...)`/`find_namespace:`
instead of `find_packages(...)`/`find:`).
You can read more about "package discovery" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/package_discovery.html
If you don't want 'boto3.examples' to be distributed and are
already explicitly excluding 'boto3.examples' via
`find_namespace_packages(...)/find_namespace` or `find_packages(...)/find`,
you can try to use `exclude_package_data`, or `include-package-data=False` in
combination with a more fine grained `package-data` configuration.
You can read more about "package data files" on setuptools documentation page:
- https://setuptools.pypa.io/en/latest/userguide/datafiles.html
[^1]: For Python, any directory (with suitable naming) can be imported,
even if it does not contain any `.py` files.
On the other hand, currently there is no concept of package data
directory, all directories are treated like packages.
********************************************************************************
!!
check.warn(importable)
creating build/lib/boto3/data/cloudformation/2010-05-15
copying boto3/data/cloudformation/2010-05-15/resources-1.json -> build/lib/boto3/data/cloudformation/2010-05-15
creating build/lib/boto3/data/cloudwatch/2010-08-01
copying boto3/data/cloudwatch/2010-08-01/resources-1.json -> build/lib/boto3/data/cloudwatch/2010-08-01
creating build/lib/boto3/data/dynamodb/2012-08-10
copying boto3/data/dynamodb/2012-08-10/resources-1.json -> build/lib/boto3/data/dynamodb/2012-08-10
creating build/lib/boto3/data/ec2/2014-10-01
copying boto3/data/ec2/2014-10-01/resources-1.json -> build/lib/boto3/data/ec2/2014-10-01
creating build/lib/boto3/data/ec2/2015-03-01
copying boto3/data/ec2/2015-03-01/resources-1.json -> build/lib/boto3/data/ec2/2015-03-01
creating build/lib/boto3/data/ec2/2015-04-15
copying boto3/data/ec2/2015-04-15/resources-1.json -> build/lib/boto3/data/ec2/2015-04-15
creating build/lib/boto3/data/ec2/2015-10-01
copying boto3/data/ec2/2015-10-01/resources-1.json -> build/lib/boto3/data/ec2/2015-10-01
creating build/lib/boto3/data/ec2/2016-04-01
copying boto3/data/ec2/2016-04-01/resources-1.json -> build/lib/boto3/data/ec2/2016-04-01
creating build/lib/boto3/data/ec2/2016-09-15
copying boto3/data/ec2/2016-09-15/resources-1.json -> build/lib/boto3/data/ec2/2016-09-15
creating build/lib/boto3/data/ec2/2016-11-15
copying boto3/data/ec2/2016-11-15/resources-1.json -> build/lib/boto3/data/ec2/2016-11-15
creating build/lib/boto3/data/glacier/2012-06-01
copying boto3/data/glacier/2012-06-01/resources-1.json -> build/lib/boto3/data/glacier/2012-06-01
creating build/lib/boto3/data/iam/2010-05-08
copying boto3/data/iam/2010-05-08/resources-1.json -> build/lib/boto3/data/iam/2010-05-08
creating build/lib/boto3/data/opsworks/2013-02-18
copying boto3/data/opsworks/2013-02-18/resources-1.json -> build/lib/boto3/data/opsworks/2013-02-18
creating build/lib/boto3/data/s3/2006-03-01
copying boto3/data/s3/2006-03-01/resources-1.json -> build/lib/boto3/data/s3/2006-03-01
creating build/lib/boto3/data/sns/2010-03-31
copying boto3/data/sns/2010-03-31/resources-1.json -> build/lib/boto3/data/sns/2010-03-31
creating build/lib/boto3/data/sqs/2012-11-05
copying boto3/data/sqs/2012-11-05/resources-1.json -> build/lib/boto3/data/sqs/2012-11-05
creating build/lib/boto3/examples
copying boto3/examples/cloudfront.rst -> build/lib/boto3/examples
copying boto3/examples/s3.rst -> build/lib/boto3/examples
installing to build/bdist.linux-aarch64/wheel
running install
running install_lib
creating build/bdist.linux-aarch64/wheel
creating build/bdist.linux-aarch64/wheel/boto3
copying build/lib/boto3/session.py -> build/bdist.linux-aarch64/wheel/./boto3
copying build/lib/boto3/crt.py -> build/bdist.linux-aarch64/wheel/./boto3
creating build/bdist.linux-aarch64/wheel/boto3/ec2
copying build/lib/boto3/ec2/createtags.py -> build/bdist.linux-aarch64/wheel/./boto3/ec2
copying build/lib/boto3/ec2/deletetags.py -> build/bdist.linux-aarch64/wheel/./boto3/ec2
copying build/lib/boto3/ec2/__init__.py -> build/bdist.linux-aarch64/wheel/./boto3/ec2
copying build/lib/boto3/compat.py -> build/bdist.linux-aarch64/wheel/./boto3
copying build/lib/boto3/exceptions.py -> build/bdist.linux-aarch64/wheel/./boto3
creating build/bdist.linux-aarch64/wheel/boto3/docs
copying build/lib/boto3/docs/method.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/attr.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/action.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/base.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/subresource.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/collection.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/waiter.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/client.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/service.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/resource.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/docstring.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/utils.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
copying build/lib/boto3/docs/__init__.py -> build/bdist.linux-aarch64/wheel/./boto3/docs
creating build/bdist.linux-aarch64/wheel/boto3/data
creating build/bdist.linux-aarch64/wheel/boto3/data/cloudwatch
creating build/bdist.linux-aarch64/wheel/boto3/data/cloudwatch/2010-08-01
copying build/lib/boto3/data/cloudwatch/2010-08-01/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/cloudwatch/2010-08-01
creating build/bdist.linux-aarch64/wheel/boto3/data/iam
creating build/bdist.linux-aarch64/wheel/boto3/data/iam/2010-05-08
copying build/lib/boto3/data/iam/2010-05-08/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/iam/2010-05-08
creating build/bdist.linux-aarch64/wheel/boto3/data/glacier
creating build/bdist.linux-aarch64/wheel/boto3/data/glacier/2012-06-01
copying build/lib/boto3/data/glacier/2012-06-01/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/glacier/2012-06-01
creating build/bdist.linux-aarch64/wheel/boto3/data/ec2
creating build/bdist.linux-aarch64/wheel/boto3/data/ec2/2014-10-01
copying build/lib/boto3/data/ec2/2014-10-01/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/ec2/2014-10-01
creating build/bdist.linux-aarch64/wheel/boto3/data/ec2/2016-04-01
copying build/lib/boto3/data/ec2/2016-04-01/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/ec2/2016-04-01
creating build/bdist.linux-aarch64/wheel/boto3/data/ec2/2016-09-15
copying build/lib/boto3/data/ec2/2016-09-15/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/ec2/2016-09-15
creating build/bdist.linux-aarch64/wheel/boto3/data/ec2/2015-04-15
copying build/lib/boto3/data/ec2/2015-04-15/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/ec2/2015-04-15
creating build/bdist.linux-aarch64/wheel/boto3/data/ec2/2015-10-01
copying build/lib/boto3/data/ec2/2015-10-01/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/ec2/2015-10-01
creating build/bdist.linux-aarch64/wheel/boto3/data/ec2/2015-03-01
copying build/lib/boto3/data/ec2/2015-03-01/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/ec2/2015-03-01
creating build/bdist.linux-aarch64/wheel/boto3/data/ec2/2016-11-15
copying build/lib/boto3/data/ec2/2016-11-15/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/ec2/2016-11-15
creating build/bdist.linux-aarch64/wheel/boto3/data/cloudformation
creating build/bdist.linux-aarch64/wheel/boto3/data/cloudformation/2010-05-15
copying build/lib/boto3/data/cloudformation/2010-05-15/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/cloudformation/2010-05-15
creating build/bdist.linux-aarch64/wheel/boto3/data/sqs
creating build/bdist.linux-aarch64/wheel/boto3/data/sqs/2012-11-05
copying build/lib/boto3/data/sqs/2012-11-05/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/sqs/2012-11-05
creating build/bdist.linux-aarch64/wheel/boto3/data/s3
creating build/bdist.linux-aarch64/wheel/boto3/data/s3/2006-03-01
copying build/lib/boto3/data/s3/2006-03-01/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/s3/2006-03-01
creating build/bdist.linux-aarch64/wheel/boto3/data/dynamodb
creating build/bdist.linux-aarch64/wheel/boto3/data/dynamodb/2012-08-10
copying build/lib/boto3/data/dynamodb/2012-08-10/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/dynamodb/2012-08-10
creating build/bdist.linux-aarch64/wheel/boto3/data/opsworks
creating build/bdist.linux-aarch64/wheel/boto3/data/opsworks/2013-02-18
copying build/lib/boto3/data/opsworks/2013-02-18/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/opsworks/2013-02-18
creating build/bdist.linux-aarch64/wheel/boto3/data/sns
creating build/bdist.linux-aarch64/wheel/boto3/data/sns/2010-03-31
copying build/lib/boto3/data/sns/2010-03-31/resources-1.json -> build/bdist.linux-aarch64/wheel/./boto3/data/sns/2010-03-31
creating build/bdist.linux-aarch64/wheel/boto3/resources
copying build/lib/boto3/resources/action.py -> build/bdist.linux-aarch64/wheel/./boto3/resources
copying build/lib/boto3/resources/response.py -> build/bdist.linux-aarch64/wheel/./boto3/resources
copying build/lib/boto3/resources/base.py -> build/bdist.linux-aarch64/wheel/./boto3/resources
copying build/lib/boto3/resources/params.py -> build/bdist.linux-aarch64/wheel/./boto3/resources
copying build/lib/boto3/resources/model.py -> build/bdist.linux-aarch64/wheel/./boto3/resources
copying build/lib/boto3/resources/collection.py -> build/bdist.linux-aarch64/wheel/./boto3/resources
copying build/lib/boto3/resources/factory.py -> build/bdist.linux-aarch64/wheel/./boto3/resources
copying build/lib/boto3/resources/__init__.py -> build/bdist.linux-aarch64/wheel/./boto3/resources
creating build/bdist.linux-aarch64/wheel/boto3/s3
copying build/lib/boto3/s3/constants.py -> build/bdist.linux-aarch64/wheel/./boto3/s3
copying build/lib/boto3/s3/transfer.py -> build/bdist.linux-aarch64/wheel/./boto3/s3
copying build/lib/boto3/s3/inject.py -> build/bdist.linux-aarch64/wheel/./boto3/s3
copying build/lib/boto3/s3/__init__.py -> build/bdist.linux-aarch64/wheel/./boto3/s3
creating build/bdist.linux-aarch64/wheel/boto3/dynamodb
copying build/lib/boto3/dynamodb/table.py -> build/bdist.linux-aarch64/wheel/./boto3/dynamodb
copying build/lib/boto3/dynamodb/transform.py -> build/bdist.linux-aarch64/wheel/./boto3/dynamodb
copying build/lib/boto3/dynamodb/types.py -> build/bdist.linux-aarch64/wheel/./boto3/dynamodb
copying build/lib/boto3/dynamodb/__init__.py -> build/bdist.linux-aarch64/wheel/./boto3/dynamodb
copying build/lib/boto3/dynamodb/conditions.py -> build/bdist.linux-aarch64/wheel/./boto3/dynamodb
copying build/lib/boto3/utils.py -> build/bdist.linux-aarch64/wheel/./boto3
creating build/bdist.linux-aarch64/wheel/boto3/examples
copying build/lib/boto3/examples/cloudfront.rst -> build/bdist.linux-aarch64/wheel/./boto3/examples
copying build/lib/boto3/examples/s3.rst -> build/bdist.linux-aarch64/wheel/./boto3/examples
copying build/lib/boto3/__init__.py -> build/bdist.linux-aarch64/wheel/./boto3
running install_egg_info
Copying boto3.egg-info to build/bdist.linux-aarch64/wheel/./boto3-1.38.41-py3.13.egg-info
running install_scripts
creating build/bdist.linux-aarch64/wheel/boto3-1.38.41.dist-info/WHEEL
creating '/build/python-boto3/src/boto3-1.38.41/dist/.tmp-nc09m3_t/boto3-1.38.41-py3-none-any.whl' and adding 'build/bdist.linux-aarch64/wheel' to it
adding 'boto3/__init__.py'
adding 'boto3/compat.py'
adding 'boto3/crt.py'
adding 'boto3/exceptions.py'
adding 'boto3/session.py'
adding 'boto3/utils.py'
adding 'boto3/data/cloudformation/2010-05-15/resources-1.json'
adding 'boto3/data/cloudwatch/2010-08-01/resources-1.json'
adding 'boto3/data/dynamodb/2012-08-10/resources-1.json'
adding 'boto3/data/ec2/2014-10-01/resources-1.json'
adding 'boto3/data/ec2/2015-03-01/resources-1.json'
adding 'boto3/data/ec2/2015-04-15/resources-1.json'
adding 'boto3/data/ec2/2015-10-01/resources-1.json'
adding 'boto3/data/ec2/2016-04-01/resources-1.json'
adding 'boto3/data/ec2/2016-09-15/resources-1.json'
adding 'boto3/data/ec2/2016-11-15/resources-1.json'
adding 'boto3/data/glacier/2012-06-01/resources-1.json'
adding 'boto3/data/iam/2010-05-08/resources-1.json'
adding 'boto3/data/opsworks/2013-02-18/resources-1.json'
adding 'boto3/data/s3/2006-03-01/resources-1.json'
adding 'boto3/data/sns/2010-03-31/resources-1.json'
adding 'boto3/data/sqs/2012-11-05/resources-1.json'
adding 'boto3/docs/__init__.py'
adding 'boto3/docs/action.py'
adding 'boto3/docs/attr.py'
adding 'boto3/docs/base.py'
adding 'boto3/docs/client.py'
adding 'boto3/docs/collection.py'
adding 'boto3/docs/docstring.py'
adding 'boto3/docs/method.py'
adding 'boto3/docs/resource.py'
adding 'boto3/docs/service.py'
adding 'boto3/docs/subresource.py'
adding 'boto3/docs/utils.py'
adding 'boto3/docs/waiter.py'
adding 'boto3/dynamodb/__init__.py'
adding 'boto3/dynamodb/conditions.py'
adding 'boto3/dynamodb/table.py'
adding 'boto3/dynamodb/transform.py'
adding 'boto3/dynamodb/types.py'
adding 'boto3/ec2/__init__.py'
adding 'boto3/ec2/createtags.py'
adding 'boto3/ec2/deletetags.py'
adding 'boto3/examples/cloudfront.rst'
adding 'boto3/examples/s3.rst'
adding 'boto3/resources/__init__.py'
adding 'boto3/resources/action.py'
adding 'boto3/resources/base.py'
adding 'boto3/resources/collection.py'
adding 'boto3/resources/factory.py'
adding 'boto3/resources/model.py'
adding 'boto3/resources/params.py'
adding 'boto3/resources/response.py'
adding 'boto3/s3/__init__.py'
adding 'boto3/s3/constants.py'
adding 'boto3/s3/inject.py'
adding 'boto3/s3/transfer.py'
adding 'boto3-1.38.41.dist-info/licenses/LICENSE'
adding 'boto3-1.38.41.dist-info/licenses/NOTICE'
adding 'boto3-1.38.41.dist-info/METADATA'
adding 'boto3-1.38.41.dist-info/WHEEL'
adding 'boto3-1.38.41.dist-info/top_level.txt'
adding 'boto3-1.38.41.dist-info/RECORD'
removing build/bdist.linux-aarch64/wheel
Successfully built boto3-1.38.41-py3-none-any.whl
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
-> Removing libtool files...
-> Purging unwanted files...
-> Removing static library files...
-> Stripping unneeded symbols from binaries and libraries...
-> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "python-boto3"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: python-boto3 1.38.41-1 (Thu Jun 26 06:48:37 2025)
==> Cleaning up...