Bug 2252823
| Summary: | yubico-piv-tool-2.4.1 is available | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||||
| Component: | yubico-piv-tool | Assignee: | Jakub Jelen <jjelen> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | jjelen, orion | ||||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | yubico-piv-tool-2.4.2-1.fc39 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2023-12-20 01:24:43 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: | |||||||||
| Attachments: |
|
||||||||
|
Description
Upstream Release Monitoring
2023-12-04 21:43:33 UTC
Created attachment 2002788 [details]
Update to 2.4.0 (#2252823)
the-new-hotness/release-monitoring.org's scratch build of yubico-piv-tool-2.4.0-1.fc38.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=109915201 The upstream issue that prevents building the package on 32b arch: https://github.com/Yubico/yubico-piv-tool/issues/456 Releases retrieved: 2.4.1 Upstream release that is considered latest: 2.4.1 Current version/release in rawhide: 2.3.1-2.fc39 URL: https://developers.yubico.com/yubico-piv-tool/ 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/6998/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/yubico-piv-tool Created attachment 2002837 [details]
Update to 2.4.1 (#2252823)
the-new-hotness/release-monitoring.org's scratch build of yubico-piv-tool-2.4.1-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=109950654 FEDORA-2023-a4d5454394 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a4d5454394 FEDORA-2023-a4d5454394 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-a4d5454394` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a4d5454394 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-5c8513d6e8 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-5c8513d6e8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5c8513d6e8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-5c8513d6e8 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. |