Problem
Due to packaging problems, attempts to upgrade a system with wine packages installed to Fedora 43 will likely fail to proceed.
The issue is related to wine-core and the error will likely look similar to this:
Transaction failed: Rpm transaction failed.
– file /usr/lib64/wine/i386-windows from install of wine-core-10.15-1.fc43.x86_64 conflicts with file from package wine-core-10.15-1.fc42.x86_64
Note: You might also encounter another issue related to wine-dxvk with an error similar to this:
Problem 1: wine-dxvk-2.6.2-1.fc42.i686 from System has inferior architecture
– wine-dxvk-2.6.2-1.fc42.x86_64 does not belong to a distupgrade repository
– problem with installed package
Cause
This is caused by a failure to properly package some additional files that appeared in recent versions of wine in such a way as to maintain the ability to have both 32-bit and 64-bit wine installed together. See this comment.
Related Issues
Bugzilla report: #2401666
Workarounds
The wine-core issue should now be resolved and fixes were pushed to Fedora 43 updates repository. You can upgrade your Fedora 41/42 system as usual, and you should no longer encounter this issue.
If you have wine-dxvk installed, you might still encounter broken dependencies and might need to use the workaround.
The usual approach of using the --allowerasing flag for DNF system upgrade might not help in this case. You’ll need to remove the affected package temporarily, perform the upgrade, and then install it again.
For wine-dxvk, you can remove it and all its subpackages with:
$ sudo dnf remove 'wine-dxvk*'
Read the output properly to see whether this also removes some application that you care about, which might be dependent on Wine (e.g. some configuration utility or a GUI manager).
After removing the affected wine packages, perform the system upgrade as usual. Once that is done, you can install the wine packages again (and some additional tools that were also removed previously, if applicable).
If removing just wine-dxvk* is not sufficient, you can repeat the process also with wine*.
Note: All your existing windows programs will be kept intact, because they are stored in your home directory, and RPM packages don’t touch your home directory. Once you install wine (+ possibly related tools) again, all your windows programs will be accessible again.
IMPORTANT NOTE: an alternative workaround involving deleting some symlinks was suggested, but testing indicates that it can result in the upgrade process crashing part-way through, leaving a broken system. Please DO NOT FOLLOW any suggestions to work around this issue by deleting symlink files. Please use the above workaround instead.