Re: Proposed fix for ld.so assertion failures for sarge

To: debian-glibc@lists.debian.org, debian-release@lists.debian.org
Subject: Re: Proposed fix for ld.so assertion failures for sarge
From: Daniel Jacobowitz <dan@debian.org>
Date: Mon, 9 May 2005 19:20:00 -0400
Message-id: <[🔎] 20050509232000.GA20895@nevyn.them.org>
Mail-followup-to: debian-glibc@lists.debian.org, debian-release@lists.debian.org
In-reply-to: <[🔎] 20050508173527.GA12796@nevyn.them.org>
References: <[🔎] 20050508173527.GA12796@nevyn.them.org>

On Sun, May 08, 2005 at 01:35:27PM -0400, Daniel Jacobowitz wrote:
> At the bottom of this message is a diff against glibc 2.3.2.ds1-21 which
> fixes merged bugs 207872, 210840, 274852, and 276384.  I spoke with Colin on
> IRC and he seemed amenable to this as a last-minute fix for sarge.  Does
> anyone else have an opinion?  Are there any other bugs vital enough to fix
> at the same time?

Anybody?  If we're going to have a new glibc for sarge, it needs to be
sooner rather than later.

-- 
Daniel Jacobowitz
CodeSourcery, LLC

Reply to:

References:
- Proposed fix for ld.so assertion failures for sarge
  - From: Daniel Jacobowitz <dan@debian.org>

Prev by Date: please approve for testing: abs-guide, python-profiler, python2.4, pysvn, kodos, doxygen, mailscanner
Next by Date: Re: please approve for testing: abs-guide, python-profiler, python2.4, pysvn, kodos, doxygen, mailscanner
Previous by thread: Proposed fix for ld.so assertion failures for sarge
Next by thread: logwatch 5.2.2-6
Index(es):
- Date
- Thread