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
How did the obsoleted pkg get installed?
This is bug #486565 rpm lets users install already obsoleted packages with rpm -Uvh without complaining at all
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.
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
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.