On Tuesday 14 July 2009 15:48, Troy Dawson wrote:
> 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.

The problem is not related to the epoch. It occurs as soon as you install a 
kernel module via rpm which is 
1) not in any repository (with the version you installed via rpm) 
2) but have an older version in some repository.
3) and then run "yum upgrade"

Another possibility to run into the same problem is:
1) We have kernel module foo with version 1.42 in repository A and with 
version 0.42 in repository B. 
2) We install the kernel module via yum. Version 1.42 will be installed.
3) We remove version 1.42 from repository A - for some reason.
4) We run "yum upgrade". Now the kernel-plugin of yum wants to install version 
0.42, but 1.42 is already installed!

Achim
--
Paul Scherrer Institut; Villigen; Schweiz
Allgemeine Informationstechnologie (AIT)