Bug#210356: Does this bug still occur?

To: 210356-submitter@bugs.debian.org, 210356@bugs.debian.org
Cc: Jeff Bailey <jbailey@nisa.net>
Subject: Bug#210356: Does this bug still occur?
From: GOTO Masanori <gotom@debian.or.jp>
Date: Tue, 29 Jun 2004 18:08:28 +0900
Message-id: <[🔎] 81fz8eloj7.wl@omega.webmasters.gr.jp>
Reply-to: GOTO Masanori <gotom@debian.or.jp>, 210356@bugs.debian.org
In-reply-to: <20031214154343.GA2724@marge.v3.ca>
References: <20031214154343.GA2724@marge.v3.ca>

Hi,

Jeff Griffiths, could you check this bug report with the latest glibc package?

Regards,
-- gotom

At Sun, 14 Dec 2003 07:43:43 -0800,
Jeff Bailey wrote:
> 2.3.2-4 had this:
> 
>     - debian/patches/revert-old-libio.dpatch: back out changes causing
>       problems with fseek in binaries linked with glibc 2.0.
>       (Closes: #206839)
> 
> Which might be the cause of your problem.  We've since sorted this out
> with a correct fix.  Can you please try again against the current
> version of glibc?

Reply to:

Follow-Ups:
- Bug#210356: Does this bug still occur?
  - From: Jeff Griffiths <jeffg@ActiveState.com>

Prev by Date: Bug#208997: libc6: apache-perl needs to be restarted
Next by Date: cvs commit to glibc-package/debian by gotom
Previous by thread: Bug#208997: libc6: apache-perl needs to be restarted
Next by thread: Bug#210356: Does this bug still occur?
Index(es):
- Date
- Thread