SCIENTIFIC-LINUX-USERS Archives

July 2009

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Gasser Marc <[log in to unmask]>
Reply To:
Gasser Marc <[log in to unmask]>
Date:
Tue, 14 Jul 2009 12:02:01 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
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.

Regards,
Marc

ATOM RSS1 RSS2