>>> py3-pkcs11: Building community/py3-pkcs11 0.7.0-r8 (using abuild 3.15.0_rc3-r2) started Sat, 10 May 2025 11:20:43 +0000
>>> py3-pkcs11: Validating /home/buildozer/aports/community/py3-pkcs11/APKBUILD...
>>> py3-pkcs11: Analyzing dependencies...
>>> py3-pkcs11: Installing for build: build-base py3-asn1crypto py3-cached-property py3-cryptography python3 cython py3-gpep517 py3-setuptools_scm py3-wheel python3-dev py3-oscrypto py3-pytest softhsm
(1/50) Installing libbz2 (1.0.8-r6)
(2/50) Installing gdbm (1.24-r0)
(3/50) Installing mpdecimal (4.0.0-r0)
(4/50) Installing libpanelw (6.5_p20250503-r0)
(5/50) Installing sqlite-libs (3.49.2-r0)
(6/50) Installing python3 (3.12.10-r0)
(7/50) Installing python3-pycache-pyc0 (3.12.10-r0)
(8/50) Installing pyc (3.12.10-r0)
(9/50) Installing py3-asn1crypto-pyc (1.5.1_git20231103-r1)
(10/50) Installing python3-pyc (3.12.10-r0)
(11/50) Installing py3-asn1crypto (1.5.1_git20231103-r1)
(12/50) Installing py3-cached-property (1.5.2-r5)
(13/50) Installing py3-cached-property-pyc (1.5.2-r5)
(14/50) Installing py3-cparser (2.22-r1)
(15/50) Installing py3-cparser-pyc (2.22-r1)
(16/50) Installing py3-cffi (1.17.1-r1)
(17/50) Installing py3-cffi-pyc (1.17.1-r1)
(18/50) Installing py3-cryptography (44.0.3-r0)
(19/50) Installing py3-cryptography-pyc (44.0.3-r0)
(20/50) Installing cython (3.0.12-r0)
(21/50) Installing cython-pyc (3.0.12-r0)
(22/50) Installing py3-installer (0.7.0-r2)
(23/50) Installing py3-installer-pyc (0.7.0-r2)
(24/50) Installing py3-gpep517 (19-r0)
(25/50) Installing py3-gpep517-pyc (19-r0)
(26/50) Installing py3-parsing (3.2.3-r0)
(27/50) Installing py3-parsing-pyc (3.2.3-r0)
(28/50) Installing py3-packaging (25.0-r0)
(29/50) Installing py3-packaging-pyc (25.0-r0)
(30/50) Installing py3-setuptools (80.3.1-r0)
(31/50) Installing py3-setuptools-pyc (80.3.1-r0)
(32/50) Installing py3-setuptools_scm (8.2.0-r0)
(33/50) Installing py3-setuptools_scm-pyc (8.2.0-r0)
(34/50) Installing py3-wheel (0.46.1-r0)
(35/50) Installing py3-wheel-pyc (0.46.1-r0)
(36/50) Installing python3-dev (3.12.10-r0)
(37/50) Installing py3-oscrypto (1.3.0-r8)
(38/50) Installing py3-oscrypto-pyc (1.3.0-r8)
(39/50) Installing py3-iniconfig (2.1.0-r0)
(40/50) Installing py3-iniconfig-pyc (2.1.0-r0)
(41/50) Installing py3-pluggy (1.5.0-r0)
(42/50) Installing py3-pluggy-pyc (1.5.0-r0)
(43/50) Installing py3-py (1.11.0-r4)
(44/50) Installing py3-py-pyc (1.11.0-r4)
(45/50) Installing py3-pytest (8.3.5-r0)
(46/50) Installing py3-pytest-pyc (8.3.5-r0)
(47/50) Installing sqlite (3.49.2-r0)
(48/50) Installing botan-libs (2.19.5-r0)
(49/50) Installing softhsm (2.6.1-r5)
(50/50) Installing .makedepends-py3-pkcs11 (20250510.112108)
Executing busybox-1.37.0-r17.trigger
OK: 718 MiB in 161 packages
>>> py3-pkcs11: Cleaning up srcdir
>>> py3-pkcs11: Cleaning up pkgdir
>>> py3-pkcs11: Cleaning up tmpdir
>>> py3-pkcs11: Fetching https://distfiles.alpinelinux.org/distfiles/v3.22/python-pkcs11-0.7.0.tar.gz
Connecting to distfiles.alpinelinux.org (172.105.82.32:443)
saving to '/var/cache/distfiles/v3.22/python-pkcs11-0.7.0.tar.gz.part'
python-pkcs11-0.7.0. 100% |********************************| 97.7k  0:00:00 ETA
'/var/cache/distfiles/v3.22/python-pkcs11-0.7.0.tar.gz.part' saved
>>> py3-pkcs11: Fetching https://distfiles.alpinelinux.org/distfiles/v3.22/python-pkcs11-0.7.0.tar.gz
>>> py3-pkcs11: Checking sha512sums...
python-pkcs11-0.7.0.tar.gz: OK
0001-test_x509-add-tzinfo-to-not_before-and-not_after-dat.patch: OK
0002-KeyType.EC_EDWARDS-in-test_sign_eddsa.patch: OK
0003-test_generate_params-use-size-1024.patch: OK
0004-tests-test_x509.py-disable-openssl-verify-test.patch: OK
0005-Fix-typo-in-_pkcs11.pyx.patch: OK
0006-fix-DeprecationWarning-in-test_ecdh.patch: OK
>>> py3-pkcs11: Unpacking /var/cache/distfiles/v3.22/python-pkcs11-0.7.0.tar.gz...
>>> py3-pkcs11: 0001-test_x509-add-tzinfo-to-not_before-and-not_after-dat.patch
patching file requirements.in
patching file requirements.txt
patching file tests/test_x509.py
>>> py3-pkcs11: 0002-KeyType.EC_EDWARDS-in-test_sign_eddsa.patch
patching file tests/test_ecc.py
>>> py3-pkcs11: 0003-test_generate_params-use-size-1024.patch
patching file tests/test_dh.py
>>> py3-pkcs11: 0004-tests-test_x509.py-disable-openssl-verify-test.patch
patching file tests/test_x509.py
>>> py3-pkcs11: 0005-Fix-typo-in-_pkcs11.pyx.patch
patching file pkcs11/_pkcs11.pyx
>>> py3-pkcs11: 0006-fix-DeprecationWarning-in-test_ecdh.patch
patching file docs/opensc.rst
patching file tests/test_public_key_external.py
2025-05-10 11:21:09,880 gpep517 INFO Building wheel via backend setuptools.build_meta:__legacy__
/usr/lib/python3.12/site-packages/setuptools/_distutils/dist.py:289: UserWarning: Unknown distribution option: 'test_suite'
  warnings.warn(msg)
WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml does not contain a tool.setuptools_scm section'
Traceback (most recent call last):
  File "/usr/lib/python3.12/site-packages/setuptools_scm/_integration/pyproject_reading.py", line 36, in read_pyproject
    section = defn.get("tool", {})[tool_name]
              ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
KeyError: 'setuptools_scm'
/usr/lib/python3.12/site-packages/setuptools/dist.py:761: SetuptoolsDeprecationWarning: License classifiers are deprecated.
!!

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

        License :: OSI Approved :: MIT License

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

!!
  self._finalize_license_expression()
2025-05-10 11:21:09,924 root INFO running bdist_wheel
2025-05-10 11:21:10,016 root INFO running build
2025-05-10 11:21:10,016 root INFO running build_py
2025-05-10 11:21:10,022 root INFO creating build/lib.linux-armv8l-cpython-312/pkcs11
2025-05-10 11:21:10,022 root INFO copying pkcs11/__init__.py -> build/lib.linux-armv8l-cpython-312/pkcs11
2025-05-10 11:21:10,023 root INFO copying pkcs11/mechanisms.py -> build/lib.linux-armv8l-cpython-312/pkcs11
2025-05-10 11:21:10,023 root INFO copying pkcs11/exceptions.py -> build/lib.linux-armv8l-cpython-312/pkcs11
2025-05-10 11:21:10,023 root INFO copying pkcs11/defaults.py -> build/lib.linux-armv8l-cpython-312/pkcs11
2025-05-10 11:21:10,024 root INFO copying pkcs11/types.py -> build/lib.linux-armv8l-cpython-312/pkcs11
2025-05-10 11:21:10,024 root INFO copying pkcs11/constants.py -> build/lib.linux-armv8l-cpython-312/pkcs11
2025-05-10 11:21:10,024 root INFO creating build/lib.linux-armv8l-cpython-312/pkcs11/util
2025-05-10 11:21:10,024 root INFO copying pkcs11/util/__init__.py -> build/lib.linux-armv8l-cpython-312/pkcs11/util
2025-05-10 11:21:10,025 root INFO copying pkcs11/util/rsa.py -> build/lib.linux-armv8l-cpython-312/pkcs11/util
2025-05-10 11:21:10,025 root INFO copying pkcs11/util/ec.py -> build/lib.linux-armv8l-cpython-312/pkcs11/util
2025-05-10 11:21:10,025 root INFO copying pkcs11/util/x509.py -> build/lib.linux-armv8l-cpython-312/pkcs11/util
2025-05-10 11:21:10,026 root INFO copying pkcs11/util/dsa.py -> build/lib.linux-armv8l-cpython-312/pkcs11/util
2025-05-10 11:21:10,026 root INFO copying pkcs11/util/dh.py -> build/lib.linux-armv8l-cpython-312/pkcs11/util
2025-05-10 11:21:10,026 root INFO running egg_info
2025-05-10 11:21:10,030 root INFO creating python_pkcs11.egg-info
2025-05-10 11:21:10,030 root INFO writing python_pkcs11.egg-info/PKG-INFO
2025-05-10 11:21:10,030 root INFO writing dependency_links to python_pkcs11.egg-info/dependency_links.txt
2025-05-10 11:21:10,031 root INFO writing requirements to python_pkcs11.egg-info/requires.txt
2025-05-10 11:21:10,031 root INFO writing top-level names to python_pkcs11.egg-info/top_level.txt
2025-05-10 11:21:10,031 root INFO writing manifest file 'python_pkcs11.egg-info/SOURCES.txt'
ERROR setuptools_scm._file_finders.git listing git files failed - pretending there aren't any
2025-05-10 11:21:10,048 root INFO reading manifest file 'python_pkcs11.egg-info/SOURCES.txt'
2025-05-10 11:21:10,049 root INFO writing manifest file 'python_pkcs11.egg-info/SOURCES.txt'
2025-05-10 11:21:10,050 root INFO copying pkcs11/_pkcs11.pyx -> build/lib.linux-armv8l-cpython-312/pkcs11
2025-05-10 11:21:10,050 root INFO running build_ext
warning: pkcs11/_pkcs11.pyx:17:0: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pkcs11/_errors.pyx:85:44: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython.
warning: pkcs11/_pkcs11.pyx:1366:4: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pkcs11/_pkcs11.pyx:1390:8: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
warning: pkcs11/_pkcs11.pyx:1421:8: The 'IF' statement is deprecated and will be removed in a future Cython version. Consider using runtime conditions or C macros instead. See https://github.com/cython/cython/issues/4310
performance hint: pkcs11/_errors.pyx:85:6: Exception check on 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:196:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:211:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:219:70: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:219:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:230:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:268:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:274:28: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:282:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:303:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:316:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:336:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:363:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:366:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:380:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:427:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:488:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:566:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:582:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:590:63: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:590:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:606:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:609:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:616:51: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:615:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:633:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:640:32: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:646:32: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:651:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:656:64: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:656:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:720:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:731:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:747:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:759:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:769:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:855:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:892:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:896:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:903:56: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:902:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:935:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:947:74: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:946:28: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:957:67: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:957:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:983:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:987:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:994:55: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:993:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1026:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:1038:74: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:1037:28: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:1048:67: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:1048:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1074:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1077:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:1084:52: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:1083:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1105:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1115:28: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1120:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:1125:65: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:1125:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1150:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1152:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1172:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1182:28: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1186:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1210:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:1217:59: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:1216:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1276:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1338:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1409:38: Exception check after calling 'C_GetFunctionList' will always require the GIL to be acquired. Declare 'C_GetFunctionList' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
performance hint: pkcs11/_pkcs11.pyx:1409:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1432:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1439:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1470:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
warning: pkcs11/_pkcs11.pyx:1478:64: Use boundscheck(False) for faster access
performance hint: pkcs11/_pkcs11.pyx:1478:20: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1487:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1556:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1557:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
performance hint: pkcs11/_pkcs11.pyx:1562:24: Exception check after calling 'assertRV' will always require the GIL to be acquired.
Possible solutions:
	1. Declare 'assertRV' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
	2. Use an 'int' return type on 'assertRV' to allow an error code to be returned.
