Bug 1669061 - 'dnf-yum' package conflicts with 'yum'
Summary: 'dnf-yum' package conflicts with 'yum'
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Mracek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1615055 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-24 08:47 UTC by Pavel Raiskup
Modified: 2019-07-30 15:09 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-30 15:09:33 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Pavel Raiskup 2019-01-24 08:47:42 UTC
This is new problem on F30 because on F29 it seems to be fine:

    $ rpm -q dnf dnf-yum yum
    dnf-4.0.9-2.fc29.noarch
    dnf-yum-4.0.9-2.fc29.noarch
    yum-3.4.3-518.fc29.noarch

But on Fedora 30:
    # dnf install dnf-yum
    Last metadata expiration check: 0:04:22 ago on Thu 24 Jan 2019 03:42:19 AM
    Error: 
     Problem: problem with installed package yum-3.4.3-518.fc29.noarch
      - package dnf-yum-4.0.10-1.fc30.noarch conflicts with yum provided by
        yum-3.4.3-518.fc29.noarch
      - conflicting requests

I'm not sure what package is broken, but since yum doesn't seem to be changed
(nor rebuilt for f30), I guess this is caused by some change in dnf-yum.

Comment 1 Michal Domonkos 2019-01-28 14:38:30 UTC
This can either be resolved by a change similar to https://github.com/rpm-software-management/dnf/pull/1209, or by dropping YUM-3.  We strongly prefer the latter:

https://pagure.io/koji/issue/1214

Comment 2 Michal Domonkos 2019-01-28 14:38:54 UTC
*** Bug 1615055 has been marked as a duplicate of this bug. ***

Comment 3 Michal Domonkos 2019-01-28 14:58:05 UTC
(In reply to Michal Domonkos from comment #1)
> https://pagure.io/koji/issue/1214

Correction:
https://pagure.io/fesco/issue/2064

Comment 5 Jaroslav Mracek 2019-07-30 15:09:33 UTC
The problem is already resolved with dnf-4.2.5


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