[update-manager] Getting upgrade prerequisites failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: update-manager
The update-manager from feisty to gutsy.
the /var/log/
2007-10-18 20:09:37,978 INFO release-upgrader version '0.81' started
2007-10-18 20:09:39,427 DEBUG lsb-release: 'feisty'
2007-10-18 20:09:39,427 DEBUG _pythonSymlinkCheck run
2007-10-18 20:09:40,941 DEBUG checkViewDepends()
2007-10-18 20:09:40,942 DEBUG getRequiredBack
2007-10-18 20:11:15,779 DEBUG marking 'release-
2007-10-18 20:11:15,896 DEBUG marking 'release-
2007-10-18 20:15:16,084 DEBUG pre-requists item: '<pkgAcquire:
2007-10-18 20:15:16,084 DEBUG pre-requists item: '<pkgAcquire:
2007-10-18 20:15:16,085 ERROR no backports found but setupRequiredBa
ProblemType: Bug
Architecture: i386
Date: Thu Oct 18 20:17:24 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/
Package: gnome-panel 1:2.18.1-0ubuntu3.1
PackageArchitec
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/kush
ProcEnviron:
PATH=/
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-panel
Uname: Linux sakura 2.6.20-16-generic #2 SMP Sun Sep 23 19:50:39 UTC 2007 i686 GNU/Linux
There is no need for me to attach my main.log since it is identical to all main.log files posted here already. There is an obvious problem with this upgrade. I'm struggling with it the third day and no solution found so far.
OK!...
Right now when I'm writing I have a little change to positive in Update Manager behavior. It finally get prerequisites and looks like it is proceeding further on. To get to this point I had to disable "universe" /"community supported" in my sources list. I was prompted that some of packages installed on my PC are no longer supported by Canonical and I would be prompted to remove them after upgrade completed or I would be able to choose keeping them if I wish.
Right now I am in the 3-d step - Fetching the Upgrades. Let's hope this was a solution.
I think if the Upgrade process is so picky to what is currently supported by Canonical and what is not then the procedure should have started from backing up a local sources.list file, replacing it with one that can for sure satisfy the Upgrade and then to proceed with the upgrade. Then after the Upgrade is completed a user could be prompted about changes in files support by Canonical and be given a choice either to use a new sources.list or to get back to his own one.
Otherwise the Upgrade is a nightmare. It was much easier for me just to install it fresh.