Description of problem: During a Fedora system upgrade from Fedora 42 to Fedora 43 using dnf system-upgrade (dnf5 offline upgrade), the transaction fails due to file-level conflicts between wine-core.i686 and wine-core.x86_64. This happens even on a Fedora-only system (no WineHQ, no third-party Wine repos), with both architectures of Wine installed. The conflict is not a dependency resolution issue, but a hard RPM file ownership conflict. Environment System upgraded incrementally up to Fedora 42 Upgrade attempt: Fedora 42 → Fedora 43 Architecture: x86_64 with multilib enabled Wine packages: Fedora repositories only No WineHQ repository has ever been enabled on this system Version-Release number of selected component (if applicable): wine 10-20.2.fc43 How reproducible: Always Steps to Reproduce On Fedora 42, install Wine multilib: (on my system it was installed long time ago, and working ok) sudo dnf install wine wine-core.i686 wine-core.x86_64 Start system upgrade: sudo dnf system-upgrade download --releasever=43 --allowerasing sudo dnf system-upgrade reboot During the offline upgrade transaction, DNF aborts with file conflict errors. Observed Results The offline transaction fails with errors similar to: file /usr/lib/wine/i386-windows/urlmon.dll from install of wine-core-10.20-2.fc43.i686 conflicts with file from package wine-core-10.20-2.fc43.x86_64 file /usr/lib/wine/i386-windows/windows.devices.bluetooth.dll from install of wine-core-10.20-2.fc43.i686 conflicts with file from package wine-core-10.20-2.fc43.x86_64 file /usr/lib/wine/i386-windows/wined3d.dll from install of wine-core-10.20-2.fc43.i686 conflicts with file from package wine-core-10.20-2.fc43.x86_64 Both RPMs attempt to install identical paths under: /usr/lib/wine/i386-windows/ Actual results: dnf system-upgrade aborts in testing offline transaction stage Expected results: Wine multilib packages (wine-core.i686 and wine-core.x86_64) should be installable together without file conflicts, as in previous Fedora releases. Additional info: As a temporary solution, I locked wine version with: dnf versionlock add wine\* and retried upgrade successfully Wehen bug is fixed, I will unlock version and try system update
*** This bug has been marked as a duplicate of bug 2401666 ***