Bug 2292911
Summary: | rust-cryptoki-0.9.0 is available | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> |
Component: | rust-cryptoki | Assignee: | Peter Robinson <pbrobinson> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | decathorpe, jjelen, pbrobinson, rust-sig |
Target Milestone: | --- | Keywords: | FutureFeature, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | rust-cryptoki-0.9.0-1.fc42 | Doc Type: | --- |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2025-05-28 01:55:57 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2292912, 2305397, 2360957 | ||
Bug Blocks: |
Description
Upstream Release Monitoring
2024-06-18 15:23:07 UTC
Releases retrieved: 0.8.0 Upstream release that is considered latest: 0.8.0 Current version/release in rawhide: 0.6.2-2.fc41 URL: https://crates.io/crates/cryptoki 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/272339/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/rust-cryptoki Releases retrieved: 0.9.0 Upstream release that is considered latest: 0.9.0 Current version/release in rawhide: 0.6.2-3.fc42 URL: https://crates.io/crates/cryptoki 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/272339/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/rust-cryptoki Is there anything blocking the update to 0.9 version? Anything I can help with? PR or any other attempt to update the package? Updating probably wasn't possible previously because dependent packages were explicitly depending on version 0.6. Those dependent packages were retired from F42+ so that blocker should be resolved. (In reply to Fabio Valentini from comment #4) > Updating probably wasn't possible previously because dependent packages were > explicitly depending on version 0.6. Thank you for checking! > Those dependent packages were retired from F42+ so that blocker should be > resolved. I tried building this locally and it looks like the cryptoki-sys needs to go first (bug #2292912 with PR) and then there is a new test dependency, which for I filled the following review request (bug #2360957). (In reply to Fabio Valentini from comment #4) > Updating probably wasn't possible previously because dependent packages were > explicitly depending on version 0.6. Correct, that was the main blocker. > Those dependent packages were retired from F42+ so that blocker should be > resolved. And the other was there was some deps that needed bumping, it was on my list now the dependents are out of the way for F-42+ to look and link this (and the -sys crate) to any on the deps so it's tracked. There was no point doing that until I'd uncoupled the dependents :) Thanks for the answer. I did some digging did package missing dependency and opened PRs for these. Discussed a bit on Fedora Rust matrix channel with Fabio and it turns out from these, there is a remaining issue the cryptoki-sys needs bindgen-0.70, which is not yet in Fedora bumped (mentioned in bug #2292912). Not sure I will have enough time to help more with the bindgen though. > Not sure I will have enough time to help more with the bindgen though.
Yeah, I am unable to deal with bindgen, but I can look at this once that lands.
Sounds like all the dependencies are resolved and PRs filled: https://src.fedoraproject.org/rpms/rust-cryptoki-sys/pull-request/1 https://src.fedoraproject.org/rpms/rust-cryptoki/pull-request/2 Any chance getting them merged and built in rawhide + F42? I will do it today, I had missed that the bindgen dep had landed. Thank you! FEDORA-2025-3cacc54f6d (rust-cryptoki-0.9.0-1.fc42 and rust-cryptoki-sys-0.3.0-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-3cacc54f6d FEDORA-2025-3cacc54f6d has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-3cacc54f6d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-3cacc54f6d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-3cacc54f6d (rust-cryptoki-0.9.0-1.fc42 and rust-cryptoki-sys-0.3.0-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. |