Your message dated Sun, 30 Jan 2005 16:54:22 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#291060: libstdc++6-4.0-doc: cannot install
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; 18 Jan 2005 14:09:56 +0000
>From [EMAIL PROTECTED] Tue Jan 18 06:09:56 2005
Return-path: <[EMAIL PROTECTED]>
Received: from bal.lis.inpg.fr [195.220.21.15]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Cqu3Q-0007Yn-00; Tue, 18 Jan 2005 06:09:56 -0800
Received: from smtpc.lis.inpg.Fr (smtpc.lis.inpg.fr [195.220.21.17])
by bal.lis.inpg.fr (Postfix) with ESMTP id 713383067C2;
Tue, 18 Jan 2005 15:09:21 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
by smtpc.lis.inpg.Fr (Postfix) with ESMTP id 893372C8144;
Tue, 18 Jan 2005 15:09:25 +0100 (CET)
Received: from smtpc.lis.inpg.Fr ([127.0.0.1])
by localhost (smtpc.lis.inpg.fr [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 27812-04; Tue, 18 Jan 2005 15:09:23 +0100 (CET)
Received: from irancy.lis.inpg.fr (irancy.lis.inpg.fr [195.220.21.167])
by smtpc.lis.inpg.Fr (Postfix) with SMTP id B993E2C819D;
Tue, 18 Jan 2005 15:09:13 +0100 (CET)
Received: by irancy.lis.inpg.fr (sSMTP sendmail emulation); Tue, 18 Jan 2005
15:09:11 +0100
From: "Laurent Bonnaud" <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: libstdc++6-4.0-doc: cannot install
X-Mailer: reportbug 3.5
Date: Tue, 18 Jan 2005 15:09:11 +0100
Message-Id: <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at lis.inpg.fr
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: libstdc++6-4.0-doc
Version: 4.0-0pre4
Severity: grave
Justification: renders package unusable
Hi,
here is the problem:
# apt-get install libstdc++6-4.0-doc
[...]
Unpacking libstdc++6-4.0-doc (from .../libstdc++6-4.0-doc_4.0-0pre4_all.deb) ...
dpkg: error processing
/var/cache/apt/archives/libstdc++6-4.0-doc_4.0-0pre4_all.deb (--unpack):
unable to clean up mess surrounding
`./usr/share/doc/gcc-4.0-base/libstdc++/html_user/structstd_1_1tr1_1_1tuple__size_3_01tuple_3_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_'
before installing another version: File name too long
dpkg-deb: subprocess paste killed by signal (Broken pipe)
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
---------------------------------------
Received: (at 291060-done) by bugs.debian.org; 30 Jan 2005 15:54:31 +0000
>From [EMAIL PROTECTED] Sun Jan 30 07:54:31 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail.cs.tu-berlin.de [130.149.17.13] (root)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CvHPD-0001mb-00; Sun, 30 Jan 2005 07:54:31 -0800
Received: from mailhost.cs.tu-berlin.de ([EMAIL PROTECTED] [130.149.17.13])
by mail.cs.tu-berlin.de (8.9.3p2/8.9.3) with ESMTP id QAA13689;
Sun, 30 Jan 2005 16:54:28 +0100 (MET)
Received: from localhost (localhost [127.0.0.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP id 6D0C3F21A;
Sun, 30 Jan 2005 16:54:28 +0100 (MET)
Received: from mailhost.cs.tu-berlin.de ([127.0.0.1])
by localhost (bueno [127.0.0.1]) (amavisd-new, port 10224) with ESMTP
id 29229-31; Sun, 30 Jan 2005 16:54:27 +0100 (MET)
Received: from bolero.cs.tu-berlin.de (bolero.cs.tu-berlin.de [130.149.19.1])
by mailhost.cs.tu-berlin.de (Postfix) with ESMTP;
Sun, 30 Jan 2005 16:54:23 +0100 (MET)
Received: (from [EMAIL PROTECTED])
by bolero.cs.tu-berlin.de (8.12.10+Sun/8.12.8/Submit) id j0UFsM7L015259;
Sun, 30 Jan 2005 16:54:22 +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: Sun, 30 Jan 2005 16:54:22 +0100
To: Laurent Bonnaud <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#291060: libstdc++6-4.0-doc: cannot install
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
X-Mailer: VM 7.03 under 21.4 (patch 6) "Common Lisp" XEmacs Lucid
X-Virus-Scanned: by amavisd-new at cs.tu-berlin.de
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Laurent Bonnaud writes:
> > > # apt-get install libstdc++6-4.0-doc
> > > [...]
> > > Unpacking libstdc++6-4.0-doc (from
> > > .../libstdc++6-4.0-doc_4.0-0pre4_all.deb) ...
> > > dpkg: error processing
> > > /var/cache/apt/archives/libstdc++6-4.0-doc_4.0-0pre4_all.deb (--unpack):
> > > unable to clean up mess surrounding
> > > `./usr/share/doc/gcc-4.0-base/libstdc++/html_user/structstd_1_1tr1_1_1tuple__size_3_01tuple_3_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_class_00_01___null_'
> > > before installing another version: File name too long
> > > dpkg-deb: subprocess paste killed by signal (Broken pipe)
> >
> > are you able to reproduce the failure with the current version in
> > experimental?
>
> No, it is fixed. Thank you !
>
> I'm not closing the bug since I'm not sure if there is still an issue
> with doxygen.
please open another one, as the original problem is fixed.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
