>>> py3-pkcs11: Building community/py3-pkcs11 0.7.0-r8 (using abuild 3.14.1-r1) started Tue, 05 Nov 2024 22:09:17 +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/52) Installing libbz2 (1.0.8-r6)
(2/52) Installing libffi (3.4.6-r0)
(3/52) Installing gdbm (1.24-r0)
(4/52) Installing xz-libs (5.6.3-r0)
(5/52) Installing mpdecimal (4.0.0-r0)
(6/52) Installing libpanelw (6.5_p20241006-r2)
(7/52) Installing sqlite-libs (3.47.0-r0)
(8/52) Installing python3 (3.12.7-r1)
(9/52) Installing python3-pycache-pyc0 (3.12.7-r1)
(10/52) Installing pyc (3.12.7-r1)
(11/52) Installing py3-asn1crypto-pyc (1.5.1_git20231103-r1)
(12/52) Installing python3-pyc (3.12.7-r1)
(13/52) Installing py3-asn1crypto (1.5.1_git20231103-r1)
(14/52) Installing py3-cached-property (1.5.2-r5)
(15/52) Installing py3-cached-property-pyc (1.5.2-r5)
(16/52) Installing py3-cparser (2.22-r1)
(17/52) Installing py3-cparser-pyc (2.22-r1)
(18/52) Installing py3-cffi (1.17.1-r1)
(19/52) Installing py3-cffi-pyc (1.17.1-r1)
(20/52) Installing py3-cryptography (43.0.3-r0)
(21/52) Installing py3-cryptography-pyc (43.0.3-r0)
(22/52) Installing cython (3.0.10-r0)
(23/52) Installing cython-pyc (3.0.10-r0)
(24/52) Installing py3-installer (0.7.0-r2)
(25/52) Installing py3-installer-pyc (0.7.0-r2)
(26/52) Installing py3-gpep517 (16-r0)
(27/52) Installing py3-gpep517-pyc (16-r0)
(28/52) Installing py3-parsing (3.1.4-r0)
(29/52) Installing py3-parsing-pyc (3.1.4-r0)
(30/52) Installing py3-packaging (24.1-r0)
(31/52) Installing py3-packaging-pyc (24.1-r0)
(32/52) Installing py3-setuptools (70.3.0-r0)
(33/52) Installing py3-setuptools-pyc (70.3.0-r0)
(34/52) Installing py3-setuptools_scm (8.1.0-r0)
(35/52) Installing py3-setuptools_scm-pyc (8.1.0-r0)
(36/52) Installing py3-wheel (0.43.0-r0)
(37/52) Installing py3-wheel-pyc (0.43.0-r0)
(38/52) Installing python3-dev (3.12.7-r1)
(39/52) Installing py3-oscrypto (1.3.0-r7)
(40/52) Installing py3-oscrypto-pyc (1.3.0-r7)
(41/52) Installing py3-iniconfig (2.0.0-r1)
(42/52) Installing py3-iniconfig-pyc (2.0.0-r1)
(43/52) Installing py3-pluggy (1.5.0-r0)
(44/52) Installing py3-pluggy-pyc (1.5.0-r0)
(45/52) Installing py3-py (1.11.0-r4)
(46/52) Installing py3-py-pyc (1.11.0-r4)
(47/52) Installing py3-pytest (8.3.3-r0)
(48/52) Installing py3-pytest-pyc (8.3.3-r0)
(49/52) Installing sqlite (3.47.0-r0)
(50/52) Installing botan-libs (2.19.5-r0)
(51/52) Installing softhsm (2.6.1-r4)
(52/52) Installing .makedepends-py3-pkcs11 (20241105.220929)
Executing busybox-1.37.0-r6.trigger
OK: 567 MiB in 153 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.21/python-pkcs11-0.7.0.tar.gz
Connecting to distfiles.alpinelinux.org (172.105.82.32:443)
saving to '/var/cache/distfiles/v3.21/python-pkcs11-0.7.0.tar.gz.part'
python-pkcs11-0.7.0. 100% |********************************| 97.7k  0:00:00 ETA
'/var/cache/distfiles/v3.21/python-pkcs11-0.7.0.tar.gz.part' saved
>>> py3-pkcs11: Fetching https://distfiles.alpinelinux.org/distfiles/v3.21/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.21/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-11-05 22:09:30,636 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'
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'
2024-11-05 22:09:30,659 root INFO running bdist_wheel
2024-11-05 22:09:30,726 root INFO running build
2024-11-05 22:09:30,726 root INFO running build_py
2024-11-05 22:09:30,729 root INFO creating build
2024-11-05 22:09:30,729 root INFO creating build/lib.linux-x86_64-cpython-312
2024-11-05 22:09:30,729 root INFO creating build/lib.linux-x86_64-cpython-312/pkcs11
2024-11-05 22:09:30,730 root INFO copying pkcs11/mechanisms.py -> build/lib.linux-x86_64-cpython-312/pkcs11
2024-11-05 22:09:30,730 root INFO copying pkcs11/defaults.py -> build/lib.linux-x86_64-cpython-312/pkcs11
2024-11-05 22:09:30,730 root INFO copying pkcs11/exceptions.py -> build/lib.linux-x86_64-cpython-312/pkcs11
2024-11-05 22:09:30,730 root INFO copying pkcs11/types.py -> build/lib.linux-x86_64-cpython-312/pkcs11
2024-11-05 22:09:30,731 root INFO copying pkcs11/constants.py -> build/lib.linux-x86_64-cpython-312/pkcs11
2024-11-05 22:09:30,731 root INFO copying pkcs11/__init__.py -> build/lib.linux-x86_64-cpython-312/pkcs11
2024-11-05 22:09:30,731 root INFO creating build/lib.linux-x86_64-cpython-312/pkcs11/util
2024-11-05 22:09:30,731 root INFO copying pkcs11/util/dh.py -> build/lib.linux-x86_64-cpython-312/pkcs11/util
2024-11-05 22:09:30,731 root INFO copying pkcs11/util/x509.py -> build/lib.linux-x86_64-cpython-312/pkcs11/util
2024-11-05 22:09:30,732 root INFO copying pkcs11/util/dsa.py -> build/lib.linux-x86_64-cpython-312/pkcs11/util
2024-11-05 22:09:30,732 root INFO copying pkcs11/util/__init__.py -> build/lib.linux-x86_64-cpython-312/pkcs11/util
2024-11-05 22:09:30,732 root INFO copying pkcs11/util/rsa.py -> build/lib.linux-x86_64-cpython-312/pkcs11/util
2024-11-05 22:09:30,732 root INFO copying pkcs11/util/ec.py -> build/lib.linux-x86_64-cpython-312/pkcs11/util
2024-11-05 22:09:30,732 root INFO running egg_info
2024-11-05 22:09:30,732 root INFO creating python_pkcs11.egg-info
2024-11-05 22:09:30,734 root INFO writing python_pkcs11.egg-info/PKG-INFO
2024-11-05 22:09:30,735 root INFO writing dependency_links to python_pkcs11.egg-info/dependency_links.txt
2024-11-05 22:09:30,735 root INFO writing requirements to python_pkcs11.egg-info/requires.txt
2024-11-05 22:09:30,735 root INFO writing top-level names to python_pkcs11.egg-info/top_level.txt
2024-11-05 22:09:30,736 root INFO writing manifest file 'python_pkcs11.egg-info/SOURCES.txt'
2024-11-05 22:09:32,262 root INFO reading manifest file 'python_pkcs11.egg-info/SOURCES.txt'
2024-11-05 22:09:32,263 root INFO writing manifest file 'python_pkcs11.egg-info/SOURCES.txt'
2024-11-05 22:09:32,263 root INFO copying pkcs11/_pkcs11.pyx -> build/lib.linux-x86_64-cpython-312/pkcs11
2024-11-05 22:09:32,264 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-11-05 22:09:33,735 root INFO building 'pkcs11._pkcs11' extension
2024-11-05 22:09:33,735 root INFO creating build/temp.linux-x86_64-cpython-312
2024-11-05 22:09:33,735 root INFO creating build/temp.linux-x86_64-cpython-312/pkcs11
2024-11-05 22:09:33,735 root INFO gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O3 -Wall -Os -fstack-clash-protection -Wformat -Werror=format-security -fno-plt -fPIC -I/usr/include/python3.12 -c pkcs11/_pkcs11.c -o build/temp.linux-x86_64-cpython-312/pkcs11/_pkcs11.o
2024-11-05 22:09:58,916 root INFO gcc -shared -Wl,--as-needed,-O1,--sort-common -Wl,-z,pack-relative-relocs -Os -fstack-clash-protection -Wformat -Werror=format-security -fno-plt build/temp.linux-x86_64-cpython-312/pkcs11/_pkcs11.o -L/usr/lib -o build/lib.linux-x86_64-cpython-312/pkcs11/_pkcs11.cpython-312-x86_64-linux-musl.so
2024-11-05 22:09:58,965 root INFO installing to build/bdist.linux-x86_64/wheel
2024-11-05 22:09:58,965 root INFO running install
2024-11-05 22:09:58,974 root INFO running install_lib
2024-11-05 22:09:58,976 root INFO creating build/bdist.linux-x86_64
2024-11-05 22:09:58,976 root INFO creating build/bdist.linux-x86_64/wheel
2024-11-05 22:09:58,977 root INFO creating build/bdist.linux-x86_64/wheel/pkcs11
2024-11-05 22:09:58,977 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/mechanisms.py -> build/bdist.linux-x86_64/wheel/pkcs11
2024-11-05 22:09:58,977 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/_pkcs11.pyx -> build/bdist.linux-x86_64/wheel/pkcs11
2024-11-05 22:09:58,977 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/defaults.py -> build/bdist.linux-x86_64/wheel/pkcs11
2024-11-05 22:09:58,977 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/exceptions.py -> build/bdist.linux-x86_64/wheel/pkcs11
2024-11-05 22:09:58,977 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/types.py -> build/bdist.linux-x86_64/wheel/pkcs11
2024-11-05 22:09:58,978 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/constants.py -> build/bdist.linux-x86_64/wheel/pkcs11
2024-11-05 22:09:58,978 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/__init__.py -> build/bdist.linux-x86_64/wheel/pkcs11
2024-11-05 22:09:58,978 root INFO creating build/bdist.linux-x86_64/wheel/pkcs11/util
2024-11-05 22:09:58,978 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/util/dh.py -> build/bdist.linux-x86_64/wheel/pkcs11/util
2024-11-05 22:09:58,978 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/util/x509.py -> build/bdist.linux-x86_64/wheel/pkcs11/util
2024-11-05 22:09:58,978 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/util/dsa.py -> build/bdist.linux-x86_64/wheel/pkcs11/util
2024-11-05 22:09:58,979 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/util/__init__.py -> build/bdist.linux-x86_64/wheel/pkcs11/util
2024-11-05 22:09:58,979 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/util/rsa.py -> build/bdist.linux-x86_64/wheel/pkcs11/util
2024-11-05 22:09:58,979 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/util/ec.py -> build/bdist.linux-x86_64/wheel/pkcs11/util
2024-11-05 22:09:58,979 root INFO copying build/lib.linux-x86_64-cpython-312/pkcs11/_pkcs11.cpython-312-x86_64-linux-musl.so -> build/bdist.linux-x86_64/wheel/pkcs11
2024-11-05 22:09:58,981 root INFO running install_egg_info
2024-11-05 22:09:58,984 root INFO Copying python_pkcs11.egg-info to build/bdist.linux-x86_64/wheel/python_pkcs11-0.7.0-py3.12.egg-info
2024-11-05 22:09:58,984 root INFO running install_scripts
2024-11-05 22:09:58,991 root INFO creating build/bdist.linux-x86_64/wheel/python_pkcs11-0.7.0.dist-info/WHEEL
2024-11-05 22:09:58,991 wheel INFO creating '/home/buildozer/aports/community/py3-pkcs11/src/python-pkcs11-0.7.0/.dist/.tmp-yw2_b4ct/python_pkcs11-0.7.0-cp312-cp312-linux_x86_64.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
2024-11-05 22:09:58,991 wheel INFO adding 'pkcs11/__init__.py'
2024-11-05 22:09:58,996 wheel INFO adding 'pkcs11/_pkcs11.cpython-312-x86_64-linux-musl.so'
2024-11-05 22:09:59,001 wheel INFO adding 'pkcs11/_pkcs11.pyx'
2024-11-05 22:09:59,002 wheel INFO adding 'pkcs11/constants.py'
2024-11-05 22:09:59,002 wheel INFO adding 'pkcs11/defaults.py'
2024-11-05 22:09:59,002 wheel INFO adding 'pkcs11/exceptions.py'
2024-11-05 22:09:59,002 wheel INFO adding 'pkcs11/mechanisms.py'
2024-11-05 22:09:59,003 wheel INFO adding 'pkcs11/types.py'
2024-11-05 22:09:59,003 wheel INFO adding 'pkcs11/util/__init__.py'
2024-11-05 22:09:59,003 wheel INFO adding 'pkcs11/util/dh.py'
2024-11-05 22:09:59,003 wheel INFO adding 'pkcs11/util/dsa.py'
2024-11-05 22:09:59,003 wheel INFO adding 'pkcs11/util/ec.py'
2024-11-05 22:09:59,004 wheel INFO adding 'pkcs11/util/rsa.py'
2024-11-05 22:09:59,004 wheel INFO adding 'pkcs11/util/x509.py'
2024-11-05 22:09:59,004 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/METADATA'
2024-11-05 22:09:59,004 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/WHEEL'
2024-11-05 22:09:59,004 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/top_level.txt'
2024-11-05 22:09:59,004 wheel INFO adding 'python_pkcs11-0.7.0.dist-info/RECORD'
2024-11-05 22:09:59,005 root INFO removing build/bdist.linux-x86_64/wheel
2024-11-05 22:09:59,006 gpep517 INFO The backend produced .dist/python_pkcs11-0.7.0-cp312-cp312-linux_x86_64.whl
python_pkcs11-0.7.0-cp312-cp312-linux_x86_64.whl
Slot 0 has a free/uninitialized token.
The token has been initialized and is reassigned to slot 1981543974
============================= test session starts ==============================
platform linux -- Python 3.12.7, pytest-8.3.3, 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 7.49s ===================
>>> 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-x86_64.so.1
>>> py3-pkcs11*: Package size: 611.3 KB
>>> py3-pkcs11*: Compressing data...
>>> py3-pkcs11*: Create checksum...
>>> py3-pkcs11*: Create py3-pkcs11-0.7.0-r8.apk
>>> py3-pkcs11: Build complete at Tue, 05 Nov 2024 22:10:07 +0000 elapsed time 0h 0m 50s
>>> py3-pkcs11: Cleaning up srcdir
>>> py3-pkcs11: Cleaning up pkgdir
>>> py3-pkcs11: Uninstalling dependencies...
(1/52) Purging .makedepends-py3-pkcs11 (20241105.220929)
(2/52) Purging py3-cached-property-pyc (1.5.2-r5)
(3/52) Purging py3-cached-property (1.5.2-r5)
(4/52) Purging py3-cryptography-pyc (43.0.3-r0)
(5/52) Purging py3-cryptography (43.0.3-r0)
(6/52) Purging py3-cffi-pyc (1.17.1-r1)
(7/52) Purging py3-cffi (1.17.1-r1)
(8/52) Purging py3-cparser-pyc (2.22-r1)
(9/52) Purging py3-cparser (2.22-r1)
(10/52) Purging cython-pyc (3.0.10-r0)
(11/52) Purging cython (3.0.10-r0)
(12/52) Purging py3-gpep517-pyc (16-r0)
(13/52) Purging py3-gpep517 (16-r0)
(14/52) Purging py3-installer-pyc (0.7.0-r2)
(15/52) Purging py3-installer (0.7.0-r2)
(16/52) Purging py3-setuptools_scm-pyc (8.1.0-r0)
(17/52) Purging py3-setuptools_scm (8.1.0-r0)
(18/52) Purging py3-setuptools-pyc (70.3.0-r0)
(19/52) Purging py3-setuptools (70.3.0-r0)
(20/52) Purging py3-wheel-pyc (0.43.0-r0)
(21/52) Purging py3-wheel (0.43.0-r0)
(22/52) Purging python3-dev (3.12.7-r1)
(23/52) Purging py3-oscrypto-pyc (1.3.0-r7)
(24/52) Purging py3-oscrypto (1.3.0-r7)
(25/52) Purging py3-asn1crypto-pyc (1.5.1_git20231103-r1)
(26/52) Purging py3-asn1crypto (1.5.1_git20231103-r1)
(27/52) Purging py3-pytest-pyc (8.3.3-r0)
(28/52) Purging py3-pytest (8.3.3-r0)
(29/52) Purging py3-iniconfig-pyc (2.0.0-r1)
(30/52) Purging py3-iniconfig (2.0.0-r1)
(31/52) Purging py3-packaging-pyc (24.1-r0)
(32/52) Purging py3-packaging (24.1-r0)
(33/52) Purging py3-parsing-pyc (3.1.4-r0)
(34/52) Purging py3-parsing (3.1.4-r0)
(35/52) Purging py3-pluggy-pyc (1.5.0-r0)
(36/52) Purging py3-pluggy (1.5.0-r0)
(37/52) Purging py3-py-pyc (1.11.0-r4)
(38/52) Purging py3-py (1.11.0-r4)
(39/52) Purging python3-pyc (3.12.7-r1)
(40/52) Purging python3-pycache-pyc0 (3.12.7-r1)
(41/52) Purging pyc (3.12.7-r1)
(42/52) Purging python3 (3.12.7-r1)
(43/52) Purging softhsm (2.6.1-r4)
(44/52) Purging sqlite (3.47.0-r0)
(45/52) Purging botan-libs (2.19.5-r0)
(46/52) Purging gdbm (1.24-r0)
(47/52) Purging libbz2 (1.0.8-r6)
(48/52) Purging libffi (3.4.6-r0)
(49/52) Purging libpanelw (6.5_p20241006-r2)
(50/52) Purging mpdecimal (4.0.0-r0)
(51/52) Purging sqlite-libs (3.47.0-r0)
(52/52) Purging xz-libs (5.6.3-r0)
Executing busybox-1.37.0-r6.trigger
OK: 395 MiB in 101 packages
>>> py3-pkcs11: Updating the community/x86_64 repository index...
>>> py3-pkcs11: Signing the index...