update-manager in dapper needs to depend on python-vte (was: "can't find DistUpgradeViewGtk" when upgrading dapper->edgy)

Bug #67999 reported by Christian Kirbach
42
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Fix Released
High
Michael Vogt
Dapper
Fix Released
Undecided
Michael Vogt

Bug Description

Binary package hint: update-manager

running Dapper. started update-manager -c -d. hit button "upgrade" next to the notification "new release 6.10". release notes appeared, confirmed "upgrade". apt system starts working for a few seconds, then window closes.

update-manager 0.42.2ubuntu22

nazgul@dragonscale:~$ sudo update-manager -c -d
Password:
/usr/lib/python2.4/site-packages/apt/__init__.py:17: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
extracting '/tmp/tmp7Q3u7Y/edgy.tar.gz'
authenticate '/tmp/tmp7Q3u7Y/edgy.tar.gz' against '/tmp/tmp7Q3u7Y/edgy.tar.gz.gpg'
can't find DistUpgradeViewGtk

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Can you please check if you have the package 'python-vte' installed? If not, please install it and try again.

Thanks,
 Michael

Changed in update-manager:
status: Unconfirmed → Needs Info
Revision history for this message
Christian Kirbach (christian-kirbach-e) wrote :

Meanwhile I upgraded to Edgy using the command line.
However python-vte is currently not installed, thus I assume it was'nt installed on my Dapper system.

Shouldn't update-manager depend on it if it is required?

Revision history for this message
Russel Winder (russel) wrote :

I am an Ubuntu fan but this bug in the dapper -> edgy distribution upgrade really, really, really annoyed me. If upgrade-manager -c depends on python-vte then it should test for the presence of this package before starting -- and tell people to install it if it is not there.

installing python-vte does fix the problem.

This should have been a blocker bug not an undecided.

Revision history for this message
Christian Kirbach (christian-kirbach-e) wrote :

Michael, you may want to make the deb depend on python-vte

Revision history for this message
Christian Kirbach (christian-kirbach-e) wrote :

see also Bug #56627 , Bug #66376

Googling I saw quite some people hitting this issue

This is a real duplicate of Bug #66376

Michael Vogt (mvo)
Changed in update-manager:
importance: Undecided → High
status: Needs Info → Confirmed
Revision history for this message
Velanzia (madara-ranawake) wrote :

When I tried to upgrade to Edgy, faced with the same problem. Then I installed 'python vte' using 'Synaptic' - took only 1.5 hours, now I have Edgy on my machine!

But I beleve, if update process is dependent on 'python vte' it should look for it, rather than throwing an error.

Note: I installed Breezy, then upgraded to Dapper and from there I upgraded to Edgy.

Revision history for this message
Johansen (huwabaua) wrote :

I also tried to update to Edgy by the command "sudo sh /cdrom/cdromupgrade". However, I got the same error as the people above (can't find DistUpgradeViewGtk). After reading this thread I installed "python-vte" in the hope it could solve my problem. Unfortunatly it didn't change anything.

Revision history for this message
Stephen Sinclair (radarsat1) wrote :

Hello, I just ran into this issue. Installing python-vte fixed it.
This seems like it should be an easy fix to change a dependancy. I would like to note that the last comment was 1 month ago, and this bug is marked high priority.

Revision history for this message
Matthew McEachen (mrm-ubuntu) wrote :

Ran into the issue as well. I'm running edgy now, but this was an ugly hiccup in what otherwise was a very slick upgrade.

+1 to upgrade the priority.

Revision history for this message
Kyle Gordon (kylegordon) wrote :

Just encountered again this bug (again) whilst upgrading from Edgy to Dapper. The fix (a simple one too) has been known for over 6 months now - why hasn't it been resolved?

Revision history for this message
Rolf Leggewie (r0lf) wrote :

I guess you meant edgy -> feisty, right? Maybe you can increase attentaion if you sent Michael Vogt (https://bugs.launchpad.net/~mvo) a mail.

Revision history for this message
Kyle Gordon (kylegordon) wrote :

Sorry, I meant Dapper to Edgy, and then I'm going to upgrade Edgy to Feisty :-) I'd always been told to do it in stages, a release at a time.

I'll mail Michael and see what he says.

Changed in update-manager:
assignee: nobody → mrcheatr
status: Confirmed → In Progress
Changed in update-manager:
assignee: mrcheatr → nobody
status: In Progress → Confirmed
Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

Moving milestone.

Martin Pitt (pitti)
Changed in update-manager:
assignee: nobody → mvo
Revision history for this message
Martin Pitt (pitti) wrote :

This is already fixed in gutsy.

Changed in update-manager:
status: Confirmed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

Easy fix for dapper. Michael, can you please upload this to dapper-proposed?

Changed in update-manager:
assignee: nobody → mvo
status: New → In Progress
Revision history for this message
Michael Vogt (mvo) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :
Revision history for this message
Michael Vogt (mvo) wrote :

Uploaded into dapper-proposed

Revision history for this message
Martin Pitt (pitti) wrote :

Accepted to dapper-proposed, thank you! Please test.

Changed in update-manager:
status: In Progress → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

Dependencies are correct now with the dapper-proposed package, considering verification-done.

Revision history for this message
Martin Pitt (pitti) wrote :

Copied to dapper-updates.

Changed in update-manager:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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