Bug#264835: Processed: gcc bug still around?

To: Debian Bug Tracking System <264835@bugs.debian.org>
Subject: Bug#264835: Processed: gcc bug still around?
From: Martin Samuelsson <debianbts@cos.user.lysator.liu.se>
Date: Thu, 26 Aug 2004 12:12:56 +0200
Message-id: <[🔎] 20040826101254.GI13524@ch.lugn.nu>
Reply-to: Martin Samuelsson <debianbts@cos.user.lysator.liu.se>, 264835@bugs.debian.org
In-reply-to: <[🔎] handler.s.C.109351408320831.transcript@bugs.debian.org>
References: <20040826095409.GH13524@ch.lugn.nu> <[🔎] handler.s.C.109351408320831.transcript@bugs.debian.org>

I don't know if reopening is the right thing to do, but I'm running an
up to date testing system where this bug still is around.

Since I'm merely a user, I don't have full understanding of how debian's
package upgrading paths are. However there has passed almost one week
since Mr. Langasek: wrote will be fixed tomorrow.

Are the fixed packages propagating through a pipe somewhere, or is the
bug still around?
--
/Martin

Attachment: pgp61ED3gIJtH.pgp
Description: PGP signature

Reply to:

Follow-Ups:
- Bug#264835: Processed: gcc bug still around?
  - From: Andreas Metzler <ametzler@downhill.at.eu.org>

References:
- Processed: gcc bug still around?
  - From: owner@bugs.debian.org (Debian Bug Tracking System)

Prev by Date: Bug#268140: libffi.la: wrong libdir setting
Next by Date: Processing of gcc-3.3_3.3.4-6sarge1.1_wheee.changes
Previous by thread: Processed: gcc bug still around?
Next by thread: Bug#264835: Processed: gcc bug still around?
Index(es):
- Date
- Thread