Your message dated Tue, 19 Feb 2002 00:33:52 +0100
with message-id <[EMAIL PROTECTED]>
and subject line fixed in the current pinfo version
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.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 10 Oct 2001 10:36:37 +0000
>From [EMAIL PROTECTED] Wed Oct 10 05:36:37 2001
Return-path: <[EMAIL PROTECTED]>
Received: from (natura.oskuro.net) [213.96.69.115]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 15rGj7-00077h-00; Wed, 10 Oct 2001 05:36:37 -0500
Received: from nubol.amalur.nat (nubol.amalur.nat [192.168.1.3])
by natura.oskuro.net (Postfix) with ESMTP
id 86351279F0; Wed, 10 Oct 2001 12:36:07 +0200 (CEST)
Received: by nubol.amalur.nat (Postfix, from userid 1000)
id 6012870A3EA; Wed, 10 Oct 2001 12:36:12 +0200 (CEST)
From: Jordi Mallach <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: cpp-2.95-doc: info cpp doesn't work
X-Reportbug-Version: 1.30
X-Mailer: reportbug 1.30
Date: Wed, 10 Oct 2001 12:36:12 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Package: cpp-2.95-doc
Version: 1:2.95.4-0.011006
Severity: normal
Hello,
If you do "pinfo gcc", you get the gcc-2.95 manual pages, but this doesn't
happen for cpp too. If I do "pinfo gcc", I just get the manual page.
The bug about cpp-2.95-doc providing cpp-doc could apply here too, as in Gcc.
Thanks,
Jordi
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux nubol 2.4.10-xfs #1 Wed Sep 26 21:27:00 CEST 2001 i686
Locale: LANG=en_US, LC_CTYPE=en_US
---------------------------------------
Received: (at 115128-done) by bugs.debian.org; 18 Feb 2002 23:35:00 +0000
>From [EMAIL PROTECTED] Mon Feb 18 17:35:00 2002
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 16cxJD-0006kN-00; Mon, 18 Feb 2002 17:35:00 -0600
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 AAA07059
for <[EMAIL PROTECTED]>; Tue, 19 Feb 2002 00:33:53 +0100 (MET)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.11.6+Sun/8.9.3) id g1INXqj07686;
Tue, 19 Feb 2002 00:33:52 +0100 (MET)
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: Tue, 19 Feb 2002 00:33:52 +0100
To: [EMAIL PROTECTED]
Subject: fixed in the current pinfo version
X-Mailer: VM 6.89 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid
Delivered-To: [EMAIL PROTECTED]
pinfo now has the same behaviour as info (in this respect).
