Gasser Marc wrote:
> Hello SL Users,
> 
> We have for instance the following situation:
> 
> - SL51 host with kernel-2.6.18-53.1.4.el5 (among others)
> 
> - kernel-module-openafs-2.6.18-53.1.4.el5    2    1.4.6    73.slp5
> is installed but removed recently from the update repo.
> 
> - kernel-module-openafs-2.6.18-53.1.4.el5    0    1.4.6    58.SL5
> is still in the sl51base repo, but not installed
> 
> Now, when I am running "yum update" on a SL51 system with the
> kernel kernel-2.6.18-53.1.4.el5 installed, the kernel-module
> plugin (package yum-3.0.6-3.sl) tries to install
> 
>      kernel-module-openafs-2.6.18-53.1.4.el5    0    1.4.6    58.SL5
> from the sl51base repo. Eventually, yum fails with the corresponding
> message "blabla which is newer is already installed".
> 
> Why does the kernel-module plugin
> only check what's the newest version of a kernel module
> in the repo and sets it to be installed,
> regardless if the version installed is newer.
> 

Because we hadn't heard of anyone putting a higher epoch in their 
kernel-modules and then taking them out.
epoch's are dangerous things and must be handled with care.
To be honest, kernel modules are hard enough to get working, if I throw 
in epoch checking, it's going to go over the top and start breaking things.
Right now, the only thing I can say is to take out the kernel module 
with the higher epoch by hand.
Troy
-- 
__________________________________________________
Troy Dawson  [log in to unmask]  (630)840-6468
Fermilab  ComputingDivision/LCSI/CSI LMSS Group
__________________________________________________