Your message dated Mon, 02 Dec 2002 14:16:53 +0900 with message-id <[EMAIL PROTECTED]> and subject line Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 25 Nov 2002 07:03:41 +0000 >From [EMAIL PROTECTED] Mon Nov 25 01:03:40 2002 Return-path: <[EMAIL PROTECTED]> Received: from maild.telia.com [194.22.190.101] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 18GDHQ-0007qx-00; Mon, 25 Nov 2002 01:03:40 -0600 Received: from d1o264.telia.com (d1o264.telia.com [217.208.180.241]) by maild.telia.com (8.12.5/8.12.5) with ESMTP id gAP73dBi000434; Mon, 25 Nov 2002 08:03:39 +0100 (CET) X-Original-Recipient: [EMAIL PROTECTED] Received: from localhost (h203n2fls35o264.telia.com [217.211.113.203]) by d1o264.telia.com (8.10.2/8.10.1) with ESMTP id gAP73cb09993; Mon, 25 Nov 2002 08:03:38 +0100 (CET) Date: Mon, 25 Nov 2002 08:03:38 +0100 (CET) Message-Id: <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: [EMAIL PROTECTED] Subject: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks From: Magnus Danielson <[EMAIL PROTECTED]> X-Mailer: Mew version 2.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=0.6 required=5.0 tests=SPAM_PHRASE_00_01 version=2.41 X-Spam-Level: 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: Preparing to replace libc6 2.3.1-3 (using .../libc6_2.3.1-5_i386.deb) ... Unpacking replacement libc6 ... dpkg: error processing /var/cache/apt/archives/libc6_2.3.1-5_i386.deb (--unpack): unable to install new version of `./lib/ld-2.3.1.so': Device or resource busy dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libc6_2.3.1-5_i386.deb When the file is to be replaced, it is being used by a heap of different tools. "lsof | grep ld-" gives a pretty good idea where the trouble is. This have worked before, new upgrade routines in the libc6 package? Cheers, Magnus --------------------------------------- Received: (at 170635-done) by bugs.debian.org; 2 Dec 2002 05:16:56 +0000 >From [EMAIL PROTECTED] Sun Dec 01 23:16:56 2002 Return-path: <[EMAIL PROTECTED]> Received: from oris.opensource.jp (oris.opensource.gr.jp) [218.44.239.73] (postfix) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 18Iiwx-000339-00; Sun, 01 Dec 2002 23:16:55 -0600 Received: from oris.opensource.jp (oris.opensource.jp [218.44.239.73]) by oris.opensource.gr.jp (Postfix) with ESMTP id BF0E5C33C1; Mon, 2 Dec 2002 14:16:53 +0900 (JST) Date: Mon, 02 Dec 2002 14:16:53 +0900 Message-ID: <[EMAIL PROTECTED]> From: GOTO Masanori <[EMAIL PROTECTED]> To: Magnus Danielson <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Bug#170635: libc6 2.3.1-3 to 2.3.1-5 upgrade breaks In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2 (i386-debian-linux-gnu) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-10.6 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SPAM_PHRASE_02_03, USER_AGENT version=2.41 X-Spam-Level: At Mon, 02 Dec 2002 03:19:00 +0100 (CET), Magnus Danielson wrote: > > 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 This message is really normal state. /lib/ld-2.3.1.so is a normal file (not directory), so getting EBUSY ("Device or resource busy" message) may be it can't be shared but it's already in use. Using 'grep EBUSY in glibc/kernel source' tell you what EBUSY means. Usually EBUSY returns from kernel, not glibc (mostly). I guess system is inproper state, rebooting your system resolve this problem. I also guess you might use something to mount/unmount a filesystem. > 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. Yes. It's likely. Rebooting your system is right decision. If you are still enable to track this problem, check your filesystem and mount status. If this problem is glibc matter, the problem is reproduceable. I close this bug. -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]