[Lustre-discuss] NAME field in lustre-client rpms

Michael Sternberg sternberg at anl.gov
Thu Apr 23 10:18:22 PDT 2009


I was trying to install a patchless client of lustre-1.6.7.1 on  
RHEL-5.3 from a local yum repository and noticed an oddity with the  
rpm metadata:  the NAME fields of the "lustre-client" rpms are the  
same as in the patched-kernel rpms.  I looked back at all the versions  
I've used (1.6.x), and saw that this has always been the case there,  
so apparently that's by design, e.g.:

   lustre-1.6.7.1-2.6.18_92.1.17.el5_lustre.1.6.7.1smp.x86_64.rpm
   lustre-modules-1.6.7.1-2.6.18_92.1.17.el5_lustre. 
1.6.7.1smp.x86_64.rpm
vs.
   lustre-client-1.6.7.1-2.6.18_92.1.17.el5_lustre.1.6.7.1smp.x86_64.rpm
   lustre-client-modules-1.6.7.1-2.6.18_92.1.17.el5_lustre. 
1.6.7.1smp.x86_64.rpm

# rpm -qip lustre-[1mc]*rpm  | grep Name
Name        : lustre                       Relocations: (not  
relocatable)
Name        : lustre                       Relocations: (not  
relocatable)
Name        : lustre-modules               Relocations: (not  
relocatable)
Name        : lustre-modules               Relocations: (not  
relocatable)

This means that the patched and patchless rpms collide in a yum  
repository, and only one will be available for installation (the last  
by collation, I believe).

This is the first time I've tried to use the patchless client.   
However, I've put it on the back burner (since there is no support yet  
for the RHEL-5.3 kernel) and pulled it out of my yum repo.

Still, how could one serve both the patched and patchless lustre rpms  
out of the same yum repository?


Regards, Michael



More information about the lustre-discuss mailing list