update-notifier-kde : Intrepid to Jaunty i386 upgrade failure

Bug #370454 reported by boblinux
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: update-manager

Hello,

I just wanted to perform this upgrade. First from Gnome, which failed with the error :

"Could not calculate the upgrade"

Then I tried from KDE with "update-notifier-kde -u" : same error.

I had an error because I missed the Launchpad public key in apt, I fixed this.
I had many obsoleted packages, I removed all of them.

Now (before upgrading) in synaptic I don't have any error.

What are all these "broken dependencies" in (attached) apt.log ?

It looks like the old days with the imperfect Mandrake distribution ...

Best regards
R. Grasso
System engineer

Revision history for this message
boblinux (robert-grasso) wrote :
Revision history for this message
boblinux (robert-grasso) wrote :
Revision history for this message
boblinux (robert-grasso) wrote :

I am still learning the Debian system.

As I have one error in main.log :

2009-05-01 19:20:46,562 ERROR Dist-upgrade failed: 'E:Unable to correct problems, you have held broken packages.'

according to teh Debian doc, I ran :

apt-get check

which did not report any broken package or other error.

Revision history for this message
Thomas Kluyver (takluyver) wrote :

It looks like the problem starts when it retains libkipi0, rather than replacing it with libkipi6.

The upgrade tool will have rolled back when it failed, so you won't be able to see the errors in synaptic normally. if you want to see what it's trying to do, you'll have to start the upgrade one way or another, so that it replaces 'intrepid' with 'jaunty' in /etc/apt/source.list, and then gets the new package lists. If you can stop it after that stage, then look at a package manager to see what it's trying to do... This is obviously something to try if you're comfortable mucking around with your system a bit.

Revision history for this message
boblinux (robert-grasso) wrote :

Thank you for your quick suggestion. I apologize I did not post before, but I wanted to monitor my upgrade a bit before : the error above about broken packages mentioned gwenview (which was not broken at all - mentioned in main.log). So I just uninstalled gwenview, restarted the upgrade : which is running smoothly so far. Thus I don't know what all these "broken dependencies" messages were (false positives ?) - but it seems that update-manager has a true problem with gwenview

Revision history for this message
boblinux (robert-grasso) wrote :

now that I know what this is about, I found the bug 365840 which describes exactly the same issue - a fix was found but I ran obviously my upgrade too soon, and the fixed update-manager was not pushed yet into any download

Revision history for this message
Thomas Kluyver (takluyver) wrote :

OK, great, I'll mark this as a duplicate of that.

You wouldn't yet see the fix even if you were updating now, as the new update-manager has only made it to jaunty-proposed. Good to know that the issue's being sorted, though.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.