Bug 700920 - [RHEL6] DUP kmod package missing module-init-tools dependency
Summary: [RHEL6] DUP kmod package missing module-init-tools dependency
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: driver-update-program
Version: 6.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jon Masters
QA Contact: Chao Yang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-29 19:40 UTC by Travis Gummels
Modified: 2018-11-14 12:54 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-26 21:29:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Travis Gummels 2011-04-29 19:40:10 UTC
Description of problem:

According to section 2.4.1 of the Driver Update Program manual:

http://people.redhat.com/jcm/el6/dup/docs/dup_book.pdf

you need a handful of packages to build drivers:

• createrepo (required when building Driver Update Disks)
• kabi-whitelists (required as a reference for official kABI)
• kabi-yum-plugins (optional enforcing plugin to mandate kABI)
• kernel-devel (older releases of RHEL had multiple possible kernel ”vari-
ants” such as kernel-xen-devel, but these do not exist in RHEL 6).
• redhat-rpm-config

It appears that if you don't also have module-init-tools installed find-provides.ksym silently fails (so your kmod package doesn't require the kernel bits).

We should probably add module-init-tools to the list of required packages or maybe make it a dependency for kernel-devel or something like that.
Version-Release number of selected component (if applicable):

How reproducible:

Attempt rpmbuild of DUP package on RHEL 6
  
Actual results:

find-provides.ksym silently fails (so your kmod package doesn't require and kernel bits)

Expected results:

No failure.

Additional info:

Comment 1 Jon Masters 2011-05-26 21:29:05 UTC
There should be no way that module-init-tools is not installed, since it is required for basic system operation. The only way it would be missing is if you're building inside a chroot or other environment, which we don't support. You can make it work, in that case, by simply including module-init-tools amongst the other packages you are pulling in.


Note You need to log in before you can comment on or make changes to this bug.