Bug 2400481 - tpm2-pkcs11-1.10.0 is available
Summary: tpm2-pkcs11-1.10.0 is available
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: tpm2-pkcs11
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Jelen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-30 16:28 UTC by Upstream Release Monitoring
Modified: 2026-05-20 14:22 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-05-20 14:22:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2025-09-30 16:28:29 UTC
Releases retrieved: 1.9.2
Upstream release that is considered latest: 1.9.2
Current version/release in rawhide: 1.9.1-6.fc44
URL: https://tpm2-software.github.io

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/18777/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/tpm2-pkcs11

Comment 1 Jakub Jelen 2025-10-01 13:57:07 UTC
the p11-kit modules installation is broken with https://github.com/tpm2-software/tpm2-pkcs11/pull/818
one more tests is now requiring some dead python module which needs to be disabled: https://github.com/tpm2-software/tpm2-pkcs11/issues/908

The current patch, which I can use to build the package:
```
diff --git a/tpm2-pkcs11.spec b/tpm2-pkcs11.spec
index 0701984..42dcc12 100644
--- a/tpm2-pkcs11.spec
+++ b/tpm2-pkcs11.spec
@@ -1,8 +1,8 @@
 #global candidate RC0
 
 Name:		tpm2-pkcs11
-Version:	1.9.1
-Release:	6%{?candidate:.%{candidate}}%{?dist}
+Version:	1.9.2
+Release:	1%{?candidate:.%{candidate}}%{?dist}
 Summary:	PKCS#11 interface for TPM 2.0 hardware
 
 License:	BSD-2-Clause
@@ -67,7 +67,8 @@ popd >&2
 
 
 %build
-%configure --enable-unit --with-fapi=yes
+# the ptool-checks require python pkcs11 module, which was not updated for 20 years!
+%configure --enable-unit --with-fapi=yes --disable-ptool-checks
 %{make_build}
 pushd tools
 %pyproject_wheel
```
up to the %files stage, where it fails to find the p11-kit modules due to problem above.

Assigning, but it needs some upstream fixes before we can update it

Comment 2 Upstream Release Monitoring 2026-05-20 01:04:25 UTC
Releases retrieved: 1.10.0
Upstream release that is considered latest: 1.10.0
Current version/release in rawhide: 1.9.1-7.fc44
URL: https://tpm2-software.github.io

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/18777/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/tpm2-pkcs11

Comment 3 Jakub Jelen 2026-05-20 14:22:26 UTC
Built in rawhide:

https://koji.fedoraproject.org/koji/taskinfo?taskID=145682617


Note You need to log in before you can comment on or make changes to this bug.