Bug#204215: does this still happen with the new glibc?

To: 204215-submitter@bugs.debian.org, 204215@bugs.debian.org
Cc: control@bugs.debian.org
Subject: Bug#204215: does this still happen with the new glibc?
From: Rene Engelhard <rene@debian.org>
Date: Sun, 21 Sep 2003 15:57:56 +0200
Message-id: <[🔎] 20030921135755.GN751@rene-engelhard.de>
Reply-to: Rene Engelhard <rene@debian.org>, 204215@bugs.debian.org

tag 204215 + sarge
thanks

Hi,

is this still happening with the new libc which just entered sarge?
Because these relocation errors were a libc6 bug fixed in 2.3.2....

If it doesn't happen anymore, I would like to close this bug....

Grüße/Regards,

René
-- 
 .''`.  René Engelhard -- Debian GNU/Linux Developer
 : :' : http://www.debian.org | http://people.debian.org/~rene/
 `. `'  rene@debian.org | GnuPG-Key ID: 248AEB73
   `-   Fingerprint: 41FA F208 28D4 7CA5 19BB  7AD9 F859 90B0 248A EB73

Attachment: signature.asc
Description: Digital signature

Reply to:

Follow-Ups:
- Processed: does this still happen with the new glibc?
  - From: owner@bugs.debian.org (Debian Bug Tracking System)

Prev by Date: Bug#211972: openoffice.org-bin: Print preview command missing in file menu
Next by Date: Processed: does this still happen with the new glibc?
Previous by thread: Bug#211972: openoffice.org-bin: Print preview command missing in file menu
Next by thread: Processed: does this still happen with the new glibc?
Index(es):
- Date
- Thread