Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
From: Jeff Bailey <jbailey@nisa.net>
Subject: Re: Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks
Date: 25 Nov 2002 06:58:16 -0500
Hi Jeff,
> On Mon, 2002-11-25 at 02:03, Magnus Danielson wrote:
>
> > Package: libc6
> > Version: 2.3.1-5
> > Severity: critical
> >
> > On upgrading my Debian/unstable system (oddly called heaven) from libc6 2.3.1-3
> > to 2.3.1-5 it halts the installation with this text:
>
> I've done -3 to -5 upgrades on many i386 systems, and 2.2.5 to 2.3.1-5 upgrades
> hurd-i386 and sparc and never seen this message. I need more details.
OK. This is what happend:
When the dpkg wanted to remove /lib/ld-2.3.1.so in order to insert it's own
(identical) this was not possible since the rm command got:
rm /lib/ld-2.3.1.so
I got the "Device or resource busy" message as a reply. It's because the file
is in use by many tools:
# lsof | grep ld-2.3.1.so
bash 907 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
startx 1005 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
xinit 1016 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
fvwm2 1021 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
xsnow 1023 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
xterm 1024 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
xterm 1025 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
xterm 1026 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
bubblefis 1027 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
bash 1028 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
bash 1029 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
bash 1030 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
FvwmPager 1031 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
emacs 3834 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
lsof 6487 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
grep 6488 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
lsof 6489 magnus mem REG 3,1 83504 1208304 /lib/ld-2.3.1.so
However, it is fishy that I should run into that problem... libc6 updates
should run smoothly and they have before.
Now, the trick around this problem is to do
cp /lib/ld-2.3.1.so /lib/ld-2.3.1.so.foo
rm /lib/ld-linux.so.2
ldconfig
Since the copied file which is more recent and ldconfig will fetch the
later. However, the bindings to the old one remains, so a reboot is the only
cure, but then the bindings will point to the .foo variant at next time, so
a new attempt to install will now work. What ever caused this problem, I don't
know. I've run pretty tight updates to unstable on this machine and this is one
of the few hickups I've had.
Now I have put these troubles behind me, but someone should figure out how to
handle this problem, both on how it could occur (I haven't fiddle with that
file prior to this!) and when it occurs. If you fuck up the libc6 installation
a lot of other stuff falls right off.
Cheers,
Magnus
Reply to: