Bug 85963 - Certain packages, e.g. alsa-driver, installer crash
Certain packages, e.g. alsa-driver, installer crash
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2003-03-11 11:33 EST by Toralf
Modified: 2007-04-18 12:51 EDT (History)
0 users

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

Attachments (Terms of Use)
Anaconda dump from failed install (76.36 KB, text/plain)
2003-03-11 11:34 EST, Toralf
no flags Details

  None (edit)
Description Toralf 2003-03-11 11:33:27 EST
Description of problem:
Installer exits with key error for some non-standard packages on my customised 
install source. Behavuour in a similar to the one I get when a package is
mentioned in "comps", but missing from "hdlist", but in this case, however, I
_know_ that the packages are included. However, it looks all the packages in
question have rather complex names, versions or release numbers. One example is
alsa-driver from freshrpms.net; version-release is 0.9.0-fr0rc6.1

How reproducible:
Every time

Steps to Reproduce:
1. Copy Red Hat CDs to location suitable for network install
2. Download alsa-driver-0.9.0-fr0rc6.1 from freshrpms, copy to install location
3. Add alsa-driver to RedHat/base/comps, update hdlist using genhdlist
4. Start network install with new location as source
Actual results:
Installer crash

Expected results:
Install starts
Comment 1 Toralf 2003-03-11 11:34:10 EST
Created attachment 90554 [details]
Anaconda dump from failed install
Comment 2 Jeremy Katz 2003-03-11 12:33:09 EST
Either the package name isn't what you think it is or it's not in the hdlist. 
That is the *only* way you can get this.

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