For the ones still having problems, check if you have any apt pinning
that prevents the libc6 update. For example, you can use "apt-cache
policy libc6" to check which version you have installed (marked with
"***") and what priority the maverick-updates/main repository is given.
Personally, I had the updates and security repositories set to the same
priority through /etc/apt/preferences and ended up getting libc6 stuck
at the 2.12.1-0ubuntu10.1 level from the security repository. Commenting
out apt pinning preferences for maverick-security and maverick-updates
in /etc/apt/preferences (i.e. going back to default priority of 500) and
doing aptitude update + aptitude dist-upgrade fixed this problem.
Before:
apt-cache policy libc6
2.12.1-0ubuntu10.2 0
900 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/
maverick-updates/main amd64 Packages
*** 2.12.1-0ubuntu10.1 0
990 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/
maverick-security/main amd64 Packages
100 /var/lib/dpkg/status
2.12.1-0ubuntu6 0
500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/ maverick/main
amd64 Packages
After:
apt-cache policy libc6
*** 2.12.1-0ubuntu10.2 0
500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/
maverick-updates/main amd64 Packages
100 /var/lib/dpkg/status
2.12.1-0ubuntu10.1 0
500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/
maverick-security/main amd64 Packages
2.12.1-0ubuntu6 0
500 http://ftp.hosteurope.de/mirror/archive.ubuntu.com/ maverick/main
amd64 Packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/711601
Title:
[fixed] upstart 0.6.6-4 - cannot install new update
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
