Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 486566 - Yum obsoletes processing does not work when the obsoleting package is already installed
Summary: Yum obsoletes processing does not work when the obsoleting package is already...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F11Target
TreeView+ depends on / blocked
 
Reported: 2009-02-20 11:10 UTC by Nicolas Mailhot
Modified: 2014-01-21 23:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-02-24 02:04:48 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Nicolas Mailhot 2009-02-20 11:10:04 UTC 
Since rpm sadly allows the installation of an obsoleted package on a system that already includes the stuff obsoleting it (bug #486565), this situation needs to be handled by yum.

Unfortunately since the obsoleting package is already installed on system yum does not see the obsoleted package should be garbage collected and leaves it installed.

This should be fixed
yum-3.2.21-9.fc11.noarch
Comment 1 seth vidal 2009-02-20 13:25:18 UTC 
How did the obsoleted pkg get installed?
Comment 2 Nicolas Mailhot 2009-02-22 18:12:28 UTC 
This is bug #486565 rpm lets users install already obsoleted packages with rpm -Uvh without complaining at all
Comment 3 James Antill 2009-02-22 20:17:42 UTC 
Last I checked it worked on each update Eg.

1. pkgA obsoletes pkgB
2a. pkgA installed
2b. thus. pkgB removed
3. pkgB installed (yum localinstall will do this as well as rpm)
4a. pkgA updates
4b. thus. pkgB removed again

...if you are suggesting that 4b should happen without 4a, then I have to disagree. Also if you want conflict+obsoletes then do conflict+obsoletes.
Comment 4 Nicolas Mailhot 2009-02-22 20:48:16 UTC 
It works that way

1. pkgA obsoletes pkgB
2. pkgA installed
3. pkgB installed via rpm (user following an howto, package available on local disk, whatever)
4. yum update. yum sees pkgA installed, does not processes its obsolete info, and pkgB is never garbage collected
5. user complains his system is broken; investigation shows pkgB interferes with pkgA, and pkgA's maintainer relied on the package management tools to get rid of pkgB when pkgA is installed

Waitin for a pkgA update is no help as in can happen months/years later
Comment 5 James Antill 2009-02-24 02:04:48 UTC 
Which is what I said.

If pkgA _conflicts_ with pkgB as well as obsoleting it, then the specfile should say that. If rpm is changed to "auto conflict" on obsolete, then we'll make changes to yum to conform to that new world view ... until then, NoB.
Note You need to log in before you can comment on or make changes to this bug.