Your message dated Sun, 26 Aug 2001 09:38:54 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fixed in gcc-3.0 3.0.2ds0-0pre010825
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; 2 Jul 2001 00:23:01 +0000
>From [EMAIL PROTECTED] Sun Jul 01 19:23:01 2001
Return-path: <[EMAIL PROTECTED]>
Received: from hardy.math.okstate.edu [::ffff:139.78.112.2] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 15GrUT-00008J-00; Sun, 01 Jul 2001 19:23:01 -0500
Received: from emerald ([EMAIL PROTECTED] [139.78.67.252])
        by hardy.math.okstate.edu (8.9.3/8.9.3) with ESMTP id TAA22606;
        Sun, 1 Jul 2001 19:16:36 -0500
Received: from bab by emerald with local (Exim 3.22 #1 (Debian))
        id 15GrTw-0003bz-00; Sun, 01 Jul 2001 19:22:28 -0500
From: Ben Burton <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: fastjar: Please include man page
X-Reportbug-Version: 1.18
X-Mailer: reportbug 1.18
Date: Sun, 01 Jul 2001 19:22:26 -0500
Message-Id: <[EMAIL PROTECTED]>
Sender: Ben Burton <[EMAIL PROTECTED]>
X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED]
  using "From" header
Delivered-To: [EMAIL PROTECTED]

Package: fastjar
Version: 1:3.0-3
Severity: normal

Hi.  Would it be possible to add a man page for fastjar?

Thanks - Ben.

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux emerald 2.4.4-686 #1 Sun Apr 29 12:22:40 EST 2001 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages fastjar depends on:
ii  libc6                         2.2.3-6    GNU C Library: Shared libraries an


---------------------------------------
Received: (at 103051-done) by bugs.debian.org; 26 Aug 2001 07:42:03 +0000
>From [EMAIL PROTECTED] Sun Aug 26 02:42:03 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 15auYV-0002jU-00; Sun, 26 Aug 2001 02:42:03 -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 JAA26692;
        Sun, 26 Aug 2001 09:38:55 +0200 (MET DST)
Received: (from [EMAIL PROTECTED])
        by bolero.cs.tu-berlin.de (8.10.2+Sun/8.9.3) id f7Q7ctq20280;
        Sun, 26 Aug 2001 09:38:55 +0200 (MEST)
From: Matthias Klose <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <[EMAIL PROTECTED]>
Date: Sun, 26 Aug 2001 09:38:54 +0200
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: fixed in gcc-3.0 3.0.2ds0-0pre010825
X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]

gcc-3.0 (1:3.0.2ds0-0pre010825) unstable; urgency=low

  * Update to CVS sources (010825).
  * Add libc6-dev-sparc64 to gcc-3.0-sparc64 and to sparc build dependencies.
  * Remove conflicts on egcc package (closes: #109718).
  * Fix gcc-3.0-nof dependency.
  * s390 patches against gcc-3.0.1 (Gerhard Tonn).
  * debian/control: Require binutils (>= 2.11.90.0.27)

gcc-3.0 (1:3.0.1ds3-1) unstable; urgency=low

  * Final gcc-3.0.1 release.
  * Changed upstream: default of -flimit-inline is 600 (closes: #106716).
  * Add fastjar man page (submitted by "The Missing Man Pages Project",
    http://www.netmeister.org/misc/m2p2i/) (closes: #103051).
  * Fixed in last upload as well: #105246.
  * debian/patches/cpp-memory-leak.dpatch: New patch
  * Disable installation of shared libgcc on s390 (Gerhard Tonn).


Reply via email to