Gutsy cdromupgrade script fails

[Michael Carden]

I downloaded ubuntu-7.10-alternate-i386.iso and mounted the iso via:

    sudo mount -o loop /mnt/wd2500/ubuntu/ubuntu-7.10-alternate-i386.iso /media/cdrom0/

I then ran the upgrade script via:

    sudo /media/cdrom0/cdromupgrade

The script terminated with the following:

A fatal error occured
Please report this as a bug and include the files /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in your report. The upgrade aborts now.

The /var/log/dist-upgrade/apt.log file is empty, and the /var/log/dist-upgrade/main.log file contains:

2007-10-19 15:19:33,550 INFO release-upgrader version '0.81' started
2007-10-19 15:19:33,830 WARNING can't import view 'DistUpgradeViewGtk' (No module named glade)
2007-10-19 15:19:34,094 WARNING can't import view 'DistUpgradeViewKDE' (No module named kdeui)
2007-10-19 15:19:34,454 DEBUG lsb-release: 'feisty'
2007-10-19 15:19:34,456 DEBUG _pythonSymlinkCheck run
2007-10-19 15:19:37,381 DEBUG checkViewDepends()
2007-10-19 15:19:37,390 ERROR not handled expection:
Traceback (most recent call last):

  File "/tmp/tmp.Nnbnr12603/gutsy", line 59, in <module>
    app.run()

  File "/tmp/tmp.Nnbnr12603/DistUpgradeControler.py", line 1346, in run
    self.fullUpgrade()

  File "/tmp/tmp.Nnbnr12603/DistUpgradeControler.py", line 1234, in fullUpgrade
    if not self.prepare():

  File "/tmp/tmp.Nnbnr12603/DistUpgradeControler.py", line 320, in prepare
    'Yes'

TypeError: askYesNoQuestion() takes exactly 3 arguments (4 given)

[Tzvetan Mikov (tmikov)]

Happened to me too. There seems to be a small bug in DistUpgradeViewText.py. The attached patch fixed the problem for me.

[Michael Vogt (mvo)]

Thanks for your bugreport.

Could you please attach the files in /var/log/dist-upgrade to this bugreport?

Thanks,
 Michael

[Michael Carden (mike-carden)]

On Tue, Apr 1, 2008 at 2:53 AM, Michael Vogt <email address hidden> wrote:
> Thanks for your bugreport.
>
> Could you please attach the files in /var/log/dist-upgrade to this
> bugreport?

I reported this in October last year. All data associated with it is
long gone I'm afraid.

Or did you intend that as an April Fool's Day suggestion?

Cheers,
MC

[Tzvetan Mikov (tmikov)]

What's the point of looking at the log files ? This seems like a trivial bug, which my patch (submitted about 6 months ago) fixes.