Your message dated Wed, 19 Jan 2005 19:03:11 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#291269: fixed in libpmount 0.0.5
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; 19 Jan 2005 19:29:00 +0000
>From [EMAIL PROTECTED] Wed Jan 19 11:29:00 2005
Return-path: <[EMAIL PROTECTED]>
Received: from europa.telenet-ops.be [195.130.132.60] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CrLVj-00055A-00; Wed, 19 Jan 2005 11:29:00 -0800
Received: from localhost (localhost.localdomain [127.0.0.1])
        by europa.telenet-ops.be (Postfix) with SMTP id 8C2AC19830B
        for <[EMAIL PROTECTED]>; Wed, 19 Jan 2005 20:28:58 +0100 (MET)
Received: from Q.roeckx.be (dD5775FD9.access.telenet.be [213.119.95.217])
        by europa.telenet-ops.be (Postfix) with ESMTP id 6068D198308
        for <[EMAIL PROTECTED]>; Wed, 19 Jan 2005 20:28:58 +0100 (MET)
Received: by Q.roeckx.be (Postfix, from userid 501)
        id E68FB26136; Wed, 19 Jan 2005 20:28:57 +0100 (CET)
Date: Wed, 19 Jan 2005 20:28:57 +0100
From: Kurt Roeckx <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: pmount: FTBFS: Block device required.
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: pmount
Version: 0.0.4
Severity: serious

Hi,

Your package is failing to build with the following error:
mke2fs 1.36-rc2 (11-Jan-2005)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
128 inodes, 1024 blocks
51 blocks (4.98%) reserved for the super user
First data block=1
1 block group
8192 blocks per group, 8192 fragments per group
128 inodes per group

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 22 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
pmount failed: Block device required
make: *** [build-stamp] Error 255


kurt


---------------------------------------
Received: (at 291269-close) by bugs.debian.org; 20 Jan 2005 00:05:37 +0000
>From [EMAIL PROTECTED] Wed Jan 19 16:05:36 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 1CrPpQ-00057T-00; Wed, 19 Jan 2005 16:05:36 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1CrPn5-0002v1-00; Wed, 19 Jan 2005 19:03:11 -0500
From: Robert Millan <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#291269: fixed in libpmount 0.0.5
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 19 Jan 2005 19:03:11 -0500
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: libpmount
Source-Version: 0.0.5

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

libpmount-dev_0.0.5_i386.deb
  to pool/main/libp/libpmount/libpmount-dev_0.0.5_i386.deb
libpmount0.0_0.0.5_i386.deb
  to pool/main/libp/libpmount/libpmount0.0_0.0.5_i386.deb
libpmount_0.0.5.dsc
  to pool/main/libp/libpmount/libpmount_0.0.5.dsc
libpmount_0.0.5.tar.gz
  to pool/main/libp/libpmount/libpmount_0.0.5.tar.gz



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.
Robert Millan <[EMAIL PROTECTED]> (supplier of updated libpmount 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: Thu, 20 Jan 2005 00:23:52 +0100
Source: libpmount
Binary: libpmount0.0 libpmount-dev
Architecture: source i386
Version: 0.0.5
Distribution: unstable
Urgency: low
Maintainer: Robert Millan <[EMAIL PROTECTED]>
Changed-By: Robert Millan <[EMAIL PROTECTED]>
Description: 
 libpmount-dev - Portable mount library, development files
 libpmount0.0 - Portable mount library, shared object
Closes: 291269
Changes: 
 libpmount (0.0.5) unstable; urgency=low
 .
   * rules: Disable testsuite.  (Closes: #291269)
Files: 
 ae506c4b1d70230a34f303202d66968c 521 libs optional libpmount_0.0.5.dsc
 90883910835334573bc72bd665ce4b99 9306 libs optional libpmount_0.0.5.tar.gz
 b4224ef5623314dd8a086802b340b17f 5242 libdevel optional 
libpmount-dev_0.0.5_i386.deb
 56b80a2735017454dccdbff42c484018 5810 libs optional libpmount0.0_0.0.5_i386.deb

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

iD8DBQFB7vUKC19io6rUCv8RAu3pAJ9gn0sgikO5AbyujklW9ancLyt4FwCdEPwq
xaFl9vEguF9eYIUjb6pvoyE=
=sPYI
-----END PGP SIGNATURE-----


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

Reply via email to