Description of problem:
It has been found that even though lvm2-2.02.01-1.3.RHEL4 requires "kernel >=
2.6.9-24", it can be installed cleanly when only kernel-2.6.9-11.EL is present.

kernel-26.spec explicitly provides "kernel = %{version}". This is not only
unnecessary, but also prevents other packages from requiring a specific kernel
release. From the rpm documentation on dependencies:

    Unspecified epoch and releases are assumed to be zero, and are
    interpreted as "providing all" or "requiring any" value.

So, by explicitly providing "kernel = 2.6.9" in kernel-2.6.9-1, you satisfy any
dependency on, eg: "kernel >= 2.6.9-999". This is clearly bad. 

All packages automatically provide 

    "%{name} = %{epoch}:%{version}-%{release}"

In the case of the kernel, based on the rpm documentation, anything that
requires "kernel = 2.6.9" will be satisfied by the default packaging behavior.
Therefore I see no reason why this line, which AFAICT causes nothing but
confusion/harm should remain. Patch attached.


Version-Release number of selected component (if applicable):
kernel-2.6.9-11.EL

How reproducible:
Always

Steps to Reproduce:
1. get on a system whose latest kernel is 2.6.9-11.EL
2. install lvm2-2.02.01-1.3.RHEL4 (which requires kernel >= 2.6.9-24)
3. 
  
Actual results:
The lvm2 package is installed without flagging the unsatisfied dependency

Expected results:
Installation should fail since kernel-2.6.9-11.EL < kernel-2.6.9-24

Additional info:
There is nothing wrong with lvm2's packaging -- the problem is in the kernel
spec file.