Bug 2411704

Summary: Installer of Fedora 43 - Package Collisions on install
Product: [Fedora] Fedora Reporter: Jaroslav Fišer <fiser.jarda>
Component: wineAssignee: Michael Cronenworth <mike>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 42CC: besser82, mike, suraj.ghimire7
Target Milestone: ---Keywords: Upgrades
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-11-02 18:42:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jaroslav Fišer 2025-11-01 07:07:21 UTC
<html>Vnitřní chyba:<br/><br/>Chyba při provádění transakce: soubor /usr/lib64/wine/i386-windows z instalace wine-core-10.15-1.fc43.x86_64 koliduje se souborem z balíčku wine-core-10.15-1.fc42.x86_64
soubor /usr/lib/wine/i386-windows/ddraw.dll způsobuje konflikt mezi instalovaným wine-core-10.15-1.fc43.i686 a wine-core-10.15-1.fc43.x86_64
soubor /usr/lib/wine/i386-windows/urlmon.dll způsobuje konflikt mezi instalovaným wine-core-10.15-1.fc43.i686 a wine-core-10.15-1.fc43.x86_64
soubor /usr/lib/wine/i386-windows/windows.devices.bluetooth.dll způsobuje konflikt mezi instalovaným wine-core-10.15-1.fc43.i686 a wine-core-10.15-1.fc43.x86_64
soubor /usr/lib/wine/i386-windows/wined3d.dll způsobuje konflikt mezi instalovaným wine-core-10.15-1.fc43.i686 a wine-core-10.15-1.fc43.x86_64
soubor /usr/lib/wine/i386-windows/winmm.dll způsobuje konflikt mezi instalovaným wine-core-10.15-1.fc43.i686 a wine-core-10.15-1.fc43.x86_64</html>

Reproducible: Always

Steps to Reproduce:
1. Try to install Fedora 43 from last Fedora 42
2.
3.
Actual Results:
It will end up with an error during installation of Fedora 43 and will not finish it

Expected Results:
Fedora 42 is updated to Fedora 43

Comment 1 Michael Cronenworth 2025-11-02 18:42:40 UTC

*** This bug has been marked as a duplicate of bug 2401666 ***