The file from f43 is a newer version than the one from f44 so it won’t upgrade it.
These do not appear to be the full messages you probably saw. It is always best to show the full detailed messages and not an interpreted version that is incomplete.
AFAIK you probably should not have both those packages installed. They are both power control related and function differently.
I would suggest removing the tlp package to eliminate that conflict.
You may be able to do a full online upgrade using dnf sudo dnf distro-sync --releasever=44 --allowerasing --setopt=protected_packages=
When you show things like this it is best to show the command and results. Such as: (so we see the exact list the system uses)
$ dnf repolist
repo id repo name
adoptium-temurin-java-repository Adoptium
code Visual Studio Code
copr:copr.fedorainfracloud.org:phracek:PyCharm Copr repo for PyCharm owned by phracek
fedora Fedora 44 - x86_64
fedora-cisco-openh264 Fedora 44 openh264 (From Cisco) - x86_64
google-chrome google-chrome
google-earth-pro google-earth-pro
masterpdfeditor Master PDF Editor
rpmfusion-free RPM Fusion for Fedora 44 - Free
rpmfusion-free-tainted RPM Fusion for Fedora 44 - Free tainted
rpmfusion-free-updates RPM Fusion for Fedora 44 - Free - Updates
rpmfusion-nonfree RPM Fusion for Fedora 44 - Nonfree
rpmfusion-nonfree-nvidia-driver RPM Fusion for Fedora 44 - Nonfree - NVIDIA Driver
rpmfusion-nonfree-steam RPM Fusion for Fedora 44 - Nonfree - Steam
rpmfusion-nonfree-updates RPM Fusion for Fedora 44 - Nonfree - Updates
updates Fedora 44 - x86_64 - Updates
The download completed successfully, but the transaction still fails with only these remaining conflicts:
Transaction failed: Rpm transaction failed.
- file /usr/bin/gnupg-key-manage from install of gpgme-2.0.1-4.fc44.x86_64 conflicts with file from package gpgme2-2.0.1-5.fc43.x86_64
- file /usr/lib64/libgpgme.so.45.0.1 from install of gpgme-2.0.1-4.fc44.x86_64 conflicts with file from package gpgme2-2.0.1-5.fc43.x86_64
- file /usr/lib64/libgpgmepp.so.7.0.0 from install of gpgmepp-2.0.1-4.fc44.x86_64 conflicts with file from package gpgme2pp-2.0.1-5.fc43.x86_64
- file /usr/lib64/libqgpgmeqt6.so.15v2.7.0 from install of qgpgme-qt6-2.0.1-4.fc44.x86_64 conflicts with file from package qgpgme2-qt6-2.0.1-5.fc43.x86_64
For reference:
sudo dnf check reports no issues.
sudo dnf repoquery --duplicates returns no duplicate packages.
I’m running Fedora 43 KDE Plasma.
The gpgme2 packages are official Fedora packages and are required by KDE PIM packages such as akonadi-calendar, kmail-libs, mailcommon, messagelib, and mimetreeparser.
Do you think this is a packaging issue with the gpgme2 compatibility packages, or is there another recommended migration step before upgrading to Fedora 44?
Hi, I have the same problem with gpgme2 when trying to update Fedora KDE from version 43 to version 44 using the command sudo dnf system-upgrade download --releasever=44.
The update fails with the message
Transaction failed: Rpm transaction failed.
- file /usr/bin/gnupg-key-manage from install of gpgme-2.0.1-4.fc44.x86_64 conflicts with file from package gpgme2-2.0.1-5.fc43.x86_64
- file /usr/lib64/libgpgme.so.45.0.1 from install of gpgme-2.0.1-4.fc44.x86_64 conflicts with file from package gpgme2-2.0.1-5.fc43.x86_64
- file /usr/lib64/libgpgmepp.so.7.0.0 from install of gpgmepp-2.0.1-4.fc44.x86_64 conflicts with file from package gpgme2pp-2.0.1-5.fc43.x86_64
- file /usr/lib64/libqgpgmeqt6.so.15v2.7.0 from install of qgpgme-qt6-2.0.1-4.fc44.x86_64 conflicts with file from package qgpgme2-qt6-2.0.1-5.fc43.x86_64
As @computersavvy mentioned the version of gpgme seems to be newer in fedora 43 (2.0.1-5) than in fedora 44 (2.0.1-4), but I also noticed that the package name is different, fedora 43 has gpgme2 while fedora 44 has gpgme.
Yes, I am also hesitant to manually delete anything, since I am not experienced and don’t know what these packages do or are needed for. However, in fedora packages there doesn’t seem to be a gpgpme2 for fedora 44, so I would expect the system to see this and remove gpgme2 itself during the update. Maybe it will work automatically once gpgme for fedora 44 catches up with the version of gpgme2 on fedora 43.
You may be able to resolve that conflict with swapping the packages. sudo dnf swap gpgme2 gpgme --releasever=44
If that works then the upgrade to 44 should complete properly. It should only be an issue if there is some installed package that explicitly requires gpgme2, and it should tell you exactly where the issue is should there be a dependency issue.
I use Workstation (gnome) and have never seen that conflict. I had gpgme installed all the way back on f42 (my last clean install) and have never had the gpgme2 packages.
Thanks for the information @anotheruser, in this case I will wait and try again tomorrow.
@computersavvy thank you for the tip and the information, but I will see if waiting for the new version in fedora 44 makes it work without needing to swap the packages. Regarding packages explicitly requiring gpgme2 I would doubt this is the case in fedora 44, since it seems that gpgme2 itself doesn’t exist for fedora 44.
Actually that linked info provides a command that should solve the issue. sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-4af373d015
The fix appears to already be in the updates-testing repo.
The dependencies are usually against the library the package provides, in this case libgpgme.so.45()(64bit). In Fedora 43 gpgme provides libgpgme.so.11()(64bit). That is the change in SONAME which went from 11 → 45, and which indicates a break of binary compatibility.
Could you please check whether the advisory ID is correct, or if there is another update or recommended migration path for this package transition?
I’d really appreciate it if someone could help me resolve this issue. At this point I’ve tried the suggested upgrade methods, removed the tlp conflict, and the only remaining problem is the gpgme2 package conflict preventing the Fedora 44 upgrade. If anyone knows the correct way to fix this, I’d be very grateful for your guidance.
The updates rpm is available in updates-testing releasever=44.
However, consider that a lot of packes from Fedora43 requires gpgme-1.24.3-6.fc43.x86_64 and gpgmepp-1.24.3-6.fc43.x86_64, so you cant replace gpgme with the version from Fedora44 untell all the other packages has been upgraded. These packages should work with gpgme2pp from Fedora 43 so if you can do the upgraded and let it skip updating gpgme it should work.
After that you can deal with gpgme. If you remove gpgme.fc43 it should reveal which package might have prevented the system to upgrade the gpgme package. You can enable the updates-testing repository to get the latest gpgme version as mentioned in the adversary.
Why so impatient? The f44 gpgme update has been submitted to stable, should be available tomorrow if the composes jobs don’t run into any issues.
Alternatively, you could also remove gpgme2 and gpgme2pp with rpm and then start the system-upgrade. This will ofc break all F43 programs that require gpgme2.