I got exactly this once I’d already upgraded to Fedora 30.
Every time dnf wanted to upgrade a kernel, I got this message. Note that it’s the DELETION of the OLDEST kernel that’s the problem and the oldest kernel that dnf shows in its ‘conflicting request’ message
The only way round it that I’ve found is to use ‘rpm -e’ to erase the offending kernel packages. The recommended way is to use dnf for everything, but trying to remove these kernels via dnf, I still had dnf barf on me, even when I tried ‘dnf remove’.
Anyway ‘rpm -e’ should’t really be a problem since it’s a kernel that dnf would remove anyway in this transaction if it didn’t barf.
Thanks to both thomaswood and jonathans for their help. That got me to the next step - but also to another error when I run “dnf upgrade --refresh” . It downloads over 500 package/updates and then ends with this:
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction check error:
file /usr/share/doc/libjpeg-turbo/ChangeLog.md from install of libjpeg-turbo-2.0.2-1.fc29.i686 conflicts with file from package libjpeg-turbo-2.0.0-3.fc29.x86_64
file /usr/share/licenses/libjpeg-turbo/LICENSE.md from install of libjpeg-turbo-2.0.2-1.fc29.i686 conflicts with file from package libjpeg-turbo-2.0.0-3.fc29.x86_64
file /usr/share/man/man5/ldap.conf.5.gz from install of openldap-2.4.46-10.fc29.i686 conflicts with file from package openldap-2.4.46-9.fc29.x86_64
Not sure if I should open a new problem or not.
Hi @rjfedora: welcome to the community! Please take a look at the introductory posts in #start-here if you haven’t yet had a chance to do so. They have useful information on how to use Discourse to have the best experience (for you and others).
These appear to be package conflicts between the 32bit packages and the 64bit ones that need to be installed as upgrades. The simple workaround is to remove the conflicting packages, upgrade, and re-install them if you do need them.
Out of curiosity: you have 32 bit packages installed on your 64 bit system? Did you install these?
Thanx for the prompt response. I did not knowingly install 32bit packages. But from the way the error reads it looks like the packages that are trying to install are the 32bit packages (i686 are 32bit correct?) or am I reading it wrong?
I expect they will—if they’re causing trouble with normal updates, they’ll probably also cause trouble with a system-upgrade. A system-upgrade is essentially a normal update but in a fresh, pristine boot.
What does trying to remove these two packages say? Does it also try to remove lots of other packages?
Those are the two packages that the update is trying to install. The packages currently in the system are the 64-bit packages :
In fact there were a number of *.i686 packages that were installed with the upgrade, but these were the only ones with conflicts. I guess the only thing to do is remove the 64 bit versions and replace them with the i686 versions, though that seems odd.
64 bit libraries cannot be updated with their 32 bit counterparts, and DNF will not suggest so.
No, I’d say removing the i686 ones is preferable. You are on a 64 bit system so all the core libraries will be x86_64. A few tools that you’ve installed may have pulled in i686 libraries, but these will be optional. In general, you should be able to remove all i686 packages and your system should still function properly.
You shouldn’t have two 64 bit versions of the package installed.
Same for this one.
No, not yet. We may have caught the actual issue here—these duplicate packages should not be here and are likely what is causing the problem. Did an upgrade fail at some point? This suggests that the transaction didn’t complete properly.
Had similar issue on a centos server recently, with several conflicts & duplications after a failed update. Removing entries from the rpm database resolved the issue for me, this doesn’t actually uninstall anything. I suggest trying the following:
That’ll be the way to go now. We do try to avoid it as much as possible, since it is hard to say if it’s only a stray entry in the database. That depends on what stage of the transaction the update failed.
Please emove, reinstall, attempt upgrade, and let us know how that goes.
I would pay more attention to critical system tasks such as upgrades
SUCCESS!!! Thanks to @tjdoyle and especially @FranciscoD or all the help and time spent!
I did the remove and reinstall as suggested and then ran dnf check-update which showed a problem with the i686 versions of those packages, so I did the exact same with the i686 versions of openldap and libjpeg-turbo (remove and reinstall) and then ran the system-upgrade and all worked fine. Sorry it took me so long to get back today, but I had a bunch of prior commitments. R.J.