[Rpm-maint] [RFC/PATCH] comparisons without release

[Michael Schroeder]

On Fri, Nov 26, 2010 at 06:42:59PM +0100, Michael Schroeder wrote:
> On Mon, Aug 09, 2010 at 06:43:18PM +0300, Anssi Hannula wrote:
> > Currently [1], if a package has
> > Provides: foo = 1.2
> > And another package has
> > Conflicts: foo < 1.2-1
> > 
> > The conflict does not trigger, as the releases will be ignored if one of the 
> > compared EVRs does not have it. (mdv bug #55810 [2])
> > 
> > Another similar case is:
> > A: Provides: foo = 1.2
> > B: Requires: foo = 1.2-2  (or >= 1.2-2)
> > The provides will match, which it IMHO should not be doing.
> 
> Most people think that "Provides: foo = 1.2" means that the
> package provides all releases of foo, thus it should match.
> Works good for Requires, doesn't work that well for Conflicts.

Having said that, the current behaviour seems to be quite broken.
Please explain the following:

    Provides: foo > 1.2-1
    Requires: foo = 1.2      no match

    Provides: foo >= 1.2-1
    Requires: foo = 1.2      matches

I think the attached patch (completely untested) may fix the issue,
but I'll have to it through some tests on Monday.

Cheers,
  Michael.

-- 
Michael Schroeder                                   mls at suse.de
SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rpm-emptyrelese.diff
Type: text/x-patch
Size: 750 bytes
Desc: not available
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20101126/e11ef673/attachment.bin>