do-release-upgrade fails libc quantal -> raring
Bug #1196762 reported by
David Austin
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubuntu-release-upgrader (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
The upgrade has aborted. Your system could be in an unusable state. A
recovery will run now (dpkg --configure -a).
Please report this bug in a browser at
http://
and attach the files in /var/log/
installArchives() failed
dpkg: dependency problems prevent configuration of libudev1:amd64:
libudev1:amd64 depends on libc6 (>= 2.17); however:
Version of libc6:amd64 on system is 2.15-0ubuntu20.1.
dpkg: error processing libudev1:amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libudev1:amd64
Upgrade complete
To post a comment you must log in.
Seems to be fixed by
apt-get -f install
The following extra packages will be installed:
libc-dev-bin libc6 libc6:i386 libc6-dev libnih-dbus1 libnih1
Suggested packages:
glibc-doc glibc-doc:i386 locales:i386
The following packages will be upgraded:
libc-dev-bin libc6 libc6:i386 libc6-dev libnih-dbus1 libnih1
6 upgraded, 0 newly installed, 0 to remove and 1046 not upgraded.
and then
apt-get dist-upgrade
did lots of work - and failed with more errors.
Looks like my mdadm array stayed mounted on /mnt (fuse - not my mount) after earlier failures,
causing issues for base-files:
Unpacking replacement base-files ... apt/archives/ base-files_ 6.12ubuntu2_ amd64.deb (--unpack):
dpkg: error processing /var/cache/
unable to stat `./mnt' (which I was about to install): Input/output error
Manually unmounted /mnt and then was able to complete apt-get dist-upgrade
David