On Tue, Nov 12, 2013 at 10:08:05AM -0500, Daniel Genin wrote: > Just ran into this bug after installing and uninstalling gdb64 (which > depends on libc6-amd64). > > Having root access does not solve the problem because rm and ln rely on > libc6 > > ~$ ldd /bin/rm > linux-vdso.so.1 => (0x00007fffd578e000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f37ad8ee000) > /lib64/ld-linux-x86-64.so.2 (0x00007f37adcd4000) > > Time to dust off that installation DVD or make a new one if you have access > to another machine. > > I agree that this is an insidious bug for inexperienced users to diagnose > because > the system becomes unusable and unbootable.
Indeed. We haven't thought that libc6-amd64 can be installed on an amd64 system (it doesn't bring anything as for gdb64), but the multiarch specification doesn't provide a way to prevent such a package to be installed. We are therefore currently working on a solution that allow libc6-amd64:i386 to be installed without breaking the system. For already broken systems like yours, here is a procedure to fix it. On a rescue system, change to the root directory of the system to be fixed. - make sure ldconfig won't be run anymore: ln -sf /bin/true lib/ldconfig - point the symlink to the correct libc version: ln -sf /lib/x86_64-linux-gnu/libdl-2.13.so lib64/ld-linux-x86-64.so.2 note that the version 2.13 might have to be adjusted depending on the libc currently installed on your system Then reboot on the system and run the following commands: - remove libc6-amd64: apt-get remove libc6-amd64 - reinstall and/or upgrade at least libc6 and libc-bin: apt-get --reinstall libc6 libc-bin -- Aurelien Jarno GPG: 1024D/F1BCDB73 aurel...@aurel32.net http://www.aurel32.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org