Compiling pkcs11/_pkcs11.pyx because it changed.
[1/1] Cythonizing pkcs11/_pkcs11.pyx
2025-05-10 11:21:12,128 root INFO building 'pkcs11._pkcs11' extension
2025-05-10 11:21:12,129 root INFO creating build/temp.linux-armv8l-cpython-312/pkcs11
2025-05-10 11:21:12,129 root INFO cc -Os -fstack-clash-protection -Wformat -Werror=format-security -fPIC -I/usr/include/python3.12 -c pkcs11/_pkcs11.c -o build/temp.linux-armv8l-cpython-312/pkcs11/_pkcs11.o
2025-05-10 11:21:33,926 root INFO cc -shared -Wl,--as-needed,-O1,--sort-common -Os -fstack-clash-protection -Wformat -Werror=format-security build/temp.linux-armv8l-cpython-312/pkcs11/_pkcs11.o -L/usr/lib -o build/lib.linux-armv8l-cpython-312/pkcs11/_pkcs11.cpython-312-arm-linux-musleabihf.so
2025-05-10 11:21:33,952 root INFO installing to build/bdist.linux-armv8l/wheel
2025-05-10 11:21:33,952 root INFO running install
2025-05-10 11:21:33,963 root INFO running install_lib
2025-05-10 11:21:33,972 root INFO creating build/bdist.linux-armv8l/wheel
2025-05-10 11:21:33,972 root INFO creating build/bdist.linux-armv8l/wheel/pkcs11
2025-05-10 11:21:33,972 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/__init__.py -> build/bdist.linux-armv8l/wheel/./pkcs11
2025-05-10 11:21:33,972 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/mechanisms.py -> build/bdist.linux-armv8l/wheel/./pkcs11
2025-05-10 11:21:33,973 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/exceptions.py -> build/bdist.linux-armv8l/wheel/./pkcs11
2025-05-10 11:21:33,973 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/defaults.py -> build/bdist.linux-armv8l/wheel/./pkcs11
2025-05-10 11:21:33,973 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/types.py -> build/bdist.linux-armv8l/wheel/./pkcs11
2025-05-10 11:21:33,973 root INFO creating build/bdist.linux-armv8l/wheel/pkcs11/util
2025-05-10 11:21:33,973 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/util/__init__.py -> build/bdist.linux-armv8l/wheel/./pkcs11/util
2025-05-10 11:21:33,974 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/util/rsa.py -> build/bdist.linux-armv8l/wheel/./pkcs11/util
2025-05-10 11:21:33,974 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/util/ec.py -> build/bdist.linux-armv8l/wheel/./pkcs11/util
2025-05-10 11:21:33,974 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/util/x509.py -> build/bdist.linux-armv8l/wheel/./pkcs11/util
2025-05-10 11:21:33,974 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/util/dsa.py -> build/bdist.linux-armv8l/wheel/./pkcs11/util
2025-05-10 11:21:33,974 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/util/dh.py -> build/bdist.linux-armv8l/wheel/./pkcs11/util
2025-05-10 11:21:33,974 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/_pkcs11.pyx -> build/bdist.linux-armv8l/wheel/./pkcs11
2025-05-10 11:21:33,975 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/_pkcs11.cpython-312-arm-linux-musleabihf.so -> build/bdist.linux-armv8l/wheel/./pkcs11
2025-05-10 11:21:33,975 root INFO copying build/lib.linux-armv8l-cpython-312/pkcs11/constants.py -> build/bdist.linux-armv8l/wheel/./pkcs11
2025-05-10 11:21:33,976 root INFO running install_egg_info
2025-05-10 11:21:33,980 root INFO Copying python_pkcs11.egg-info to build/bdist.linux-armv8l/wheel/./python_pkcs11-0.7.0-py3.12.egg-info
2025-05-10 11:21:33,981 root INFO running install_scripts
2025-05-10 11:21:33,987 root INFO creating build/bdist.linux-armv8l/wheel/python_pkcs11-0.7.0.dist-info/WHEEL
2025-05-10 11:21:33,988 wheel INFO creating '/home/buildozer/aports/community/py3-pkcs11/src/python-pkcs11-0.7.0/.dist/.tmp-2cu04bic/python_pkcs11-0.7.0-cp312-cp312-linux_armv8l.whl' and adding 'build/bdist.linux-armv8l/wheel' to it
2025-05-10 11:21:33,988 wheel INFO adding 'pkcs11/__init__.py'
2025-05-10 11:21:33,990 wheel INFO adding 'pkcs11/_pkcs11.cpython-312-arm-linux-musleabihf.so'
2025-05-10 11:21:33,992 wheel INFO adding 'pkcs11/_pkcs11.pyx'
2025-05-10 11:21:33,992 wheel INFO adding 'pkcs11/constants.py'
2025-05-10 11:21:33,993 wheel INFO adding 'pkcs11/defaults.py'
2025-05-10 11:21:33,993 wheel INFO adding 'pkcs11/exceptions.py'
2025-05-10 11:21:33,993 wheel INFO adding 'pkcs11/mechanisms.py'
2025-05-10 11:21:33,994 wheel INFO adding 'pkcs11/types.py'
2025-05-10 11:21:33,994 wheel INFO adding 'pkcs11/util/__init__.py'
2025-05-10 11:21:33,994 wheel INFO adding 'pkcs11/util/dh.py'
2025-05-10 11:21:33,994 wheel INFO adding 'pkcs11/util/dsa.py'
2025-05-10 11:21:33,995 wheel INFO adding 'pkcs11/util/ec.py'
2025-05-10 11:21:33,995 wheel INFO adding 'pkcs11/util/rsa.py'
2025-05-10 11:21:33,995 wheel INFO adding 'pkcs11/util/x509.py'
2025-05-10 11:21:33,995 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/METADATA'
2025-05-10 11:21:33,996 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/WHEEL'
2025-05-10 11:21:33,996 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/top_level.txt'
2025-05-10 11:21:33,996 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/RECORD'
2025-05-10 11:21:33,996 root INFO removing build/bdist.linux-armv8l/wheel
2025-05-10 11:21:33,997 gpep517 INFO The backend produced .dist/python_pkcs11-0.7.0-cp312-cp312-linux_armv8l.whl
python_pkcs11-0.7.0-cp312-cp312-linux_armv8l.whl
Slot 0 has a free/uninitialized token.
The token has been initialized and is reassigned to slot 1793399234
============================= test session starts ==============================
platform linux -- Python 3.12.10, pytest-8.3.5, pluggy-1.5.0
rootdir: /home/buildozer/aports/community/py3-pkcs11/src/python-pkcs11-0.7.0
collected 70 items

