Control: severity -1 serious
On 2013-05-08 09:37 +0200, Sven Joachim wrote:
> On 2013-05-08 03:32 +0200, Ben Hutchings wrote:
>> OK, where is /lib64/ld-linux-x86-64.so.2 pointing? To ld-2.13.so,
>> which does not exist.
>
> It ought to point at /lib/x86_64-linux-gnu/ld-2.13.so,
It does so in the libc6:amd64 package, but installing libc6-amd64
2.13-38 does indeed change the target to ld-2.13.so…
> and that should exist while the libc6:amd64 preinst runs.
…which does no longer exist at that time. :-/
>> This is left over from libc6-amd64, which
>> dpkg has mostly but not entirely removed in preparation for the
>> upgrade that replaces it.
>
> The new version of libc6-amd64 has already been unpacked, but
> /lib64/ld-linux-x86-64.so.2 belongs to libc6:amd64 which declares a
> "Replaces: libc6-amd64".
Unfortunately that does not help much because it's ldconfig which
changes the symlink.
>> -- System Information:
>> Debian Release: 7.0
>> APT prefers unstable
>> APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
>> Architecture: i386 (x86_64)
>> Foreign Architectures: amd64
If amd64 is the native architecture the problem becomes much worse since
you might not be able to run any programs. Hence I'm bumping the
severity.
Cheers,
Sven
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]
