Wacky results from a package comparison

[Chip Seraphine]

On a Mandrake 10.0 box, I am getting some odd test results-- the comparison 
reports the package stanza is satisfied, but then goes and behaves as if the 
test failed.  

The package is a kernel (kernel-p3-smp-64GB-2.6.3.15mdk).  Under Mandrakes 
method of versioning kernel RPMs, every RPM is version '1' .  I am getting 
some improper results from this piece of 'packages:' code:

                # The Linux Kernel compiled with options for pentium III, smp 
                kernel-p3-smp-64GB-2.6.3.15mdk
                  vers=1                        cmp=ge  
elsedefine=needrpm:needrpm_kernel_p3_smp_64GB_2_6_3_15mdk

When run with -v, I get this:

RPMCheckPackage(): Requested kernel-p3-smp-64GB-2.6.3.15mdk ge 1
RPMCheckPackage(): Trying installed version 0:1-1mdk
Comparison result: eq
RPM Package kernel-p3-up-64GB-2.6.3.15mdk not installed.

The first three lines are so far, so good.  The conclusion (not installed even 
though the result was 'eq') is puzzling me.    Other kernel package checks 
work fine, e.g.:

                # The Linux Kernel compiled for SMP machines.
                kernel-smp-2.6.3.15mdk
                  vers=1                        cmp=ge  
elsedefine=needrpm:needrpm_kernel_smp_2_6_3_15mdk

produces:

RPMCheckPackage(): Requested kernel-smp-2.6.3.15mdk ge 1
RPMCheckPackage(): Trying installed version 0:1-1mdk
Comparison result: eq

...with no following 'not installed' line. 

Any ideas?  This isn't really damaging anything, but it is resulting in hosts 
trying (and failing) to install the same RPMs over and over.



-- 

Chip Seraphine
Unix Administrator
TradeLink, LLC
312-264-2048
chip@trdlnk.com