tests/test_aes.py ....ss.                                                [ 10%]
tests/test_des.py ....                                                   [ 15%]
tests/test_dh.py ...                                                     [ 20%]
tests/test_digest.py ....                                                [ 25%]
tests/test_dsa.py ...                                                    [ 30%]
tests/test_ecc.py .s....                                                 [ 38%]
tests/test_iterators.py x.                                               [ 41%]
tests/test_public_key_external.py .s..                                   [ 47%]
tests/test_rsa.py .......                                                [ 57%]
tests/test_sessions.py ..............                                    [ 77%]
tests/test_slots_and_tokens.py ........                                  [ 88%]
tests/test_threading.py .                                                [ 90%]
tests/test_x509.py ..s..s.                                               [100%]

================== 63 passed, 6 skipped, 1 xfailed in 21.75s ===================
>>> py3-pkcs11: Entering fakeroot...
>>> py3-pkcs11-pyc*: Running split function pyc...
'usr/lib/python3.12/site-packages/pkcs11/__pycache__' -> '/home/buildozer/aports/community/py3-pkcs11/pkg/py3-pkcs11-pyc/usr/lib/python3.12/site-packages/pkcs11/__pycache__'
'usr/lib/python3.12/site-packages/pkcs11/util/__pycache__' -> '/home/buildozer/aports/community/py3-pkcs11/pkg/py3-pkcs11-pyc/usr/lib/python3.12/site-packages/pkcs11/util/__pycache__'
>>> py3-pkcs11-pyc*: Preparing subpackage py3-pkcs11-pyc...
>>> py3-pkcs11-pyc*: Running postcheck for py3-pkcs11-pyc
>>> py3-pkcs11*: Running postcheck for py3-pkcs11
>>> py3-pkcs11*: Preparing package py3-pkcs11...
>>> py3-pkcs11*: Stripping binaries
>>> py3-pkcs11-pyc*: Scanning shared objects
>>> py3-pkcs11*: Scanning shared objects
>>> py3-pkcs11-pyc*: Tracing dependencies...
	py3-asn1crypto
	py3-cached-property
	py3-cryptography
	python3
	python3~3.12
