Your message dated Mon, 28 May 2001 00:08:35 +0200 (MEST) with message-id <[EMAIL PROTECTED]> and subject line fixed bugs in gcc-3.0 (3.0.ds6-0pre010526) 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.) Darren Benham (administrator, Debian Bugs database) -------------------------------------- Received: (at submit) by bugs.debian.org; 4 May 2001 02:17:33 +0000 >From [EMAIL PROTECTED] Thu May 03 21:17:33 2001 Return-path: <[EMAIL PROTECTED]> Received: from as5800-82-74.access.naxs.com (silk.kitenet.net) [216.98.82.74] (mail) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 14vV9w-0003Ys-00; Thu, 03 May 2001 21:17:33 -0500 Received: from joey by silk.kitenet.net with local (Exim 3.22 #1 (Debian)) id 14vVDB-0000R0-00; Thu, 03 May 2001 22:20:53 -0400 From: Joey Hess <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: bad descriptions X-Reportbug-Version: 1.15 X-Mailer: reportbug 1.15 Date: Thu, 03 May 2001 22:20:50 -0400 Message-Id: <[EMAIL PROTECTED]> Sender: Joey Hess <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] Package: libgcc0 Version: N/A; reported 2001-05-03 Severity: normal libgcc0 - Shared libgcc. That is a pretty bad peice of work, just barely borderline for a short description. It even repeats the base of the package name in the descripotion, a no-no. Shared libgcc. For an extended, aka "long" description, that sucks rocks (through pipettes). -- System Information Debian Release: testing/unstable Architecture: i386 Kernel: Linux silk 2.4.3 #2 Wed Apr 25 18:53:02 EDT 2001 i686 --------------------------------------- Received: (at 96262-done) by bugs.debian.org; 27 May 2001 22:10:17 +0000 >From [EMAIL PROTECTED] Sun May 27 17:10:17 2001 Return-path: <[EMAIL PROTECTED]> Received: from mail.cs.tu-berlin.de [130.149.17.13] (root) by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 1548jm-0005Ir-00; Sun, 27 May 2001 17:10:14 -0500 Received: from bolero.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.19.1]) by mail.cs.tu-berlin.de (8.9.3/8.9.3) with ESMTP id AAA03363; Mon, 28 May 2001 00:08:35 +0200 (MET DST) Received: (from [EMAIL PROTECTED]) by bolero.cs.tu-berlin.de (8.9.3+Sun/8.9.3) id AAA01795; Mon, 28 May 2001 00:08:35 +0200 (MEST) From: Matthias Klose <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 28 May 2001 00:08:35 +0200 (MEST) To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: fixed bugs in gcc-3.0 (3.0.ds6-0pre010526) X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <[EMAIL PROTECTED]> Delivered-To: [EMAIL PROTECTED] gcc-3.0 (3.0.ds6-0pre010526) unstable; urgency=high * Urgency "high" for replacing the gcc-3.0 snapshots in testing, which now are incompatile due to the changed ABIs. * Upstream begins tagging with "gcc-3_0_pre_2001mmdd". * Tighten dependencies to install only binary packages derived from one source (#98851). Tighten libc6-dev dependency to match libc6. gcc-3.0 (3.0.ds6-0pre010525) unstable; urgency=low * ATTENTION: The ABI (exception handling) changed. No upgrade path from earlier snapshots (you had been warned in the postinst ...) Closing #93597, #94576, #96448, #96461. You have to rebuild * HELP is appreciated for scanning the Debian BTS and sending followups to bug reports!!! * Should we name debian gcc uploads? What about a "still seeking g++ maintainer" upload? * Fixed in gcc-3.0: #97030 * Update patches for recent (010525) CVS sources. * Make check depend on build target (fakeroot problmes). * debian/rules.d/binary-libgcc.mk: new file, build first. * Free memory detection on the hurd for running the testsuite. * Update debhelper build dependency. * libstdc++-doc: Include doxygen generated docs. * Fix boring packaging bugs, too tired for appropriate changelogs ... #93343, #96348, #96262, #97134, #97905, #96451, #95812, #93157 * Fixed bugs: #87000.