[Yum-devel] [PATCH 1/2] make sure obsoletes are looked up for localinstall/updated pkgs this handles the cases where the localpkg is a proper update AND an obsolete for a different installed pkg.

[Seth Vidal]

On Wed, 12 Aug 2009, Seth Vidal wrote:

>
>
> On Tue, 11 Aug 2009, James Antill wrote:
>
>> 
>> 
>> I agree this "works", however the problem is that we rely on the
>> obsoletes data which is built up before we do anything based on looking
>> at just what is in the repos. So if we have local pkgs:
>> 
>> pkg-new-A
>> pkgA
>> 
>> ...and pkg-new-A obs pkgA, then doing either of:
>> 
>> yum install pkgA.rpm pkg-new-A.rpm
>> yum install pkg-new-A.rpm pkgA.rpm
>> 
>
> But installing pkg-A and pkg-new-A can be completely consistent and not 
> conflicting at all. Especially from local pkgs.
>
> A comment is fine but I'm not going to chase down a bunch of rabbit holes 
> unless we have a case where this is unhappy.

Commented and I also tested the above with rpm and obsoleting (but not 
conflicting) packages. both pkgs get installed with rpm -Uvh - the 
obsoleting one alone isn't installed. I found that curious.

I'll post new patches of both.

-sv