Bug 1717218 - inappropriate i686 package conflicts with x86_64
Summary: inappropriate i686 package conflicts with x86_64
Keywords:
Status: CLOSED DUPLICATE of bug 1653683
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 30
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: rpm-software-management
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-04 22:57 UTC by Dr M C Nelson
Modified: 2019-06-05 08:32 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-05 08:32:08 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Output from dnf install wine, including errors (30.60 KB, text/plain)
2019-06-04 22:57 UTC, Dr M C Nelson
no flags Details

Description Dr M C Nelson 2019-06-04 22:57:59 UTC
Created attachment 1577357 [details]
Output from dnf install wine, including errors

Description of problem:

While attempting to update a F30 system, a large number of conflicts were reported between i686 and x86_64 versions of libraries, programs and even man pages.

After removing *i686, the update succeeds.  Then on attempting to reinstall wine, the conflicts appear again.

Version-Release number of selected component (if applicable):


How reproducible:
100% on my laptop.  Not encountered on my desktops.


Steps to Reproduce:
1. dnf update --refresh
2.
3.

Or,

1.  dnf remove *i686
2.  dnf update --refresh
3.  dnf install wine

Actual results:
Reports i686 x86_64 conflicts


Expected results:
Should update and/or install the packages as commanded.


Additional info:

Comment 1 Panu Matilainen 2019-06-05 08:32:08 UTC
The file conflicts are real, but the issue is that they come from attempting to parallel-install i686 and x86_64 variants that with different version. It can happen when mirrors are out of sync and other phase-of-moon issues. Yum had a protection against this but dnf doesn't -> dupe of bug 1653683.

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


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