Upgrade from Dapper to Edgy failed because xutils could not be found

Bug #67368 reported by Mariano Draghi
4
Affects Status Importance Assigned to Milestone
lighttpd (Ubuntu)
Invalid
Undecided
Unassigned
update-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I'm trying to update my box doing a
  update-manager -c -d

First I run into bug #58424, but by following the instructions in that bug report I can get update-manager to begin the download of edgy packages.

As soon as the download finsished, a window pop-up, telling that the updates could not be installed, because xinit package could not be found.

The message box says update-manager is running a dpkg --configure -a

Tags: edgy-upgrade
Revision history for this message
Mariano Draghi (chaghi) wrote :

apt.log

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

Thanks for your bugreport and for the logs.

Is this problem reproducable for you? I would like to see a screenshot of the error message because it if for some strange reason not in the logs (all errors should end up there).

Thanks,
 Michael

Changed in update-manager:
status: Unconfirmed → Needs Info
Revision history for this message
Mariano Draghi (chaghi) wrote :

Unfortunately it's not. I've already completed the upgrade.

I think the problem was caused by some package that could not be downloaded (look at the end of main.log), which in turn broke the transaction that the update-manager had precalculated.

I started it again, it downloaded a few more packages (which seems to confirm my idea), and then it crashed again, because for some unknown reason the initscript for "lighttpd" returned exit status 1 when the pre-removal script run it. That's because for some reason the /etc/init.d/lighttpd script returned 1 trying to stop the service.

At that point, I decided to gave up on update-manager and get my hands dirty. I edited /etc/init.d/lighttpd, and added an "exit 0" as the first line. After that, and a few aptitude update, aptitude dist-upgrade and aptitude -f install, I finished the upgrade.

So, to sum it up:
 - it seems that update-manager doesn't get notified if a package can not be downloaded (this I think is a bug)
 - maybe there's a bug in the lighttpd pre-removal script; or smething broke in between (lighttpd was starting/stopping normally before the update), but the fact is that update-manager could not deal with it (and I think that's a pitty but it's fine... a pre-removal script can fail for a thousand reasons, and could not be ignored that easy.)

Here's the last lines of my last attempt with update-manager:

2006-10-21 09:56:46,713 DEBUG Free space on /: 4359114752
2006-10-21 09:56:46,713 DEBUG Dir /usr mounted on /
2006-10-21 09:56:46,714 DEBUG Dir /var mounted on /
2006-10-21 09:56:46,714 DEBUG Free space on /boot: 31480832
2006-10-21 09:56:47,280 DEBUG required download: 5254666.0
2006-10-21 09:56:47,280 DEBUG free on /var/cache/apt/archives/: 4359114752
2006-10-21 09:56:47,810 DEBUG need additional space: 486704128.0
2006-10-21 09:56:48,368 DEBUG /usr on same fs as /var/cache/apt/archives/, taking dl-size into account, new free: 4353860086.0
2006-10-21 09:56:48,368 DEBUG using safety buffer: 104857600
2006-10-21 10:13:00,123 DEBUG got a conffile-prompt from dpkg for file: '/etc/bash_completion'
2006-10-21 10:34:39,463 ERROR got an error from dpkg for pkg: '/var/cache/apt/archives/lighttpd_1.4.13~r1370-1ubuntu1_i386.deb': 'subprocess new pre-removal script returned error exit status 1
'
2006-10-21 10:43:22,742 WARNING no activity on terminal for 240 seconds (Preparándose para configurar liferea-gtkhtml)

Revision history for this message
Lukas Fittl (lfittl) wrote :

The lighttpd problem is a seperate bug, and already known (bug #68401).

Changed in lighttpd:
status: Unconfirmed → Rejected
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for update-manager (Ubuntu) because there has been no activity for 60 days.]

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.