Red Hat Bugzilla – Bug 464301
preupgrade 0.9.3-3.fc7.noarch freezes while downloading installer stage 2
Last modified: 2014-01-21 18:06:12 EST
Description of problem:
I downloaded preupgrade yesterday (26th sepbember 2008) to upgrade my fedora 7 x86_64 System to the latest version. It seems to have downloaded all the necessary packages, but froze when it tried to download installer stage 2... and output an error message.
Version-Release number of selected component (if applicable):
I used preupgrade - 0.9.3-3.fc7.noarch (this is what the package manager says when I search for preupgrade among the installed packages)
If I close the preupgrader dialog and start it again (without deleting any downloaded packages)
I get the same errormessage and the same behaviour. I tried this several times.
Steps to Reproduce:
1. download preupgrade
2. start it
3. start downloading
It displayed "Downloading installer stage 2..." on the gui and seems to have frozen. On the console from which I started it, I got the following output:
[root@localhost tmp]# preupgrade
Traceback (most recent call last):
File "/usr/share/preupgrade/preupgrade-gtk.py", line 198, in on_assistant_apply
File "/usr/share/preupgrade/preupgrade-gtk.py", line 206, in _do_main
File "/usr/share/preupgrade/preupgrade-gtk.py", line 371, in main_preupgrade
(mdev,mpath) = preupgrade.bootpath_to_anacondapath(stage2_abs)
TypeError: unpack non-sequence
Download everything and prompt for restart as described on the fedora page.
It would be nice if preupgrade could be asked to display it's version. Maybe using an about menu item or a -v option.
Is there a Is there a possibility to resume the upgrade manually?
I already did a backup of my data and emails (bigish) and downloaded all the packages. I fear that if I can only continue after some days/weeks probably I have to do all that again :(
Thank you for your bug report.
We are sorry, but the Fedora Project no longer maintains this version of Fedora. Please upgrade to the latest version and reopen this bug against that version if this bug exists there.
As a result we are setting this bug to CLOSED:WONTFIX