Bug 985944 - Yum does not handle conflicts between multiple packages obsoleting the same package
Yum does not handle conflicts between multiple packages obsoleting the same p...
Product: Fedora
Classification: Fedora
Component: yum (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: packaging-team-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-07-18 10:44 EDT by Nicolas Chauvet (kwizart)
Modified: 2015-02-17 11:14 EST (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-17 11:14:17 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
test case (817 bytes, patch)
2013-07-19 06:38 EDT, Zdeněk Pavlas
no flags Details | Diff

  None (edit)
Description Nicolas Chauvet (kwizart) 2013-07-18 10:44:09 EDT
Description of problem:
Yum does not handle conflicts between multiple packages obsoleting the same package

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

How reproducible:

Steps to Reproduce:
1. Enable a repository with package A obsoleted/provided by package B1 B2 and B3
When user already have package B? installed.

Actual results:
All B{1,2,3} packages are installed, package A should be obsoleted.

Expected results:
Only package B? should be installed and package A should be obsoleted.

Additional info:
Initially reported on a external tracker.
Comment 1 Zdeněk Pavlas 2013-07-19 06:38:07 EDT
Created attachment 775747 [details]
test case

Works with N = [1], but fails when N = [1, 2]...
Comment 2 Nicolas Chauvet (kwizart) 2013-07-21 07:11:52 EDT
I'm not sure to understand why the problem still rise when package A is only Obsoleted (not virtually provided). This happen in F-18.
At this time, I understand that Obsoleting/Providing a package has the same effect as only Obsoleting it.

What I would expect is that if package A is installed on a system, with no package B?. And the repository contain package B1 and B2 that Obsoletes package A without providing it, then nothing should change.

Only when users want package B1 or B2, package A will be obsoleted.
Currently, package A is obsoleted even if the capability is only provided by the package itself.

This is not what I expected.
Comment 3 Nicolas Chauvet (kwizart) 2013-07-21 07:37:11 EDT
As just experienced: yum update hit the problem, whereas dnf update not.
This problem may rise in F-17 also (but there is no dnf there to workaround)
Comment 4 Nicolas Chauvet (kwizart) 2014-05-07 05:19:10 EDT
I don't know the status of this issue. 
For now I've dropped the Obsoletes in our package...
Comment 5 Fedora End Of Life 2015-01-09 13:59:34 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2015-02-17 11:14:17 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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