Bug 2414760 - Upgrade from 42 to 43 failed due to wine
Summary: Upgrade from 42 to 43 failed due to wine
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-13 04:28 UTC by aurelien.paumier
Modified: 2025-11-13 07:20 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-11-13 07:20:27 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description aurelien.paumier 2025-11-13 04:28:44 UTC 
<html>Erreur interne:<br/><br/>Erreur d’exécution pour la transaction : le fichier /usr/lib64/wine/i386-windows de l&apos;installation de wine-core-10.15-1.fc43.x86_64 entre en conflit avec le fichier du paquet wine-core-10.15-1.fc42.x86_64
le fichier /usr/lib/wine/i386-windows/ddraw.dll entre en conflit avec les tentatives d&apos;installation de wine-core-10.15-1.fc43.i686 et wine-core-10.15-1.fc43.x86_64
le fichier /usr/lib/wine/i386-windows/urlmon.dll entre en conflit avec les tentatives d&apos;installation de wine-core-10.15-1.fc43.i686 et wine-core-10.15-1.fc43.x86_64
le fichier /usr/lib/wine/i386-windows/windows.devices.bluetooth.dll entre en conflit avec les tentatives d&apos;installation de wine-core-10.15-1.fc43.i686 et wine-core-10.15-1.fc43.x86_64
le fichier /usr/lib/wine/i386-windows/wined3d.dll entre en conflit avec les tentatives d&apos;installation de wine-core-10.15-1.fc43.i686 et wine-core-10.15-1.fc43.x86_64
le fichier /usr/lib/wine/i386-windows/winmm.dll entre en conflit avec les tentatives d&apos;installation de wine-core-10.15-1.fc43.i686 et wine-core-10.15-1.fc43.x86_64</html>

Reproducible: Always

Steps to Reproduce:
1.Upgrade dist with Discover
2.
3.
Comment 1 Miroslav Suchý 2025-11-13 07:20:27 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.