Bug#221360: upgrade of libc6_2.3.2.ds1-10 hosed libc install

[Miek Gieben <miekg@atoom.net>]

[On 17 Nov, @23:19, Daniel wrote in "Re: Bug#221360: upgrade of lib ..."]
> > And I have no glue what to do next. I've copied the /lib/tls directory over from
> > my server, but I'm hesitating to delete the libraries in question.
> 
> What are those libraries?  Are they symlinks, old versions, whatever -
> and can you get any idea where they came from?  We've had a lot of
> reports but we can't figure out how it keeps happening.

a dpkg tells me this:

root@kasteel# dpkg -S /lib/libc.so.6 
libc6: /lib/libc.so.6

root@kasteel# dpkg -s libc6
Package: libc6
Status: install ok installed
Priority: required
Section: base
Installed-Size: 12808
Maintainer: GNU Libc Maintainers <debian-glibc@lists.debian.org>
Source: glibc
Version: 2.3.2-9

So it looks like the it is just the old libc package.

> Save them to another directory and reinstall libc6, and you should be
> fine.  And the /lib/tls dir has nothing to do with the problem.

will that actually work? I do not want to be blunt, but several years ago
I've delete libc from my system and that was not a lot of fun :(

And from the looks of it, there _are_ used:
root@kasteel# ldd `which ls`
                librt.so.1 => /lib/librt.so.1 (0x4001a000)
        libc.so.6 => /lib/libc.so.6 (0x4002c000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x4015a000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

thanks for your quick reply, btw.

grtz
      Miek
--
Serenity now!
-- Frank Costanza (Seinfeld)