D: [iurt_root_command] chroot Building target platforms: x86_64 Building for target x86_64 Installing /home/pterjan/rpmbuild/SRPMS/python-pkcs11-0.7.0-2.mga10.src.rpm Executing(%mkbuilddir): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.SD4hEy Executing(%prep): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.fDbShI + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + cd /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + rm -rf python-pkcs11-0.7.0 + /usr/lib/rpm/rpmuncompress -x /home/pterjan/rpmbuild/SOURCES/python-pkcs11-0.7.0.tar.gz + STATUS=0 + '[' 0 -ne 0 ']' + cd python-pkcs11-0.7.0 + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w . + RPM_EC=0 ++ jobs -p + exit 0 Executing(%generate_buildrequires): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.k6cxHz + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + cd python-pkcs11-0.7.0 + echo pyproject-rpm-macros + echo python3-devel + echo 'python3dist(packaging)' + echo 'python3dist(pip) >= 19' + '[' -f pyproject.toml ']' + '[' -f setup.py ']' + echo 'python3dist(setuptools) >= 40.8' + for f in pyproject.toml setup.py setup.cfg + '[' -f pyproject.toml ']' + for f in pyproject.toml setup.py setup.cfg + '[' -f setup.py ']' + sed -i -E -e '/^requires/s/(['\''"]\s*flit_core\s*>=\s*[0-9]+(\.[0-9]+)+)\s*,\s*<\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\4/' setup.py + sed -i -E -e '/python_requires/s/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/' setup.py + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9a-z]+)*)\s*,\s*(<|!=|<=)\s*[0-9]+(\.[0-9a-z]+)*(-?dev[0-9]*)?(\.\*)*(\s*['\''"]?)/\1\7/g' setup.py + sed -i -E -e 's/(['\''"]\w+\s*)!=(\s*([0-9])+(\.[0-9]+)*\s*['\''"])/\1>\2/g' setup.py + sed -i -E -e 's/(['\''"]\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\5/g' setup.py + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/g' setup.py + sed -i -E -e 's/(['\''"]\s*)\^(\s*[0-9]+(\.[0-9]+)*\s*['\''"])/\1>=\2/g' setup.py + sed -i -e 's/~=/>=/g' setup.py + sed -i -E -e 's/(['\''"]\s*\S*\s*)==(\s*[0-9]+(\.[0-9]+)*)\.\*(\s*['\''"])/\1>=\2\4/g' setup.py + sed -i -E -e 's/(['\''"]?\w*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)[0-9]+(\.[0-9]+)*\s*(['\''"]?)/\1\5/g' setup.py + for f in pyproject.toml setup.py setup.cfg + '[' -f setup.cfg ']' + sed -i -E -e '/^requires/s/(['\''"]\s*flit_core\s*>=\s*[0-9]+(\.[0-9]+)+)\s*,\s*<\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\4/' setup.cfg + sed -i -E -e '/python_requires/s/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/' setup.cfg + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9a-z]+)*)\s*,\s*(<|!=|<=)\s*[0-9]+(\.[0-9a-z]+)*(-?dev[0-9]*)?(\.\*)*(\s*['\''"]?)/\1\7/g' setup.cfg + sed -i -E -e 's/(['\''"]\w+\s*)!=(\s*([0-9])+(\.[0-9]+)*\s*['\''"])/\1>\2/g' setup.cfg + sed -i -E -e 's/(['\''"]\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\s*['\''"])/\1\5/g' setup.cfg + sed -i -E -e 's/(['\''"]?\s*\S*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*(,\s*(<|!=)\s*[0-9]+(\.[0-9]+)*(\.\*)*)+(\s*['\''"]?)/\1\7/g' setup.cfg + sed -i -E -e 's/(['\''"]\s*)\^(\s*[0-9]+(\.[0-9]+)*\s*['\''"])/\1>=\2/g' setup.cfg + sed -i -e 's/~=/>=/g' setup.cfg + sed -i -E -e 's/(['\''"]\s*\S*\s*)==(\s*[0-9]+(\.[0-9]+)*)\.\*(\s*['\''"])/\1>=\2\4/g' setup.cfg + sed -i -E -e 's/(['\''"]?\w*\s*>=\s*[0-9]+(\.[0-9]+)*)\s*,\s*(<|!=)[0-9]+(\.[0-9]+)*\s*(['\''"]?)/\1\5/g' setup.cfg + rm -rfv '*.dist-info/' + '[' -f /usr/bin/python3 ']' + mkdir -p /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir + echo -n + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + VALAFLAGS=-g + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + CXX=g++ + TMPDIR=/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir + RPM_TOXENV=py313 + HOSTNAME=rpmbuild + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_buildrequires.py --generate-extras --python3_pkgversion 3 --wheeldir /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/pyproject-wheeldir --output /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0-2.mga10.x86_64-pyproject-buildrequires Handling setuptools >= 40.8 from default build backend Requirement satisfied: setuptools >= 40.8 (installed: setuptools 78.1.0) Handling cython from get_requires_for_build_wheel Requirement satisfied: cython (installed: cython 3.0.12) Handling setuptools >= 18.0 from get_requires_for_build_wheel Requirement satisfied: setuptools >= 18.0 (installed: setuptools 78.1.0) Handling setuptools_scm from get_requires_for_build_wheel Requirement satisfied: setuptools_scm (installed: setuptools_scm 8.0.4) /usr/lib/python3.13/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.13/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.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: MIT License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running dist_info writing python_pkcs11.egg-info/PKG-INFO writing dependency_links to python_pkcs11.egg-info/dependency_links.txt writing requirements to python_pkcs11.egg-info/requires.txt writing top-level names to python_pkcs11.egg-info/top_level.txt reading manifest file 'python_pkcs11.egg-info/SOURCES.txt' writing manifest file 'python_pkcs11.egg-info/SOURCES.txt' creating '/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/python_pkcs11-0.7.0.dist-info' Handling aenum; python_version < "3.6" from hook generated metadata: Requires-Dist (python-pkcs11) Ignoring alien requirement: aenum; python_version < "3.6" Handling asn1crypto from hook generated metadata: Requires-Dist (python-pkcs11) Requirement satisfied: asn1crypto (installed: asn1crypto 1.5.1) Handling cached-property from hook generated metadata: Requires-Dist (python-pkcs11) Requirement satisfied: cached-property (installed: cached-property 1.5.2) + cat /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0-2.mga10.x86_64-pyproject-buildrequires + rm -rfv python_pkcs11-0.7.0.dist-info/ removed 'python_pkcs11-0.7.0.dist-info/top_level.txt' removed 'python_pkcs11-0.7.0.dist-info/METADATA' removed directory 'python_pkcs11-0.7.0.dist-info/' + RPM_EC=0 ++ jobs -p + exit 0 Executing(%build): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.5EB5r1 + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd python-pkcs11-0.7.0 + '[' 1 -eq 1 ']' + '[' 1 -eq 1 ']' + mkdir -p /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + VALAFLAGS=-g + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + CXX=g++ + TMPDIR=/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir + /usr/bin/python3 -Bs /usr/lib/rpm/redhat/pyproject_wheel.py /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/pyproject-wheeldir Processing /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0 Preparing metadata (pyproject.toml): started Running command Preparing metadata (pyproject.toml) /usr/lib/python3.13/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.13/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.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: MIT License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running dist_info creating /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir/pip-modern-metadata-vbpqruha/python_pkcs11.egg-info writing /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir/pip-modern-metadata-vbpqruha/python_pkcs11.egg-info/PKG-INFO writing dependency_links to /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir/pip-modern-metadata-vbpqruha/python_pkcs11.egg-info/dependency_links.txt writing requirements to /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir/pip-modern-metadata-vbpqruha/python_pkcs11.egg-info/requires.txt writing top-level names to /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir/pip-modern-metadata-vbpqruha/python_pkcs11.egg-info/top_level.txt writing manifest file '/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir/pip-modern-metadata-vbpqruha/python_pkcs11.egg-info/SOURCES.txt' reading manifest file '/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir/pip-modern-metadata-vbpqruha/python_pkcs11.egg-info/SOURCES.txt' writing manifest file '/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir/pip-modern-metadata-vbpqruha/python_pkcs11.egg-info/SOURCES.txt' creating '/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir/pip-modern-metadata-vbpqruha/python_pkcs11-0.7.0.dist-info' Preparing metadata (pyproject.toml): finished with status 'done' Building wheels for collected packages: python-pkcs11 Building wheel for python-pkcs11 (pyproject.toml): started Running command Building wheel for python-pkcs11 (pyproject.toml) /usr/lib/python3.13/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.13/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.13/site-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. !! ******************************************************************************** Please consider removing the following classifiers in favor of a SPDX license expression: License :: OSI Approved :: MIT License See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. ******************************************************************************** !! self._finalize_license_expression() running bdist_wheel running build running build_py creating build/lib.linux-x86_64-cpython-313/pkcs11 copying pkcs11/exceptions.py -> build/lib.linux-x86_64-cpython-313/pkcs11 copying pkcs11/types.py -> build/lib.linux-x86_64-cpython-313/pkcs11 copying pkcs11/constants.py -> build/lib.linux-x86_64-cpython-313/pkcs11 copying pkcs11/__init__.py -> build/lib.linux-x86_64-cpython-313/pkcs11 copying pkcs11/defaults.py -> build/lib.linux-x86_64-cpython-313/pkcs11 copying pkcs11/mechanisms.py -> build/lib.linux-x86_64-cpython-313/pkcs11 creating build/lib.linux-x86_64-cpython-313/pkcs11/util copying pkcs11/util/dh.py -> build/lib.linux-x86_64-cpython-313/pkcs11/util copying pkcs11/util/rsa.py -> build/lib.linux-x86_64-cpython-313/pkcs11/util copying pkcs11/util/x509.py -> build/lib.linux-x86_64-cpython-313/pkcs11/util copying pkcs11/util/__init__.py -> build/lib.linux-x86_64-cpython-313/pkcs11/util copying pkcs11/util/ec.py -> build/lib.linux-x86_64-cpython-313/pkcs11/util copying pkcs11/util/dsa.py -> build/lib.linux-x86_64-cpython-313/pkcs11/util running egg_info writing python_pkcs11.egg-info/PKG-INFO writing dependency_links to python_pkcs11.egg-info/dependency_links.txt writing requirements to python_pkcs11.egg-info/requires.txt writing top-level names to python_pkcs11.egg-info/top_level.txt reading manifest file 'python_pkcs11.egg-info/SOURCES.txt' writing manifest file 'python_pkcs11.egg-info/SOURCES.txt' copying pkcs11/_errors.pyx -> build/lib.linux-x86_64-cpython-313/pkcs11 copying pkcs11/_mswin.pxd -> build/lib.linux-x86_64-cpython-313/pkcs11 copying pkcs11/_pkcs11.pyx -> build/lib.linux-x86_64-cpython-313/pkcs11 copying pkcs11/_pkcs11_defn.pxd -> build/lib.linux-x86_64-cpython-313/pkcs11 copying pkcs11/_utils.pyx -> build/lib.linux-x86_64-cpython-313/pkcs11 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 building 'pkcs11._pkcs11' extension creating build/temp.linux-x86_64-cpython-313/pkcs11 gcc -O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full -fPIC -I/usr/include/python3.13 -c pkcs11/_pkcs11.c -o build/temp.linux-x86_64-cpython-313/pkcs11/_pkcs11.o gcc -shared -Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full build/temp.linux-x86_64-cpython-313/pkcs11/_pkcs11.o -L/usr/lib64 -lpython3.13 -o build/lib.linux-x86_64-cpython-313/pkcs11/_pkcs11.cpython-313-x86_64-linux-gnu.so installing to build/bdist.linux-x86_64/wheel running install running install_lib creating build/bdist.linux-x86_64/wheel creating build/bdist.linux-x86_64/wheel/pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/exceptions.py -> build/bdist.linux-x86_64/wheel/./pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/_pkcs11.cpython-313-x86_64-linux-gnu.so -> build/bdist.linux-x86_64/wheel/./pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/_errors.pyx -> build/bdist.linux-x86_64/wheel/./pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/types.py -> build/bdist.linux-x86_64/wheel/./pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/_pkcs11_defn.pxd -> build/bdist.linux-x86_64/wheel/./pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/_utils.pyx -> build/bdist.linux-x86_64/wheel/./pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/_pkcs11.pyx -> build/bdist.linux-x86_64/wheel/./pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/_mswin.pxd -> build/bdist.linux-x86_64/wheel/./pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/constants.py -> build/bdist.linux-x86_64/wheel/./pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/__init__.py -> build/bdist.linux-x86_64/wheel/./pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/defaults.py -> build/bdist.linux-x86_64/wheel/./pkcs11 copying build/lib.linux-x86_64-cpython-313/pkcs11/mechanisms.py -> build/bdist.linux-x86_64/wheel/./pkcs11 creating build/bdist.linux-x86_64/wheel/pkcs11/util copying build/lib.linux-x86_64-cpython-313/pkcs11/util/dh.py -> build/bdist.linux-x86_64/wheel/./pkcs11/util copying build/lib.linux-x86_64-cpython-313/pkcs11/util/rsa.py -> build/bdist.linux-x86_64/wheel/./pkcs11/util copying build/lib.linux-x86_64-cpython-313/pkcs11/util/x509.py -> build/bdist.linux-x86_64/wheel/./pkcs11/util copying build/lib.linux-x86_64-cpython-313/pkcs11/util/__init__.py -> build/bdist.linux-x86_64/wheel/./pkcs11/util copying build/lib.linux-x86_64-cpython-313/pkcs11/util/ec.py -> build/bdist.linux-x86_64/wheel/./pkcs11/util copying build/lib.linux-x86_64-cpython-313/pkcs11/util/dsa.py -> build/bdist.linux-x86_64/wheel/./pkcs11/util running install_egg_info Copying python_pkcs11.egg-info to build/bdist.linux-x86_64/wheel/./python_pkcs11-0.7.0-py3.13.egg-info running install_scripts creating build/bdist.linux-x86_64/wheel/python_pkcs11-0.7.0.dist-info/WHEEL creating '/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir/pip-wheel-kjymgsnw/.tmp-2a7fk53v/python_pkcs11-0.7.0-cp313-cp313-linux_x86_64.whl' and adding 'build/bdist.linux-x86_64/wheel' to it adding 'pkcs11/__init__.py' adding 'pkcs11/_errors.pyx' adding 'pkcs11/_mswin.pxd' adding 'pkcs11/_pkcs11.cpython-313-x86_64-linux-gnu.so' adding 'pkcs11/_pkcs11.pyx' adding 'pkcs11/_pkcs11_defn.pxd' adding 'pkcs11/_utils.pyx' adding 'pkcs11/constants.py' adding 'pkcs11/defaults.py' adding 'pkcs11/exceptions.py' adding 'pkcs11/mechanisms.py' adding 'pkcs11/types.py' adding 'pkcs11/util/__init__.py' adding 'pkcs11/util/dh.py' adding 'pkcs11/util/dsa.py' adding 'pkcs11/util/ec.py' adding 'pkcs11/util/rsa.py' adding 'pkcs11/util/x509.py' adding 'python_pkcs11-0.7.0.dist-info/METADATA' adding 'python_pkcs11-0.7.0.dist-info/WHEEL' adding 'python_pkcs11-0.7.0.dist-info/top_level.txt' adding 'python_pkcs11-0.7.0.dist-info/RECORD' removing build/bdist.linux-x86_64/wheel Building wheel for python-pkcs11 (pyproject.toml): finished with status 'done' Created wheel for python-pkcs11: filename=python_pkcs11-0.7.0-cp313-cp313-linux_x86_64.whl size=1575632 sha256=fdde3a82791fdc8edc17e3d10bae86784c82468b7edce472f8a149df19cb869d Stored in directory: /home/pterjan/.cache/pip/wheels/6e/b3/fd/506f2f8368f4e963c836c4d405d61a36f10a545b718ba5feb8 Successfully built python-pkcs11 + RPM_EC=0 ++ jobs -p + exit 0 Executing(%install): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.XVJj1W + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + '[' 1 -eq 1 ']' + '[' /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT '!=' / ']' + rm -rf /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT ++ dirname /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT + mkdir -p /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + mkdir /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd python-pkcs11-0.7.0 + '[' 1 -eq 1 ']' ++ xargs basename --multiple ++ ls /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/pyproject-wheeldir/python_pkcs11-0.7.0-cp313-cp313-linux_x86_64.whl ++ sed -E 's/([^-]+)-([^-]+)-.+\.whl/\1==\2/' + specifier=python_pkcs11==0.7.0 + '[' -z python_pkcs11==0.7.0 ']' + TMPDIR=/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/.pyproject-builddir + /usr/bin/python3 -m pip install --root /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT --prefix /usr --no-deps --disable-pip-version-check --progress-bar off --verbose --ignore-installed --no-warn-script-location --no-index --no-cache-dir --find-links /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/pyproject-wheeldir python_pkcs11==0.7.0 Using pip 25.0.1 from /usr/lib/python3.13/site-packages/pip (python 3.13) Looking in links: /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/pyproject-wheeldir Processing ./pyproject-wheeldir/python_pkcs11-0.7.0-cp313-cp313-linux_x86_64.whl Installing collected packages: python_pkcs11 Successfully installed python_pkcs11-0.7.0 + '[' -d /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/bin ']' + rm -f /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0-2.mga10.x86_64-pyproject-ghost-distinfo + site_dirs=() + '[' -d /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib/python3.13/site-packages ']' + '[' /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib64/python3.13/site-packages '!=' /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib/python3.13/site-packages ']' + '[' -d /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib64/python3.13/site-packages ']' + site_dirs+=("/usr/lib64/python3.13/site-packages") + for site_dir in ${site_dirs[@]} + for distinfo in /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT$site_dir/*.dist-info + echo '%ghost /usr/lib64/python3.13/site-packages/python_pkcs11-0.7.0.dist-info' + sed -i s/pip/rpm/ /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib64/python3.13/site-packages/python_pkcs11-0.7.0.dist-info/INSTALLER + PYTHONPATH=/usr/lib/rpm/redhat + /usr/bin/python3 -B /usr/lib/rpm/redhat/pyproject_preprocess_record.py --buildroot /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT --record /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib64/python3.13/site-packages/python_pkcs11-0.7.0.dist-info/RECORD --output /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0-2.mga10.x86_64-pyproject-record + rm -fv /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib64/python3.13/site-packages/python_pkcs11-0.7.0.dist-info/RECORD removed '/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib64/python3.13/site-packages/python_pkcs11-0.7.0.dist-info/RECORD' + rm -fv /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib64/python3.13/site-packages/python_pkcs11-0.7.0.dist-info/REQUESTED removed '/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib64/python3.13/site-packages/python_pkcs11-0.7.0.dist-info/REQUESTED' ++ wc -l /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0-2.mga10.x86_64-pyproject-ghost-distinfo ++ cut -f1 '-d ' + lines=1 + '[' 1 -ne 1 ']' + RPM_FILES_ESCAPE=4.19 + /usr/bin/python3 /usr/lib/rpm/redhat/pyproject_save_files.py --output-files /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0-2.mga10.x86_64-pyproject-files --output-modules /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0-2.mga10.x86_64-pyproject-modules --buildroot /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT --sitelib /usr/lib/python3.13/site-packages --sitearch /usr/lib64/python3.13/site-packages --python-version 3.13 --pyproject-record /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0-2.mga10.x86_64-pyproject-record --prefix /usr pkcs11 + /usr/bin/find-debuginfo -j16 --strict-build-id -m -i --build-id-seed 0.7.0-2.mga10 --unique-debug-suffix -0.7.0-2.mga10.x86_64 --unique-debug-src-base python-pkcs11-0.7.0-2.mga10.x86_64 --run-dwz --dwz-low-mem-die-limit 10000000 --dwz-max-die-limit 110000000 -S debugsourcefiles.list /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0 find-debuginfo: starting Extracting debug info from 1 files DWARF-compressing 1 files sepdebugcrcfix: Updated 1 CRC32s, 0 CRC32s did match. Creating .debug symlinks for symlinks to ELF files Copying sources found by 'debugedit -l' to /usr/src/debug/python-pkcs11-0.7.0-2.mga10.x86_64 find-debuginfo: done + /usr/lib/rpm/check-buildroot + '[' -n '' ']' + /usr/share/spec-helper/clean_files + '[' -n '' ']' + /usr/share/spec-helper/compress_files .xz + '[' -n '' ']' + /usr/share/spec-helper/relink_symlinks + '[' -n '' ']' + /usr/share/spec-helper/clean_perl + '[' -n '' ']' + /usr/share/spec-helper/lib_symlinks + '[' -n '' ']' + /usr/share/spec-helper/gprintify + '[' -n '' ']' + /usr/share/spec-helper/fix_mo + '[' -n '' ']' + /usr/share/spec-helper/fix_pamd + '[' -n '' ']' + /usr/share/spec-helper/remove_info_dir + '[' -n '' ']' + /usr/share/spec-helper/fix_eol + '[' -n '' ']' + /usr/share/spec-helper/check_desktop_files + '[' -n '' ']' + /usr/share/spec-helper/check_elf_files + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/brp-remove-la-files + /usr/lib/rpm/redhat/brp-mangle-shebangs + env -u SOURCE_DATE_EPOCH /usr/lib/rpm/redhat/brp-python-bytecompile '' 1 0 -j16 Bytecompiling .py files below /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib64/python3.13 using python3.13 Not clamping source mtimes, $SOURCE_DATE_EPOCH not set Bytecompiling .py files below /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib/debug/usr/lib64/python3.13 using python3.13 Not clamping source mtimes, $SOURCE_DATE_EPOCH not set + /usr/lib/rpm/redhat/brp-python-hardlink Reading /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/SPECPARTS/rpm-debuginfo.specpart Executing(%check): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.YgXZYQ + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + CFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CFLAGS + CXXFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full' + export CXXFLAGS + FFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FFLAGS + FCFLAGS='-O2 -g -pipe -Wformat -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -m64 -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection=full ' + export FCFLAGS + VALAFLAGS=-g + export VALAFLAGS + RUSTFLAGS='-Copt-level=3 -Cdebuginfo=2 -Ccodegen-units=1 -Cstrip=none --cap-lints=warn' + export RUSTFLAGS + LDFLAGS='-Wl,--as-needed -Wl,--no-undefined -Wl,-z,relro -Wl,-z,now -Wl,-O1 -Wl,--build-id=sha1 -Wl,--enable-new-dtags -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + export LDFLAGS + LT_SYS_LIBRARY_PATH=/usr/lib64: + export LT_SYS_LIBRARY_PATH + CC=gcc + export CC + CXX=g++ + export CXX + cd python-pkcs11-0.7.0 + '[' 1 -eq 1 ']' + '[' '!' -f /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0-2.mga10.x86_64-pyproject-modules ']' + PATH=/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/pterjan/.local/bin:/home/pterjan/bin + PYTHONPATH=/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib64/python3.13/site-packages:/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib/python3.13/site-packages + _PYTHONSITE=/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib64/python3.13/site-packages:/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/lib/python3.13/site-packages + PYTHONDONTWRITEBYTECODE=1 + /usr/bin/python3 -sP /usr/lib/rpm/redhat/import_all_modules.py -f /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0-2.mga10.x86_64-pyproject-modules Check import: pkcs11 Check import: pkcs11.constants Check import: pkcs11.defaults Check import: pkcs11.exceptions Check import: pkcs11.mechanisms Check import: pkcs11.types Check import: pkcs11.util Check import: pkcs11.util.dh Check import: pkcs11.util.dsa Check import: pkcs11.util.ec Check import: pkcs11.util.rsa Check import: pkcs11.util.x509 + RPM_EC=0 ++ jobs -p + exit 0 Processing files: python3-python-pkcs11-0.7.0-2.mga10.x86_64 Executing(%doc): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.9IPfwl + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + cd python-pkcs11-0.7.0 + DOCDIR=/home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/share/doc/python3-python-pkcs11 + export LC_ALL=C + LC_ALL=C + export DOCDIR + /usr/bin/mkdir -p /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/share/doc/python3-python-pkcs11 + cp -pr /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/python-pkcs11-0.7.0/README.rst /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT/usr/share/doc/python3-python-pkcs11 + RPM_EC=0 ++ jobs -p + exit 0 Provides: python-python-pkcs11 = 0.7.0-2.mga10 python3-python-pkcs11 = 0.7.0-2.mga10 python3-python-pkcs11(x86-64) = 0.7.0-2.mga10 python3.13-python-pkcs11 = 0.7.0-2.mga10 python3.13dist(python-pkcs11) = 0.7 python3dist(python-pkcs11) = 0.7 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PartialHardlinkSets) <= 4.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Requires: libc.so.6()(64bit) libc.so.6(GLIBC_2.14)(64bit) libc.so.6(GLIBC_2.2.5)(64bit) libc.so.6(GLIBC_2.3.4)(64bit) libc.so.6(GLIBC_2.34)(64bit) libc.so.6(GLIBC_2.4)(64bit) libpython3.13.so.1.0()(64bit) python(abi) = 3.13 python3.13dist(asn1crypto) python3.13dist(cached-property) Processing files: python-pkcs11-debugsource-0.7.0-2.mga10.x86_64 Provides: python-pkcs11-debugsource = 0.7.0-2.mga10 python-pkcs11-debugsource(x86-64) = 0.7.0-2.mga10 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Processing files: python3-python-pkcs11-debuginfo-0.7.0-2.mga10.x86_64 Provides: debuginfo(build-id) = 0f5a0e4103dee7a57c4b961589c91444b5e0d5d4 python-python-pkcs11-debuginfo = 0.7.0-2.mga10 python3-python-pkcs11-debuginfo = 0.7.0-2.mga10 python3-python-pkcs11-debuginfo(x86-64) = 0.7.0-2.mga10 python3.13-python-pkcs11-debuginfo = 0.7.0-2.mga10 Requires(rpmlib): rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(FileDigests) <= 4.6.0-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 Recommends: python-pkcs11-debugsource(x86-64) = 0.7.0-2.mga10 Checking for unpackaged file(s): /usr/lib/rpm/check-files /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build/BUILDROOT Wrote: /home/pterjan/rpmbuild/RPMS/x86_64/python3-python-pkcs11-0.7.0-2.mga10.x86_64.rpm Wrote: /home/pterjan/rpmbuild/RPMS/x86_64/python-pkcs11-debugsource-0.7.0-2.mga10.x86_64.rpm Wrote: /home/pterjan/rpmbuild/RPMS/x86_64/python3-python-pkcs11-debuginfo-0.7.0-2.mga10.x86_64.rpm Executing(rmbuild): /bin/sh -e /home/pterjan/rpmbuild/tmp/rpm-tmp.2YQtMG + umask 022 + cd /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + test -d /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + /usr/bin/chmod -Rf a+rX,u+w,g-w,o-w /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + rm -rf /home/pterjan/rpmbuild/BUILD/python-pkcs11-0.7.0-build + RPM_EC=0 ++ jobs -p + exit 0 D: [iurt_root_command] Success!