Selecting 'upgrade system' (on a disk containing a debian potato
installation) gives the python traceback:
Traceback (innermost last):
File "/usr/lib/anaconda/gui.py" line 176 in run
File "/usr/lib/python1.5/site-packages/gtk.py", line 2538 in mainloop
File "/usr/lib/python1.5/site-packages/gtk.py", line 125 in __call__
ret = apply(self.func, a)
File "/usr/lib/anaconda/gui.py", line 408, in nextClicked
next = self.currentScreen.getNext()
File "/usr/lib/anaconda/iw/examine_gui.py", line 21, in getNext
File "/usr/lib/anaconda/todo.py", line 771, in upgradeFindPackages
File "/usr/lib/anaconda/fstab.py", line 913, in readFstab
if fields == "#" and fields[0:4] == "LOOP":
IndexError: list index out of range
After clicking OK in the python traceback dialog, the system reboots (it
should get back to the upgrade/install selection, no ?).
The fstab in question contains:
# /etc/fstab: static filesystem information.
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/hda2 / ext2 defaults,errors=remount-ro 0 1
/dev/hda1 none swap sw 0 0
proc /proc proc defaults 0 0
/dev/fd0 /floppy auto defaults,user,noauto 0 0
/dev/cdrom /cdrom iso9660 defaults,ro,user,noauto 0 0
Does this behavior still happen with Pinstripe (beta-5)?
Please reopen if you continue to have problems.
Sorry to say that this is not fixed in RC1.
The error is not the same though:
I boot with 'linux updates', choose 'upgrade an existing system', and the
the steps 'finding a previous RedHat installation' and gives up when 'finding
to upgrade' with a 'Rebuild of RPM database failed. You may be out of disk
is false, btw).
I can also see a partial error on the blue screen behind the dialog box saying
The debian system is the same as in the original bug report.
It doesn't have /etc/redhat-release, right?
No, it has a /etc/debian-release instead :)