>>> py3-pkcs11-pyc*: Package size: 110.6 KB
>>> py3-pkcs11-pyc*: Compressing data...
>>> py3-pkcs11-pyc*: Create checksum...
>>> py3-pkcs11-pyc*: Create py3-pkcs11-pyc-0.7.0-r8.apk
>>> py3-pkcs11*: Tracing dependencies...
	py3-asn1crypto
	py3-cached-property
	py3-cryptography
	python3
	python3~3.12
	so:libc.musl-armhf.so.1
>>> py3-pkcs11*: Package size: 629.2 KB
>>> py3-pkcs11*: Compressing data...
>>> py3-pkcs11*: Create checksum...
>>> py3-pkcs11*: Create py3-pkcs11-0.7.0-r8.apk
>>> py3-pkcs11: Build complete at Sat, 10 May 2025 11:21:57 +0000 elapsed time 0h 1m 14s
>>> py3-pkcs11: Cleaning up srcdir
>>> py3-pkcs11: Cleaning up pkgdir
>>> py3-pkcs11: Uninstalling dependencies...
(1/50) Purging .makedepends-py3-pkcs11 (20250510.112108)
(2/50) Purging py3-cached-property-pyc (1.5.2-r5)
(3/50) Purging py3-cached-property (1.5.2-r5)
(4/50) Purging py3-cryptography-pyc (44.0.3-r0)
(5/50) Purging py3-cryptography (44.0.3-r0)
(6/50) Purging py3-cffi-pyc (1.17.1-r1)
(7/50) Purging py3-cffi (1.17.1-r1)
(8/50) Purging py3-cparser-pyc (2.22-r1)
(9/50) Purging py3-cparser (2.22-r1)
(10/50) Purging cython-pyc (3.0.12-r0)
(11/50) Purging cython (3.0.12-r0)
(12/50) Purging py3-gpep517-pyc (19-r0)
(13/50) Purging py3-gpep517 (19-r0)
(14/50) Purging py3-installer-pyc (0.7.0-r2)
(15/50) Purging py3-installer (0.7.0-r2)
(16/50) Purging py3-setuptools_scm-pyc (8.2.0-r0)
(17/50) Purging py3-setuptools_scm (8.2.0-r0)
(18/50) Purging py3-setuptools-pyc (80.3.1-r0)
(19/50) Purging py3-setuptools (80.3.1-r0)
(20/50) Purging py3-wheel-pyc (0.46.1-r0)
(21/50) Purging py3-wheel (0.46.1-r0)
(22/50) Purging python3-dev (3.12.10-r0)
(23/50) Purging py3-oscrypto-pyc (1.3.0-r8)
(24/50) Purging py3-oscrypto (1.3.0-r8)
(25/50) Purging py3-asn1crypto-pyc (1.5.1_git20231103-r1)
(26/50) Purging py3-asn1crypto (1.5.1_git20231103-r1)
(27/50) Purging py3-pytest-pyc (8.3.5-r0)
(28/50) Purging py3-pytest (8.3.5-r0)
(29/50) Purging py3-iniconfig-pyc (2.1.0-r0)
(30/50) Purging py3-iniconfig (2.1.0-r0)
(31/50) Purging py3-packaging-pyc (25.0-r0)
(32/50) Purging py3-packaging (25.0-r0)
(33/50) Purging py3-parsing-pyc (3.2.3-r0)
(34/50) Purging py3-parsing (3.2.3-r0)
(35/50) Purging py3-pluggy-pyc (1.5.0-r0)
(36/50) Purging py3-pluggy (1.5.0-r0)
(37/50) Purging py3-py-pyc (1.11.0-r4)
(38/50) Purging py3-py (1.11.0-r4)
(39/50) Purging python3-pyc (3.12.10-r0)
(40/50) Purging python3-pycache-pyc0 (3.12.10-r0)
(41/50) Purging pyc (3.12.10-r0)
(42/50) Purging python3 (3.12.10-r0)
(43/50) Purging softhsm (2.6.1-r5)
(44/50) Purging sqlite (3.49.2-r0)
(45/50) Purging botan-libs (2.19.5-r0)
(46/50) Purging gdbm (1.24-r0)
(47/50) Purging libbz2 (1.0.8-r6)
(48/50) Purging libpanelw (6.5_p20250503-r0)
(49/50) Purging mpdecimal (4.0.0-r0)
(50/50) Purging sqlite-libs (3.49.2-r0)
Executing busybox-1.37.0-r17.trigger
OK: 601 MiB in 111 packages
>>> py3-pkcs11: Updating the community/armhf repository index...
>>> py3-pkcs11: Signing the index...