Bug 2292915
| Summary: | libassuan-3.0.2 is available | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||||||
| Component: | libassuan | Assignee: | Jakub Jelen <jjelen> | ||||||||
| Status: | ASSIGNED --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | crypto-team, jjelen, rdieter, tm | ||||||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||||||
| Target Release: | --- | Flags: | fedora-admin-xmlrpc:
mirror+
|
||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 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
2024-06-18 15:29:55 UTC
Created attachment 2037699 [details]
Update to 3.0.0 (#2292915)
the-new-hotness/release-monitoring.org's scratch build of libassuan-3.0.0-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=119241614 The new package bumps ABI 0.8.7->9.0.0 I tried to rebuild it in copr, but gnupg2 has cyclic build-time dependency on itself so when the new ABI of libasssuan is installed, the gnupg2 is not possible to install in the buildroot of gnupg2 itself: https://copr.fedorainfracloud.org/coprs/jjelen/libassuan/ So this will either need explicit provides of compat-version in the new libassuan build, bootstrap gnupg2 (without checking signatures), providing separate libassuan2 package based on the LST version 2.5.7 and/or side-tag build. There are just half a dozen of dependencies of this package (createrepo-agent, gnupg-pkcs11-scd, gnupg2, gpgme, kleopatra, pinentry) and neither of them requires the v3 API so we can stay on the 2.5.x stable branch for now. Releases retrieved: 3.0.1 Upstream release that is considered latest: 3.0.1 Current version/release in rawhide: 2.5.7-1.fc41 URL: https://gnupg.org/software/libassuan/index.html 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/1559/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/libassuan Created attachment 2038156 [details]
Update to 3.0.1 (#2292915)
the-new-hotness/release-monitoring.org's scratch build of libassuan-3.0.1-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=119506782 This was discussed on https://lists.gnupg.org/pipermail/gnupg-devel/2024-June/035587.html with the release of 3.0.1 -- I did not have time to dig into that more than seeing the bump is still there and the recursive issue of building of gnupg2 with the new libassuan is still there. Releases retrieved: 3.0.2 Upstream release that is considered latest: 3.0.2 Current version/release in rawhide: 2.5.7-3.fc42 URL: https://gnupg.org/software/libassuan/index.html 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/1559/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/libassuan Created attachment 2076973 [details]
Update to 3.0.2 (#2292915)
the-new-hotness/release-monitoring.org's scratch build of libassuan-3.0.2-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=129378176 |