Details
-
Bug
-
Resolution: Incomplete
-
Major
-
None
-
Lustre 2.4.0
-
None
-
RHEL 6.4
-
1
-
9711
Description
lustre-client-modules-2.4.0-2.6.32_358.6.2.el6.x86_64_gd3f91c4.x86_64.rpm
has a kernel requirement -
Requires: kernel = 2.6.32-358.6.2.el6
If installed via yum, yum always resolves the dependency with the debug kernel.
lustre-client-modules-2.4.0-2.6.32_358.6.2.el6.x86_64_gd3f91c4.x86_64 requires: kernel = 2.6.32-358.6.2.el6
--> Processing Dependency: kernel = 2.6.32-358.6.2.el6 for package: lustre-client-modules-2.4.0-2.6.32_358.6. 2.el6.x86_64_gd3f91c4.x86_64
Searching pkgSack for dep: kernel
Building updates object
up:simple updates time: 0.304
up:obs time: 0.006
up:condense time: 0.000
updates time: 3.922
TSINFO: Marking kernel-debug-2.6.32-358.6.2.el6.x86_64 as install for lustre-client-modules-2.4.0-2.6.32_358. 6.2.el6.x86_64_gd3f91c4.x86_64
--> Running transaction check
---> Package kernel-debug.x86_64 0:2.6.32-358.6.2.el6 will be installed
This is a bug in yum or rpm I think. I made a simple rpm package that just requires a kernel and it does the same thing. I played with the spec file but couldn't figure out a way to work around this with an rpm.
It is not a huge deal, but we have to work around it for automated installs.