Upgrade fails (possibly due to absence of default sources)

[DerGuteMoritz]

Upgrading to Dapper fails on my machine. Regarding the information the traceback gives me, I believe this is due to the absence of the default Ubuntu apt sources in my sources.list since I am using apt-proxy. I only attached my dist-upgrade.log since the other ones were empty anyway.

[DerGuteMoritz (moritz-invision-team)]

The log file produced by upgrade-manager.

[DerGuteMoritz (moritz-invision-team)]

Ah, correction: I now know why it doesn't work - it's because my apt-proxy's name doesn't contain a dot, so this line 205 in aptsources.py is bound to fail:

if compare_srv[compare_srv.index(".")+1:] == master_srv:

Slightly off topic: Why is my first version of the bug's description still visible? I firstly appended my log file inline because on the bug submittal page I wasn't given an option do append a file ... hmm.

[Michael Vogt (mvo)]

Thanks for your bugreport.

This problem is fixed in my bzr version of update-manager and it will be part of the next upload.

Cheers,
 Michael

[Michael Vogt (mvo)]

The crash itself is fixed in bzr now, but the root of the problem remains. If you have nothing that looks like a official ubuntu source, it will fail to rewrite your sources.list.

Some more intelligence is needed here, but it may be hard to come up with something reliable.

[DerGuteMoritz (moritz-invision-team)]

Thank you very much!
What exactly are the criteria for identifying an official Ubuntu source?
You are right, there seems to be no reliable way of handling this. But then, update-manager isn't actually targeted at people using an apt-proxy except for situations where there is an administrator maintaining the proxy and wanting his users to be able to upgrade their release using this nice graphical interface without a headache through the apt-proxy server. Given this case, one would need something to mark an apt source 'official', enabling update-manager to rewrite it. Putting a comment before/after the source entry comes to mind but maybe this is not what one would call a straight forward approach. Should I file a new bug report concerning this problem?

[Gianluca Sartori (g-sartori-gmail)]

Same problem here upgrading from dapper to edgy. The following is the last line in /var/log/dist-upgrade/main.log

2006-10-21 11:07:18,124 DEBUG Can't mark 'ubuntu-desktop' for upgrade (E:Impossibile correggere i problemi, ci sono pacchetti rotti bloccati)

I'm attaching the whole folder.
Gianluca