Red Hat Bugzilla – Bug 22561
Traceback : "IndexError: list index out of range"
Last modified: 2007-04-18 12:30:16 EDT
Here's the full body of the saved file:
Traceback (innermost last):
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/iw/progress_gui.py", line 20, in run
rc = self.todo.doInstall ()
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1480, in doInstall
if self.method.systemMounted (self.fstab, self.instPath, self.hdList.selected()):
File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/image.py", line 46, in systemMounted
self.loopbackFile = mntPoint + fstab.filesystemSpace(mntPoint) + \
IndexError: list index out of range
Local variables in innermost frame:
fstab: <fstab.GuiFstab instance at 84baed0>
selected: [ImageMagick, LPRng, MAKEDEV, Mesa, Mesa-devel, ORBit, ORBit-devel, SDL, SDL-devel, SDL_image, SDL_image-devel,
SysVinit, WindowMaker, WindowMaker-libs, XFree86, XFree86-75dpi-fonts, XFree86-devel, XFree86-doc, XFree86-libs, XFree86-tools,
XFree86-twm, XFree86-xdm, XFree86-xfs, Xaw3d, Xaw3d-devel, Xconfigurator, anacron, anonftp, apache, apache-devel, apache-manual, apmd,
arpwatch, ash, asp2php, asp2php-gtk, aspell, at, audiofile, audiofile-devel, aumix, authconfig, autoconf, automake, autorun, awesfx,
basesystem, bash, bash-doc, bc, bdflush, bind, bind-utils, binutils, bison, bug-buddy, byacc, bzip2, bzip2-devel, caching-nameserver,
cdda2wav, cdecl, cdp, cdparanoia, cdrecord, chkconfig, chkfontpath, cleanfeed, compat-egcs, compat-egcs-c++, compat-glibc,
compat-libstdc++, console-tools, control-center, control-center-devel, control-panel, cpio, cpp, cproto, cracklib, cracklib-dicts, crontabs
What am I doing wrong? Is there a component I shouldn't install or is it just my version that's been corrupted?
*** This bug has been marked as a duplicate of 19928 ***
This problem occurs when performing a partitionless install that requires at
least one package from the 2nd cd ... we are working to find a fix for it ...
thanks for your report! :)
*** This bug has been marked as a duplicate of 19523 ***
An updates disk is available which fixes this -- for details, see bug 19523 (the
same disk fixes both this but and that one).