Hi all.

As we at CERN were not using yum extensively on SL
until now the following escaped my attention:

With current SL 30X yum while trying to upgrade kernel
and assorted modules this is what happens:

[...]
I will do the following:
[install: kernel-smp 2.4.21-32.0.1.EL.cern.x86_64]
[install: kernel-source 2.4.21-32.0.1.EL.cern.x86_64]
[install: kernel 2.4.21-32.0.1.EL.cern.x86_64]

(I've got previous kernel, kernel-smp, kernel-source
AND matching kernel-module-openafs installed)

Apparently changing:

self.setPkgState(name,arch, '')

to:

self.setPkgState(name,arch, 'i')

in /usr/share/yum/nevral.py (line 336)

fixes the behaviour:

[...]
I will do the following:
[install: kernel-module-openafs-2.4.21-32.0.1.EL.cernsmp 
1.2.11-15.12.SL.x86_64]
[install: kernel-smp 2.4.21-32.0.1.EL.cern.x86_64]
[install: kernel-module-openafs-2.4.21-32.0.1.EL.cern 
1.2.11-15.12.SL.x86_64]
[install: kernel-source 2.4.21-32.0.1.EL.cern.x86_64]
[install: kernel 2.4.21-32.0.1.EL.cern.x86_64]

(yes, kernel-module-XXX packages are built to coexist)

I believe that this is the behaviour expected by users ?

It also seems to me that doing above change would permit
to skip the code just below the mentioned line:

[...]
for (name, arch) in self.NAkeys():
             mo = re.match(km_re,name)
             if mo:
                 modname, kv = mo.group(1,2)
                 if modname in mod_list and kv in 
kernel_version_list.keys() and arch == kernel_version_list[kv]:
                     if self.state(name,arch) != 'u':
                         self.setPkgState(name,arch, 'u')
                         log(4, "Upgrading " + name)
[...]

- the standard upgrade ie:

from kernel-module-openafs-KVER-VER1-REL2 to
      kernel-module-openafs-KVER-VER2-REL2

is handled by standard yum code.

Best Regards

Jarek

__
-------------------------------------------------------
_ Jaroslaw_Polok ___________________ CERN - IT/ADC/LE _
_ http://home.cern.ch/~jpolok ___ tel_+41_22_767_1834 _
_____________________________________ +41_78_792_0795 _