Red Hat Bugzilla – Bug 35176
While reading the package, an internal error occurred.
Last modified: 2007-04-18 12:32:36 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows 98)
After downloading linux 7.0 from RedHat FTP site, I made the boot
diskette, using the boot image and rawrite from the site. However, when I
started installation, after creating a user account, an internal error
occured during the process of reading the package.
Steps to Reproduce:
1. Boot from a floppy, or start installation using autoboot.bat
<Then the rest didn't matter much, because I tried using different options
and different partitioning methods, ranging from using PartitionMagic to
make Linux partitions to letting Druid create the partitions>
Actual Results: Same exact error for maybe 4~5 times.
The Error Message:
Traceback (innermost last):
File "/usr/bin/anaconda.real", line 438, in ?
intf.run(todo, test = test)
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 1030, in
line 33, in __call__
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 539, in
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/harddrive.py", line 43,
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/comps.py", line 459, in
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/comps.py", line 428, in
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/comps.py", line 101, in
Local variables in innermost frame:
self: <comps.HeaderList instance at 824e7b8>
Since this is a hard drive install, how did you do the download? Did you
download the iso images to your hard drive and then do an install? Also, are
you sure that you did the download in binary format? This bug looks similar to
bug #21675 and bug #18019.
I'm experiencing the same problem..... The response listings to the availiable
anaconda patch show the true extent of this problem.... there are many users
who have downloaded the RPMS and base files from FTP servers and had the same
subsequent error when trying to install....
The anaconda fix update simply doesn't seem to work...
*** This bug has been marked as a duplicate of 18019 ***