>>> py3-pkcs11: Building community/py3-pkcs11 0.7.0-r8 (using abuild 3.12.0-r5) started Sat, 13 Apr 2024 09:50:34 +0000 >>> py3-pkcs11: Checking sanity of /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/53) Installing libbz2 (1.0.8-r6) (2/53) Installing libffi (3.4.6-r0) (3/53) Installing gdbm (1.23-r1) (4/53) Installing xz-libs (5.6.1-r3) (5/53) Installing mpdecimal (4.0.0-r0) (6/53) Installing libpanelw (6.4_p20240330-r0) (7/53) Installing readline (8.2.10-r0) (8/53) Installing sqlite-libs (3.45.2-r0) (9/53) Installing python3 (3.12.3-r0) (10/53) Installing python3-pycache-pyc0 (3.12.3-r0) (11/53) Installing pyc (3.12.3-r0) (12/53) Installing py3-asn1crypto-pyc (1.5.1_git20231103-r1) (13/53) Installing python3-pyc (3.12.3-r0) (14/53) Installing py3-asn1crypto (1.5.1_git20231103-r1) (15/53) Installing py3-cached-property (1.5.2-r5) (16/53) Installing py3-cached-property-pyc (1.5.2-r5) (17/53) Installing py3-cparser (2.22-r1) (18/53) Installing py3-cparser-pyc (2.22-r1) (19/53) Installing py3-cffi (1.16.0-r1) (20/53) Installing py3-cffi-pyc (1.16.0-r1) (21/53) Installing py3-cryptography (42.0.5-r1) (22/53) Installing py3-cryptography-pyc (42.0.5-r1) (23/53) Installing cython (3.0.8-r0) (24/53) Installing cython-pyc (3.0.8-r0) (25/53) Installing py3-installer (0.7.0-r2) (26/53) Installing py3-installer-pyc (0.7.0-r2) (27/53) Installing py3-gpep517 (15-r2) (28/53) Installing py3-gpep517-pyc (15-r2) (29/53) Installing py3-parsing (3.1.2-r1) (30/53) Installing py3-parsing-pyc (3.1.2-r1) (31/53) Installing py3-packaging (24.0-r1) (32/53) Installing py3-packaging-pyc (24.0-r1) (33/53) Installing py3-setuptools (69.2.0-r2) (34/53) Installing py3-setuptools-pyc (69.2.0-r2) (35/53) Installing py3-setuptools_scm (8.0.4-r2) (36/53) Installing py3-setuptools_scm-pyc (8.0.4-r2) (37/53) Installing py3-wheel (0.42.0-r1) (38/53) Installing py3-wheel-pyc (0.42.0-r1) (39/53) Installing python3-dev (3.12.3-r0) (40/53) Installing py3-oscrypto (1.3.0-r6) (41/53) Installing py3-oscrypto-pyc (1.3.0-r6) (42/53) Installing py3-iniconfig (2.0.0-r1) (43/53) Installing py3-iniconfig-pyc (2.0.0-r1) (44/53) Installing py3-pluggy (1.4.0-r1) (45/53) Installing py3-pluggy-pyc (1.4.0-r1) (46/53) Installing py3-py (1.11.0-r3) (47/53) Installing py3-py-pyc (1.11.0-r3) (48/53) Installing py3-pytest (8.1.1-r1) (49/53) Installing py3-pytest-pyc (8.1.1-r1) (50/53) Installing sqlite (3.45.2-r0) (51/53) Installing botan-libs (2.19.3-r5) (52/53) Installing softhsm (2.6.1-r4) (53/53) Installing .makedepends-py3-pkcs11 (20240413.095036) Executing busybox-1.36.1-r25.trigger OK: 586 MiB in 158 packages >>> py3-pkcs11: Cleaning up srcdir >>> py3-pkcs11: Cleaning up pkgdir >>> py3-pkcs11: Cleaning up tmpdir >>> py3-pkcs11: Fetching https://distfiles.alpinelinux.org/distfiles/edge/python-pkcs11-0.7.0.tar.gz >>> py3-pkcs11: Fetching https://distfiles.alpinelinux.org/distfiles/edge/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/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 2024-04-13 09:50:37,312 gpep517 INFO Building wheel via backend setuptools.build_meta:__legacy__ WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml does not contain a tool.setuptools_scm section' 2024-04-13 09:50:37,346 root INFO running bdist_wheel 2024-04-13 09:50:37,409 root INFO running build 2024-04-13 09:50:37,409 root INFO running build_py 2024-04-13 09:50:37,411 root INFO creating build 2024-04-13 09:50:37,411 root INFO creating build/lib.linux-aarch64-cpython-312 2024-04-13 09:50:37,411 root INFO creating build/lib.linux-aarch64-cpython-312/pkcs11 2024-04-13 09:50:37,412 root INFO copying pkcs11/__init__.py -> build/lib.linux-aarch64-cpython-312/pkcs11 2024-04-13 09:50:37,412 root INFO copying pkcs11/mechanisms.py -> build/lib.linux-aarch64-cpython-312/pkcs11 2024-04-13 09:50:37,412 root INFO copying pkcs11/exceptions.py -> build/lib.linux-aarch64-cpython-312/pkcs11 2024-04-13 09:50:37,412 root INFO copying pkcs11/defaults.py -> build/lib.linux-aarch64-cpython-312/pkcs11 2024-04-13 09:50:37,412 root INFO copying pkcs11/types.py -> build/lib.linux-aarch64-cpython-312/pkcs11 2024-04-13 09:50:37,413 root INFO copying pkcs11/constants.py -> build/lib.linux-aarch64-cpython-312/pkcs11 2024-04-13 09:50:37,413 root INFO creating build/lib.linux-aarch64-cpython-312/pkcs11/util 2024-04-13 09:50:37,413 root INFO copying pkcs11/util/__init__.py -> build/lib.linux-aarch64-cpython-312/pkcs11/util 2024-04-13 09:50:37,413 root INFO copying pkcs11/util/rsa.py -> build/lib.linux-aarch64-cpython-312/pkcs11/util 2024-04-13 09:50:37,413 root INFO copying pkcs11/util/ec.py -> build/lib.linux-aarch64-cpython-312/pkcs11/util 2024-04-13 09:50:37,413 root INFO copying pkcs11/util/x509.py -> build/lib.linux-aarch64-cpython-312/pkcs11/util 2024-04-13 09:50:37,414 root INFO copying pkcs11/util/dsa.py -> build/lib.linux-aarch64-cpython-312/pkcs11/util 2024-04-13 09:50:37,414 root INFO copying pkcs11/util/dh.py -> build/lib.linux-aarch64-cpython-312/pkcs11/util 2024-04-13 09:50:37,414 root INFO running egg_info 2024-04-13 09:50:37,414 root INFO creating python_pkcs11.egg-info 2024-04-13 09:50:37,416 root INFO writing python_pkcs11.egg-info/PKG-INFO 2024-04-13 09:50:37,416 root INFO writing dependency_links to python_pkcs11.egg-info/dependency_links.txt 2024-04-13 09:50:37,416 root INFO writing requirements to python_pkcs11.egg-info/requires.txt 2024-04-13 09:50:37,417 root INFO writing top-level names to python_pkcs11.egg-info/top_level.txt 2024-04-13 09:50:37,417 root INFO writing manifest file 'python_pkcs11.egg-info/SOURCES.txt' 2024-04-13 09:50:38,696 root INFO reading manifest file 'python_pkcs11.egg-info/SOURCES.txt' 2024-04-13 09:50:38,697 root INFO writing manifest file 'python_pkcs11.egg-info/SOURCES.txt' 2024-04-13 09:50:38,697 root INFO copying pkcs11/_pkcs11.pyx -> build/lib.linux-aarch64-cpython-312/pkcs11 2024-04-13 09:50:38,698 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 2024-04-13 09:50:40,183 root INFO building 'pkcs11._pkcs11' extension 2024-04-13 09:50:40,184 root INFO creating build/temp.linux-aarch64-cpython-312 2024-04-13 09:50:40,184 root INFO creating build/temp.linux-aarch64-cpython-312/pkcs11 2024-04-13 09:50:40,184 root INFO gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -Os -fstack-clash-protection -Wformat -Werror=format-security -fPIC -I/usr/include/python3.12 -c pkcs11/_pkcs11.c -o build/temp.linux-aarch64-cpython-312/pkcs11/_pkcs11.o 2024-04-13 09:51:10,898 root INFO gcc -shared -Wl,--as-needed,-O1,--sort-common -Os -fstack-clash-protection -Wformat -Werror=format-security build/temp.linux-aarch64-cpython-312/pkcs11/_pkcs11.o -L/usr/lib -o build/lib.linux-aarch64-cpython-312/pkcs11/_pkcs11.cpython-312-aarch64-linux-musl.so 2024-04-13 09:51:10,934 wheel INFO installing to build/bdist.linux-aarch64/wheel 2024-04-13 09:51:10,934 root INFO running install 2024-04-13 09:51:10,942 root INFO running install_lib 2024-04-13 09:51:10,944 root INFO creating build/bdist.linux-aarch64 2024-04-13 09:51:10,944 root INFO creating build/bdist.linux-aarch64/wheel 2024-04-13 09:51:10,944 root INFO creating build/bdist.linux-aarch64/wheel/pkcs11 2024-04-13 09:51:10,944 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/__init__.py -> build/bdist.linux-aarch64/wheel/pkcs11 2024-04-13 09:51:10,944 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/mechanisms.py -> build/bdist.linux-aarch64/wheel/pkcs11 2024-04-13 09:51:10,944 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/exceptions.py -> build/bdist.linux-aarch64/wheel/pkcs11 2024-04-13 09:51:10,945 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/defaults.py -> build/bdist.linux-aarch64/wheel/pkcs11 2024-04-13 09:51:10,945 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/types.py -> build/bdist.linux-aarch64/wheel/pkcs11 2024-04-13 09:51:10,945 root INFO creating build/bdist.linux-aarch64/wheel/pkcs11/util 2024-04-13 09:51:10,945 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/util/__init__.py -> build/bdist.linux-aarch64/wheel/pkcs11/util 2024-04-13 09:51:10,945 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/util/rsa.py -> build/bdist.linux-aarch64/wheel/pkcs11/util 2024-04-13 09:51:10,945 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/util/ec.py -> build/bdist.linux-aarch64/wheel/pkcs11/util 2024-04-13 09:51:10,945 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/util/x509.py -> build/bdist.linux-aarch64/wheel/pkcs11/util 2024-04-13 09:51:10,946 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/util/dsa.py -> build/bdist.linux-aarch64/wheel/pkcs11/util 2024-04-13 09:51:10,946 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/util/dh.py -> build/bdist.linux-aarch64/wheel/pkcs11/util 2024-04-13 09:51:10,946 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/_pkcs11.pyx -> build/bdist.linux-aarch64/wheel/pkcs11 2024-04-13 09:51:10,946 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/constants.py -> build/bdist.linux-aarch64/wheel/pkcs11 2024-04-13 09:51:10,946 root INFO copying build/lib.linux-aarch64-cpython-312/pkcs11/_pkcs11.cpython-312-aarch64-linux-musl.so -> build/bdist.linux-aarch64/wheel/pkcs11 2024-04-13 09:51:10,948 root INFO running install_egg_info 2024-04-13 09:51:10,951 root INFO Copying python_pkcs11.egg-info to build/bdist.linux-aarch64/wheel/python_pkcs11-0.7.0-py3.12.egg-info 2024-04-13 09:51:10,952 root INFO running install_scripts 2024-04-13 09:51:10,955 wheel INFO creating build/bdist.linux-aarch64/wheel/python_pkcs11-0.7.0.dist-info/WHEEL 2024-04-13 09:51:10,956 wheel INFO creating '/home/buildozer/aports/community/py3-pkcs11/src/python-pkcs11-0.7.0/.dist/.tmp-a29lndmh/python_pkcs11-0.7.0-cp312-cp312-linux_aarch64.whl' and adding 'build/bdist.linux-aarch64/wheel' to it 2024-04-13 09:51:10,956 wheel INFO adding 'pkcs11/__init__.py' 2024-04-13 09:51:10,960 wheel INFO adding 'pkcs11/_pkcs11.cpython-312-aarch64-linux-musl.so' 2024-04-13 09:51:10,961 wheel INFO adding 'pkcs11/_pkcs11.pyx' 2024-04-13 09:51:10,962 wheel INFO adding 'pkcs11/constants.py' 2024-04-13 09:51:10,962 wheel INFO adding 'pkcs11/defaults.py' 2024-04-13 09:51:10,962 wheel INFO adding 'pkcs11/exceptions.py' 2024-04-13 09:51:10,962 wheel INFO adding 'pkcs11/mechanisms.py' 2024-04-13 09:51:10,962 wheel INFO adding 'pkcs11/types.py' 2024-04-13 09:51:10,962 wheel INFO adding 'pkcs11/util/__init__.py' 2024-04-13 09:51:10,963 wheel INFO adding 'pkcs11/util/dh.py' 2024-04-13 09:51:10,963 wheel INFO adding 'pkcs11/util/dsa.py' 2024-04-13 09:51:10,963 wheel INFO adding 'pkcs11/util/ec.py' 2024-04-13 09:51:10,963 wheel INFO adding 'pkcs11/util/rsa.py' 2024-04-13 09:51:10,963 wheel INFO adding 'pkcs11/util/x509.py' 2024-04-13 09:51:10,963 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/METADATA' 2024-04-13 09:51:10,964 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/WHEEL' 2024-04-13 09:51:10,964 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/top_level.txt' 2024-04-13 09:51:10,964 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/RECORD' 2024-04-13 09:51:10,964 wheel INFO removing build/bdist.linux-aarch64/wheel 2024-04-13 09:51:10,965 gpep517 INFO The backend produced .dist/python_pkcs11-0.7.0-cp312-cp312-linux_aarch64.whl python_pkcs11-0.7.0-cp312-cp312-linux_aarch64.whl Slot 0 has a free/uninitialized token. The token has been initialized and is reassigned to slot 321526346 ============================= test session starts ============================== platform linux -- Python 3.12.3, pytest-8.1.1, pluggy-1.4.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 10.40s =================== >>> py3-pkcs11: Entering fakeroot... >>> py3-pkcs11-pyc*: Running split function pyc... '/home/buildozer/aports/community/py3-pkcs11/pkg/py3-pkcs11/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__' '/home/buildozer/aports/community/py3-pkcs11/pkg/py3-pkcs11/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: 176.0 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-aarch64.so.1 >>> py3-pkcs11*: Package size: 708.0 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, 13 Apr 2024 09:51:22 +0000 elapsed time 0h 0m 48s >>> py3-pkcs11: Cleaning up srcdir >>> py3-pkcs11: Cleaning up pkgdir >>> py3-pkcs11: Uninstalling dependencies... (1/53) Purging .makedepends-py3-pkcs11 (20240413.095036) (2/53) Purging py3-cached-property-pyc (1.5.2-r5) (3/53) Purging py3-cached-property (1.5.2-r5) (4/53) Purging py3-cryptography-pyc (42.0.5-r1) (5/53) Purging py3-cryptography (42.0.5-r1) (6/53) Purging py3-cffi-pyc (1.16.0-r1) (7/53) Purging py3-cffi (1.16.0-r1) (8/53) Purging py3-cparser-pyc (2.22-r1) (9/53) Purging py3-cparser (2.22-r1) (10/53) Purging cython-pyc (3.0.8-r0) (11/53) Purging cython (3.0.8-r0) (12/53) Purging py3-gpep517-pyc (15-r2) (13/53) Purging py3-gpep517 (15-r2) (14/53) Purging py3-installer-pyc (0.7.0-r2) (15/53) Purging py3-installer (0.7.0-r2) (16/53) Purging py3-setuptools_scm-pyc (8.0.4-r2) (17/53) Purging py3-setuptools_scm (8.0.4-r2) (18/53) Purging py3-setuptools-pyc (69.2.0-r2) (19/53) Purging py3-setuptools (69.2.0-r2) (20/53) Purging py3-wheel-pyc (0.42.0-r1) (21/53) Purging py3-wheel (0.42.0-r1) (22/53) Purging python3-dev (3.12.3-r0) (23/53) Purging py3-oscrypto-pyc (1.3.0-r6) (24/53) Purging py3-oscrypto (1.3.0-r6) (25/53) Purging py3-asn1crypto-pyc (1.5.1_git20231103-r1) (26/53) Purging py3-asn1crypto (1.5.1_git20231103-r1) (27/53) Purging py3-pytest-pyc (8.1.1-r1) (28/53) Purging py3-pytest (8.1.1-r1) (29/53) Purging py3-iniconfig-pyc (2.0.0-r1) (30/53) Purging py3-iniconfig (2.0.0-r1) (31/53) Purging py3-packaging-pyc (24.0-r1) (32/53) Purging py3-packaging (24.0-r1) (33/53) Purging py3-parsing-pyc (3.1.2-r1) (34/53) Purging py3-parsing (3.1.2-r1) (35/53) Purging py3-pluggy-pyc (1.4.0-r1) (36/53) Purging py3-pluggy (1.4.0-r1) (37/53) Purging py3-py-pyc (1.11.0-r3) (38/53) Purging py3-py (1.11.0-r3) (39/53) Purging softhsm (2.6.1-r4) (40/53) Purging sqlite (3.45.2-r0) (41/53) Purging botan-libs (2.19.3-r5) (42/53) Purging python3-pyc (3.12.3-r0) (43/53) Purging python3-pycache-pyc0 (3.12.3-r0) (44/53) Purging pyc (3.12.3-r0) (45/53) Purging python3 (3.12.3-r0) (46/53) Purging gdbm (1.23-r1) (47/53) Purging libbz2 (1.0.8-r6) (48/53) Purging libffi (3.4.6-r0) (49/53) Purging libpanelw (6.4_p20240330-r0) (50/53) Purging mpdecimal (4.0.0-r0) (51/53) Purging readline (8.2.10-r0) (52/53) Purging sqlite-libs (3.45.2-r0) (53/53) Purging xz-libs (5.6.1-r3) Executing busybox-1.36.1-r25.trigger OK: 380 MiB in 105 packages >>> py3-pkcs11: Updating the community/aarch64 repository index... >>> py3-pkcs11: Signing the index...