Gutsy->Hardy Upgrade: "unresolvable problem occurred"

Bug #221285 reported by Doug on 2008-04-24
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)

Bug Description

Binary package hint: update-manager

I got these messages when running 'update-manager':
Can't install 'ubuntu-desktop'
An unresolvable problem occurred while calculating the upgrade.
Please report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bugreport.
my Ubuntu release: 7.10
update-manager version: 1:0.81.3

I have 863 packages listed as updates, and began doing a "partial" dist-upgrade, but I think update-manager cannot work around broken package dependencies related to 'ubuntu-desktop'.

I will include the apt.log, as requested in the above message. It's 180kB so I will upload it compressed. I believe I can find a work-around, but wanted to "follow directions" to report this as a bug.


Doug (illusion65) wrote :
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Could you please attach the "main.log" file as well to this report? What version of python do you have installed (dpkg -l python|grep ^ii)?

Changed in update-manager:
status: New → Incomplete
Doug (illusion65) wrote :

python: 2.5.1-1ubuntu2

I installed ubuntu-desktop, which removed many packages (~20) and installed many more (~40) using synaptic. Then ran update-manager again. This time I did not get the error during the dist-upgrade, but it stopped with "Error authenticating some packages", listing a large collection (maybe all ~800 being upgraded) of common packages (acpi, gcc, many lib*, python2.5, xsane, ...).

"main.log.bz2" attached. I didn't think it would be useful since it, "main-pre-req.log" & "term.log" (also in "/var/log/dist-upgrade") are dated 28 Oct 2007, which is when I upgraded from Feisty to Gutsy.


Michael Vogt (mvo) wrote :

Thanks for the additional information.

The large number of package to update indicates that your /etc/apt/sources.list got modified to a different version of ubuntu than the one you installed (or upgraded) too. Could you please attach that file too?

Doug (illusion65) wrote :

Hi Michael,

Sorry about the delay, I was on holiday the week that you posted and just now catching up from a flurry of work. I did solve the problem, but I don't think I did anything special. Instead of trying a system update, I ran a distribution upgrade.

I'm including three "sources.list" with their dates as suffix. The 17Jul07 is certainly "before" I tried the Hardy upgrade, the source.list.21Apr08 was probably timestamped when I first tried the upgrade (and was marked ".saved", with a duplicate named ".distUpgrade"), and the .28Apr08 sources.list file is post-upgrade and has the Hardy references. I believe the references are correct in the files, but I'll let you determine that for certain.

Since that time, I've "fresh" installed Hardy on 2 laptops and dist-upgraded another, so now we're a 4 laptop, Ubuntu family! The Hardy "fresh install" is easily the best experience I've encountered for installing an OS on a laptop. Well done and thanks to everyone who's contributed so much.


Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 46245, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

Brian Murray (brian-murray) wrote :

This probably has something to with one of the following repositories which I found in the 21Apr08 sources.list file:

deb experimental/
deb-src experimental/
deb gutsy free non-free
deb breezy/all/
deb breezy/$(ARCH)/
deb lenny main

Changed in update-manager:
importance: Undecided → Low
status: Incomplete → Confirmed
Pinejoker (esijeffrey) wrote :
Download full text (13.1 KiB)

i got same problem

family@family-desktop:~$ sudo do-release-upgrade
Checking for a new ubuntu release
Done Upgrade tool signature
Done Upgrade tool
Done downloading
extracting '/tmp/tmp-1yX90/gutsy.tar.gz'
authenticate '/tmp/tmp-1yX90/gutsy.tar.gz' against '/tmp/tmp-1yX90/gutsy.tar.gz.gpg'

Reading cache

Checking package manager
Reading package lists: Done
Reading state information: Done
Reading state information: Done
Reading state information: Done
Ignored feisty-backports Release.gpg
Failed feisty-backports Release.gpg
Done feisty-updates Release.gpg
Done feisty Release.gpg
Done feisty-backports Release.gpg
Ignored feisty-backports Release
Failed feisty-backports Release
Done feisty-security Release.gpg
Done feisty-proposed Release.gpg
Hit feisty-updates Release
Done feisty-updates Release
Ignored feisty-backports/main/debian-installer Packages
Failed feisty-backports/main/debian-installer Packages
Hit feisty Release
Hit feisty-backports Release
Hit feisty-security Release
Done feisty Release
Done feisty-backports Release
Done feisty-security Release
Failed feisty-backports/main/debian-installer Packages
Hit feisty-proposed Release
Done feisty-proposed Release
Hit feisty-updates/main Packages
Hit feisty-updates/restricted Packages
Hit feisty-updates/main Sources
Hit feisty-updates/restricted Sources
Hit feisty-updates/main Packages
Hit feisty-updates/restricted Packages
Hit feisty-updates/universe Packages
Hit feisty-updates/multiverse Packages
Hit feisty-updates/main Sources
Hit feisty-updates/restricted Sources
Hit feisty-updates/universe Sources
Hit feisty-updates/multiverse Sources
Hit feisty/universe Packages
Hit feisty/universe Sources
Hit feisty/multiverse Packages
Hit feisty/multiverse Sources
Hit feisty-backports/main Packages
Hit feisty-backports/restricted Packages
Hit feisty-backports/universe Packages
Hit feisty-backports/multiverse Packages
Hit http://old-rel...

RedSingularity (redsingularity) wrote :

Cleaning up unsupported versions.
Ubuntu Bug Squad volunteer triager

Changed in update-manager (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers