Bug 2429875
| Summary: | Upgrade from Fedora 42 to 43 does not install gnupg2-scdaemon | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Evgeni Golov <egolov> |
| Component: | gnupg2 | Assignee: | Jakub Jelen <jjelen> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 43 | CC: | bcl, crypto-team, decathorpe, jjelen, tm |
| Target Milestone: | --- | Keywords: | Upgrades |
| Target Release: | --- | Flags: | fedora-admin-xmlrpc:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | gnupg2-2.4.9-4.fc43 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2026-01-23 00:55:53 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: | |||
|
Description
Evgeni Golov
2026-01-15 09:14:42 UTC
Thank you for the report! Wondering what would be the best solution for this now given that all the Fedora versions have gnupg2-2.4.9-1 now :/ I guess that given that the only fedora not having this is f42, we could do something like this for f43+: %global split_min_version 2.4.8-2.fc43 but I did not test it yet. Fabio, what do you think? > %global split_min_version 2.4.8-2.fc43
Eh ... why would this help?
Adding a suffix won't change the lexicographic ordering (2.4.9 still !< 2.4.8whateverfollowshere).
Maybe (**maybe**) setting this would work (until the *next* f42 update, of course):
%global split_min_version 2.4.9-1.fc42.1
Sorry, I obviously meant 2.4.9-1.fc42 but was too fast writing. And indeed it would need to change the obsoletes conditions to `Obsoletes: gnupg2 <= %{split_min_version}`
Your suggestion of having the .1 without the need to change the Obsoletes conditions so I will likely go ahead with that one later today.
I hope we will not need to update the Fedora 42 anymore, but if we do, I will make sure this will be up to date.
Assuming Fedora 42 would never get a version before Fedora 43, what about:
%global split_min_version %{version}-1.fc42
Obsoletes: gnupg2 <= %{split_min_version}
or
%global split_min_version %{version}-1.fc42.1
Obsoletes: gnupg2 < %{split_min_version}
Wait, no, that would also trigger on gnupg2-2.4.9-1.fc43.x86_64 to gnupg2-2.4.10-1.fc43.x86_64, as 2.4.9-1.fc43 < 2.4.10-1.fc42.
Just don't update gnupg in f42 anymore ;)
FEDORA-2026-c35e3ecd6c (gnupg2-2.4.9-3.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-c35e3ecd6c FEDORA-2026-650c8b9bc9 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-650c8b9bc9` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-650c8b9bc9 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2026-650c8b9bc9 (gnupg2-2.4.9-4.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. |