libc6 update for Edgy fails due to sanity check
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
glibc (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Dapper |
Fix Released
|
High
|
Fabio Massimo Di Nitto |
Bug Description
The preinst script in libc6 (and variants) contains a sanity check which is designed to locate improperly-
The system is not harmed in any way by this failure, so DO NOT attempt to "fix" it with dpkg or by moving files by hand. Simply wait for the next update to be available from your local mirror, and install it when it arrives.
There are two problems related to this check:
1. The test contains a bug causing it to be triggered by an unrelated (valid) library provided by the libpthread20 package.
2. Some users have reported occurrences of /usr/lib/libdl.so.2 and /usr/lib/libc.so.6 which trigger the check. These files are NOT provided by any Ubuntu package and their origin is as yet unknown.
For example:
(Reading database ... 160320 files and directories currently installed.)
Preparing to replace libc6-dev 2.4-1ubuntu12 (using .../libc6-
Unpacking replacement libc6-dev ...
Preparing to replace libc6 2.4-1ubuntu12 (using .../libc6_
Matching libraries: /usr/lib/libc.so.6 /lib/ld-linux.so.2
A copy of glibc was found in an unexpected directory.
It is not safe to upgrade the C library in this situation;
please remove that copy of the C library and try again.
dpkg: error processing /var/cache/
subprocess pre-installation script returned error exit status 1
Errors were encountered while processing:
/var/cache/
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install. Trying to recover:
dpkg: dependency problems prevent configuration of libc6-dev:
libc6-dev depends on libc6 (= 2.4-1ubuntu12.2); however:
Version of libc6 on system is 2.4-1ubuntu12.
dpkg: error processing libc6-dev (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
libc6-dev
Ubuntu does not ship /usr/lib/libc.so.6 and never did or will.
The message is telling you what to do and why it's aborting the upgrade. It's not a bug.
Fabio