Your message dated Mon, 15 Aug 2005 15:51:41 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#323032: libc6: GLIBC_PRIVATE errors
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; 14 Aug 2005 09:54:35 +0000
>From [EMAIL PROTECTED] Sun Aug 14 02:54:35 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp.kisikew.org (smtp.nuit.ca) [66.11.160.83] (Debian-exim)
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E4FCN-00022L-00; Sun, 14 Aug 2005 02:54:35 -0700
Received: from simon by smtp.nuit.ca with local (Exim 4.52)
msgID 1E4FCI-0002G0-Pe; Sun, 14 Aug 2005 09:54:30 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: simon raven <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: libc6: GLIBC_PRIVATE errors
X-Mailer: reportbug 3.15
Date: Sun, 14 Aug 2005 05:54:30 -0400
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: libc6
Version: 2.3.2.ds1-22
Severity: grave
Justification: renders package unusable
fakeroot debian/rules binary
/usr/bin/make: relocation error: /lib/libdl.so.2: symbol _dl_catch_error,
version GLIBC_PRIVATE not defined in file ld.so.1 with link time reference
zsh: 8307 exit 127 fakeroot debian/rules binary
this is a follow-up to 321561 and 321712. if i allow the upgrade to
happen, i can't even run make, or perl, or crond, or anything at all in
fact. please fix this.
when i run strings on the library (libc6 so file) i see the "GLIBC_PRIVATE"
string.
isn't this supposed to work, like the previous libc6 major change (like
the woody->sarge one)? perl pukes in such a way that the locale gets all
confused, and cannot load properly, and the locales package install
fails, if libc6 2.3.5 is installed.
i haven't been able to upgrade for days and days, and this worries me
because there are security issues involved here.
i would also like a clarification on what's going on, being in the dark
isn't helping anything, either.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (1000, 'unstable'), (998, 'experimental')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.12-pylon
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Versions of packages libc6 depends on:
ii libdb1-compat 2.1.3-7 The Berkeley database routines [gl
libc6 recommends no packages.
-- no debconf information
---------------------------------------
Received: (at 323032-done) by bugs.debian.org; 15 Aug 2005 22:51:42 +0000
>From [EMAIL PROTECTED] Mon Aug 15 15:51:42 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (mauritius.dodds.net)
[66.93.39.86]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1E4nny-0001d9-00; Mon, 15 Aug 2005 15:51:42 -0700
Received: by mauritius.dodds.net (Postfix, from userid 1000)
id 67BD8171D65; Mon, 15 Aug 2005 15:51:41 -0700 (PDT)
Date: Mon, 15 Aug 2005 15:51:41 -0700
From: Steve Langasek <[EMAIL PROTECTED]>
To: "SR, ESC" <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#323032: libc6: GLIBC_PRIVATE errors
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL
PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="UKNXkkdQCYZ6W5l3"
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
--UKNXkkdQCYZ6W5l3
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Aug 15, 2005 at 12:56:25PM -0400, SR, ESC wrote:
> Le lun 2005-08-15 a 12:45:56 -0400, Daniel Jacobowitz <[EMAIL PROTECTED]> a =
dit:
> > > $ dpkg -x g/glibc/libc6_2.3.5-3_powerpc.deb /tmp/libc6
> > > $ nm -Du /tmp/libc6/lib/libdl.so.2 |grep _dl_catch_error
> > > $
> > > I can't find any evidence of this bug you're describing in glibc 2.3.=
5-3.
> > It was in 2.3.2, however; I suspect that Simon has somehow managed to
> > get the old libdl with the new ld.so. Probably there is a stray copy
> > in /usr or some directory in /etc/ld.so.conf.
> it's *exactly* what happened. i had prelink installed a lomng while
> ago, and it had made a mess of the libs, and i guess i mised a few
> things in the clean-up. i keep finding stray cruft like this
> sometimes. you can close all the bugs now, it works seemingly flawlessly =
as
> usual.
> thank you for putting up with me =3D), and for the help.
Thanks for the followup, Simon. Closing this report.
--=20
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--UKNXkkdQCYZ6W5l3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDARx9KN6ufymYLloRAh+ZAJ9G86CuMZ5cLe+jTJeGcIASOhaWvgCfa76H
eZkXduWUJuNU5Tb/Ay/VOJs=
=oiHW
-----END PGP SIGNATURE-----
--UKNXkkdQCYZ6W5l3--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
