Bug 2413794 - Trying to update to Fedora 43, getting error with wine packages
Summary: Trying to update to Fedora 43, getting error with wine packages
Keywords:
Status: CLOSED DUPLICATE of bug 2401666
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: 42
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Michael Cronenworth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-11-10 15:26 UTC by john.p.potter
Modified: 2025-11-10 15:38 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-11-10 15:38:59 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description john.p.potter 2025-11-10 15:26:23 UTC
<html>Internal error:<br/><br/>Error running transaction: 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
file /usr/lib/wine/i386-windows/ddraw.dll conflicts between attempted installs of wine-core-10.15-1.fc43.i686 and wine-core-10.15-1.fc43.x86_64
file /usr/lib/wine/i386-windows/urlmon.dll conflicts between attempted installs of wine-core-10.15-1.fc43.i686 and wine-core-10.15-1.fc43.x86_64
file /usr/lib/wine/i386-windows/windows.devices.bluetooth.dll conflicts between attempted installs of wine-core-10.15-1.fc43.i686 and wine-core-10.15-1.fc43.x86_64
file /usr/lib/wine/i386-windows/wined3d.dll conflicts between attempted installs of wine-core-10.15-1.fc43.i686 and wine-core-10.15-1.fc43.x86_64
file /usr/lib/wine/i386-windows/winmm.dll conflicts between attempted installs of wine-core-10.15-1.fc43.i686 and wine-core-10.15-1.fc43.x86_64</html>

Reproducible: Always

Steps to Reproduce:
1. Click "Update to Fedora 43"

Actual Results:
I get the error in summary

Expected Results:
It should update wine as part of the fedora 43 upgrade

Comment 1 Michael Cronenworth 2025-11-10 15:38:59 UTC

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


Note You need to log in before you can comment on or make changes to this bug.