Bug 2408857 - will not update to 43
Summary: will not update to 43
Keywords:
Status: CLOSED DUPLICATE of bug 2401666
Alias: None
Product: Fedora
Classification: Fedora
Component: wine
Version: 42
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Michael Cronenworth
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-10-31 14:19 UTC by Jamie Imler
Modified: 2025-10-31 15:51 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-10-31 15:51:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Jamie Imler 2025-10-31 14:19:44 UTC
Description of problem:willnot update to 43kde from 42 kde


Version-Release number of selected component (if applicable):wine-core-10.15-1.fc43.i686


How reproducible:every time i try


Steps to Reproduce:
1.run a update
2.
3.

Actual results:
<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>

Expected results:


Additional info:

Comment 1 Michael Cronenworth 2025-10-31 15:51:10 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.