[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#46106: marked as done (/lib/libndbm-2.1.2.so)



Your message dated Tue, 28 Sep 1999 22:45:39 +0200
with message-id <19990928224539.A11065@k6.resI.insa-lyon.fr>
and subject line libndbm.so
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.)

Darren Benham
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 27 Sep 1999 13:52:21 +0000
Received: (qmail 31998 invoked from network); 27 Sep 1999 13:52:21 -0000
Received: from rina.torah.org (brozen@207.226.84.142)
  by master.debian.org with SMTP; 27 Sep 1999 13:52:21 -0000
Received: from localhost (brozen@localhost)
	by rina.torah.org (8.9.3/8.9.3/Debian/GNU) with ESMTP id JAA26261
	for <submit@bugs.debian.org>; Mon, 27 Sep 1999 09:52:16 -0400
Date: Mon, 27 Sep 1999 15:52:16 +0200 (IST)
From: Brock Rozen <brozen@torah.org>
To: submit@bugs.debian.org
Subject: /lib/libndbm-2.1.2.so
Message-ID: <[🔎] Pine.LNX.4.10.9909271542100.25899-100000@rina.torah.org>
X-URL: http://www2.torah.org/~brozen/
X-Backup: Disable
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Severity: grave
Package: libc6
Version: 2.1.2-4

Is it just me or does /lib/libndbm-2.1.2.so not exist?

I even see a symlink to it from /lib/libndbm.so

In the stable version it is linked to libdb.so but when I just manually
installed the unstable version, ldconfig is complaining:

ldconfig: warning: can't open /usr/lib/libndbm.so (No such file or
directory), skipping


-- 
Brock Rozen                                              brozen@torah.org
Director of Technical Services                             (410) 602-1350
Project Genesis                                     http://www.torah.org/ 

---------------------------------------
Received: (at 46106-done) by bugs.debian.org; 28 Sep 1999 20:45:55 +0000
Received: (qmail 1566 invoked from network); 28 Sep 1999 20:45:53 -0000
Received: from i511.resi.insa-lyon.fr (HELO k6.resI.insa-lyon.fr) (134.214.164.9)
  by master.debian.org with SMTP; 28 Sep 1999 20:45:53 -0000
Received: by k6.resI.insa-lyon.fr (Postfix, from userid 1001)
	id A44B24078; Tue, 28 Sep 1999 22:45:39 +0200 (CEST)
Message-ID: <19990928224539.A11065@k6.resI.insa-lyon.fr>
Date: Tue, 28 Sep 1999 22:45:39 +0200
From: Raphael Hertzog <rhertzog@hrnet.fr>
To: Brock Rozen <brozen@torah.org>, 46106-done@bugs.debian.org
Subject: Re: libndbm.so
References: <[🔎] 19990927222634.A13063@k6.resI.insa-lyon.fr> <[🔎] Pine.LNX.4.10.9909282011220.15740-100000@rina.torah.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Transfer-Encoding: 8bit
X-Mailer: Mutt 0.93i
In-Reply-To: <[🔎] Pine.LNX.4.10.9909282011220.15740-100000@rina.torah.org>; from Brock Rozen on Tue, Sep 28, 1999 at 08:19:15PM +0200

Le Tue, Sep 28, 1999 at 08:19:15PM +0200, Brock Rozen écrivait:
> This could be the problem, as this is still the slink version. Regardless,
> the error occurred as a result of upgrading libc6 package to unstable
> without upgrading libc6-dev -- and thus that should be fixed.

This has already been corrected :

$ apt-cache show libc6-dev
Package: libc6-dev
Version: 2.1.2-4
Priority: standard
Section: devel
Maintainer: Debian GNU C Library Maintainers <debian-glibc@lists.debian.org>
Depends: libc6 (= 2.1.2-4)
                ^^^^^^^^^

libc6-dev depends on the specific libc you are running, so libc6-dev can
no more be out of sync with the installed libc.

That's why I'm closing the bug. If someone don't agree, then feel free to
reopen it.

Cheers,
-- 
Raphaël Hertzog >> 0C4CABF1 >> http://tux.u-strasbg.fr/~raphael/
<pub> CD Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd </pub>


Reply to: