Bug 472951 - Driver Update Disk Format Change for RHEL5.3 (allow renamed packages)
Driver Update Disk Format Change for RHEL5.3 (allow renamed packages)
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
high Severity high
: rc
: ---
Assigned To: Chris Lumens
Release Test Team
Depends On:
  Show dependency treegraph
Reported: 2008-11-25 14:17 EST by Jon Masters
Modified: 2009-01-20 16:33 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-20 16:33:12 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jon Masters 2008-11-25 14:17:17 EST
Description of problem:

Previous releases of RHEL5 have required that the Driver Update disk contain RPMs wherein the name matches kmod-$driver_name-$kernel_variant (for appropriate values of $driver_name exactly matching the ".ko" file, and the kernel variant being one of the standard RHEL5.X supported Enterprise kernels). We require, however, to support arbitrary names with the right dependencies being used to resolve the name that should be selected at install time.

A trivial patch exists, which is under test at the moment. This needs to make 5.3 and has previously been discussed by the installer team, myself, Daniel Riek, and numerous others. It's been worked on but didn't have a BZ to track it formally.

Comment 3 Chris Lumens 2008-11-25 16:15:29 EST
This should be fixed in anaconda-
Comment 8 errata-xmlrpc 2009-01-20 16:33:12 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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