Your message dated Wed, 01 Jun 2005 18:32:28 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#311149: fixed in libcommoncpp2 1.3.10-3
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; 29 May 2005 09:36:35 +0000
>From [EMAIL PROTECTED] Sun May 29 02:36:34 2005
Return-path: <[EMAIL PROTECTED]>
Received: from poros.telenet-ops.be [195.130.132.44] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DcKDi-0001Qj-00; Sun, 29 May 2005 02:36:34 -0700
Received: from localhost (localhost.localdomain [127.0.0.1])
        by poros.telenet-ops.be (Postfix) with SMTP id 9EB143BC04D
        for <[EMAIL PROTECTED]>; Sun, 29 May 2005 11:36:33 +0200 (MEST)
Received: from Q.roeckx.be (dD5775FD9.access.telenet.be [213.119.95.217])
        by poros.telenet-ops.be (Postfix) with ESMTP id 903B73BC0D5
        for <[EMAIL PROTECTED]>; Sun, 29 May 2005 11:36:33 +0200 (MEST)
Received: by Q.roeckx.be (Postfix, from userid 501)
        id 5EA7426136; Sun, 29 May 2005 11:36:33 +0200 (CEST)
Date: Sun, 29 May 2005 11:36:33 +0200
From: Kurt Roeckx <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: libcommoncpp2: FTBFS: dh_installdocs: cp: cannot stat `doc/html': No 
such file or directory
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
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: libcommoncpp2
Version: 1.3.10-1
Severity: serious
Tags: sid


Hi,

Your package is failing to build with the following error:
dh_installdocs
cp: cannot stat `doc/html': No such file or directory
dh_installdocs: command returned error code 256
make: *** [binary-arch] Error 1



Kurt


---------------------------------------
Received: (at 311149-close) by bugs.debian.org; 1 Jun 2005 22:39:42 +0000
>From [EMAIL PROTECTED] Wed Jun 01 15:39:42 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DdbsD-00056M-00; Wed, 01 Jun 2005 15:39:42 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DdblE-00073A-00; Wed, 01 Jun 2005 18:32:28 -0400
From: Mark Purcell <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#311149: fixed in libcommoncpp2 1.3.10-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 01 Jun 2005 18:32:28 -0400
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: 

Source: libcommoncpp2
Source-Version: 1.3.10-3

We believe that the bug you reported is fixed in the latest version of
libcommoncpp2, which is due to be installed in the Debian FTP archive:

libcommoncpp2-1.3_1.3.10-3_i386.deb
  to pool/main/libc/libcommoncpp2/libcommoncpp2-1.3_1.3.10-3_i386.deb
libcommoncpp2-dev_1.3.10-3_i386.deb
  to pool/main/libc/libcommoncpp2/libcommoncpp2-dev_1.3.10-3_i386.deb
libcommoncpp2_1.3.10-3.diff.gz
  to pool/main/libc/libcommoncpp2/libcommoncpp2_1.3.10-3.diff.gz
libcommoncpp2_1.3.10-3.dsc
  to pool/main/libc/libcommoncpp2/libcommoncpp2_1.3.10-3.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mark Purcell <[EMAIL PROTECTED]> (supplier of updated libcommoncpp2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed,  1 Jun 2005 22:41:13 +0100
Source: libcommoncpp2
Binary: libcommoncpp2-1.3 libcommoncpp2-dev
Architecture: source i386
Version: 1.3.10-3
Distribution: unstable
Urgency: low
Maintainer: Mark Purcell <[EMAIL PROTECTED]>
Changed-By: Mark Purcell <[EMAIL PROTECTED]>
Description: 
 libcommoncpp2-1.3 - A GNU package for creating portable C++ programs
 libcommoncpp2-dev - Header files and static libraries for Common C++ "2"
Closes: 311149 311397
Changes: 
 libcommoncpp2 (1.3.10-3) unstable; urgency=low
 .
   * Add Conflicts/Replaces: libcommoncpp2-1.0-0c102 (=1.3.10-1) (Closes:
     Bug#311397)
   * Closes: #311149: FTBFS: dh_installdocs: cp: cannot stat `doc/html':
     No such file or directory
     - Add Build-Depends doxygen
Files: 
 e0e6cc20e0be3dc86ca215d84e6d75a3 652 devel optional libcommoncpp2_1.3.10-3.dsc
 beb78fc61afb659408f3748425ead046 16222 devel optional 
libcommoncpp2_1.3.10-3.diff.gz
 30fb030c7bd2e951c704f13de908a2c1 1235702 libdevel optional 
libcommoncpp2-dev_1.3.10-3_i386.deb
 a552c8abe46e30469825c4dc3eb08b1e 225838 libs optional 
libcommoncpp2-1.3_1.3.10-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCnjHtoCzanz0IthIRAoUCAJ42pHwEBKov2kjvL0DVA0Kr/XrTLgCcDBZ/
Gm4jMot4YQt026fGjnFWpfs=
=5ycK
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to