Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 8124 - "Exception Error" occurs during HD based installation
Summary: "Exception Error" occurs during HD based installation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 6.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jay Turner
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-01-03 03:43 UTC by mike11117
Modified: 2015-01-07 23:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-01-03 16:09:11 UTC


Attachments (Terms of Use)

Description mike11117 2000-01-03 03:43:40 UTC
I have tried to install redhat 6.1 three times, twice using the entire
downloadable redhat i386 directory located on ftp mirror sites, the third
using the downloadable ISO image (mounted the ISO image under linux and
copied it to my DOS hard drive to ensure that all proper files were
present).
All three times, I have experienced a dialog with the title "Exception
Occurred" whose main body contains the following message (at the bottom):
"TypeError: unsubscriptable object" in reference to line 50 of "comps.py"
...this is after configuring the installation and after the program begins
to read packages from the install directory.

Comment 1 Jay Turner 2000-01-03 16:09:59 UTC
The most common cause of this error message that you are getting is that there
is a file in the RedHat/RPMS directory which is not actually a .rpm file.
Change into that directory and run "ls | grep -v rpm"  If you get a list of any
files (which I am expecting that you will) delete them and you should be able to
continue with the installation.  Please reopen this bug if you are still having
problems after following these directions.


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