Fedora Account System
Red Hat Associate
Red Hat Customer
Error message: <html>Internal error:<br/><br/>Error running transaction: 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</html> 3 attempts with a reboot has resulted in the same thing. Reproducible: Always Steps to Reproduce: 1.In Discover select "Fedora Linux 44" 2.click update all 3.get above message Actual Results: <html>Internal error:<br/><br/>Error running transaction: 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</html> Expected Results: Install all packages with no error message
Seems someone already made changes in git repo without notifying me. From the looks of it, creating the bodhi update should handle this for Fedora 44. Rawhide will be a bit more fun, as gpgme is already split to several packages as per upstream.
in Fedora 44, qgpgme is still part of gpgme, reassigning
FEDORA-2026-4af373d015 (gpgme-2.0.1-5.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-4af373d015
FEDORA-2026-4af373d015 has been pushed to the Fedora 44 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-4af373d015` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-4af373d015 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Let me know when this testing repro is ready ->No advisory found matching the requested name: "FEDORA-2026-4af373d015" Thanks
Once it posted the comment #4 it was ready. The issue you have (I guess) is that you are trying to update to Fedora 44, so you are still on Fedora 43, right? The fix has to happen in Fedora 44 repository, so when you try to update on your system - Fedora 43, it does not find anything, as there isn't anything. There are two options - A) if your upgraded method allows it, you can enable/add F44 updates testing repository BUT you will get all testing updates, which can cause a problem if there is currently some bad update being tested, or option B) wait for the change to land in regular updates repository (this bug will close) and test again. Also, there is option C) as Fedora 43 was released with gpgme 1.24.3, there should only a few packages that require gpgme2, so you can try to uninstall gpgme2 which will probably want to uninstall some other packages. CHECK what dnf will want to uninstall as well and if that is reasonable. Update system to F44 and reinstall those packages back.
*** Bug 2494996 has been marked as a duplicate of this bug. ***
How does this not duplicate Bug 2494016?
They are duplicates, but both are added to the advisory and it won't make any difference to deduplicate them in ON_QA phase
(In reply to Michal Hlavinka from comment #6) > Once it posted the comment #4 it was ready. The issue you have (I guess) is > that you are trying to update to Fedora 44, so you are still on Fedora 43, > right? That is correct. I am on 43 right now and trying to upgrade to 44 > The fix has to happen in Fedora 44 repository, so when you try to > update on your system - Fedora 43, it does not find anything, as there isn't > anything. There are two options - A) if your upgraded method allows it, you > can enable/add F44 updates testing repository BUT you will get all testing > updates, which can cause a problem if there is currently some bad update > being tested, or option I am just using the Discover app to do the upgrade. I know enough how to add stuff with dnf, but would have to look for an upgrade to OS method for the command line. Question: why would a fix for Fedora 44 update be unavailable in an older version? If I had 44 then I would not be trying to update to 44. > B) wait for the change to land in regular updates repository (this bug will close) and test again. Likely will have to wait > Also, there is option C) as Fedora 43 was released with gpgme 1.24.3, there > should only a few packages that require gpgme2, so you can try to uninstall > gpgme2 which will probably want to uninstall some other packages. CHECK what > dnf will want to uninstall as well and if that is reasonable. Update system > to F44 and reinstall those packages back. There are 43 packages that will be removed. They all appear to be part of the fedora set of libraries and applications. Like akregator which I did not install or use, But with 43 this seems like a lot. I have no idea why all of these apps latched on to gpgme2 or where it came from. Why would this library fork into 2 different installations? Thanks
FEDORA-2026-4af373d015 (gpgme-2.0.1-5.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
> > B) wait for the change to land in regular updates repository (this bug will close) and test again. > Likely will have to wait it should be available in updates repository, so you can give it a try now. As bodhi gathers feedback for updates, but it was basically (almost) impossible to test before it landed in updates repo, please let me know (or anyone else who had this issue) whether it works now. > There are 43 packages that will be removed. They all appear to be part of > the fedora set of libraries and applications. Like akregator which I did > not install or use, But with 43 this seems like a lot. yeah, that seems a lot for this type of approach if you are not familiar with all of them > I have no idea why > all of these apps latched on to gpgme2 or where it came from. Why would > this library fork into 2 different installations? I don't know, I did not do that and nobody contacted me about it either. Anyway, as one of the listed conflicts was qgpgme and your list of dependencies to remove includes akregator, I guess that some KDE apps needed it, just weird that it happened after F43 release.
(In reply to Michal Hlavinka from comment #12) Thanks for the help and the quick resolution. Much better this time than the wine issue from 42->43 which ended with having to re-build my wine app setups. The install went fine.