Your message dated Wed, 20 Apr 2005 21:32:20 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#305055: fixed in dmapi 2.2.1-1
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; 17 Apr 2005 17:24:44 +0000
>From [EMAIL PROTECTED] Sun Apr 17 10:24:44 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail-out.m-online.net [212.18.0.9] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DNDVj-0008TK-00; Sun, 17 Apr 2005 10:24:44 -0700
Received: from mail.m-online.net (svr20.m-online.net [192.168.3.148])
        by mail-out.m-online.net (Postfix) with ESMTP id 8B7D2810F;
        Sun, 17 Apr 2005 19:24:42 +0200 (CEST)
Received: from atari.stigge.org (ppp-82-135-71-67.mnet-online.de [82.135.71.67])
        by mail.m-online.net (Postfix) with ESMTP id 3ACB26BDBF;
        Sun, 17 Apr 2005 19:24:38 +0200 (CEST)
Received: from [192.168.5.99] (localhost [127.0.0.1])
        by atari.stigge.org (Postfix) with ESMTP id 2E718100442A3;
        Sun, 17 Apr 2005 19:24:37 +0200 (CEST)
From: Roland Stigge <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: dmapi: FTBFS: parse error in xfs/xfs_fs.h
Message-Id: <[EMAIL PROTECTED]>
Date: Sun, 17 Apr 2005 19:24:37 +0200 (CEST)
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: dmapi
Version: 2.2.0-1
Severity: serious

Hi,

building the package dmapi in a clean sid build environment
(with pbuilder) on i386 results in:

=========================================================================
[...]
 gcc -O1 -g -DNDEBUG -funsigned-char -Wall -I../include -DVERSION=\"2.2.0\" 
-DLOCALEDIR=\"/usr/share/locale\" -DPACKAGE=\"dmapi\" -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -fno-strict-aliasing -c dm_event.c -o 
dm_event.o >/dev/null 2>&1
/usr/bin/libtool --mode=compile gcc -O1 -g -DNDEBUG -funsigned-char -Wall 
-I../include -DVERSION=\"2.2.0\" -DLOCALEDIR=\"/usr/share/locale\" 
-DPACKAGE=\"dmapi\" -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64   -D_REENTRANT 
-fno-strict-aliasing -c dm_handle.c
 gcc -O1 -g -DNDEBUG -funsigned-char -Wall -I../include -DVERSION=\"2.2.0\" 
-DLOCALEDIR=\"/usr/share/locale\" -DPACKAGE=\"dmapi\" -D_GNU_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -fno-strict-aliasing -c dm_handle.c  -fPIC 
-DPIC -o .libs/dm_handle.o
In file included from dm_handle.c:43:
/usr/include/xfs/xfs_fs.h:319: error: parse error before '*' token
/usr/include/xfs/xfs_fs.h:321: error: parse error before '*' token
/usr/include/xfs/xfs_fs.h:322: error: parse error before '*' token
/usr/include/xfs/xfs_fs.h:323: error: parse error before '}' token
/usr/include/xfs/xfs_fs.h:350: error: variable or field `__user' declared void
/usr/include/xfs/xfs_fs.h:350: error: parse error before '*' token
/usr/include/xfs/xfs_fs.h:352: error: parse error before '*' token
/usr/include/xfs/xfs_fs.h:354: error: parse error before '*' token
/usr/include/xfs/xfs_fs.h:355: error: parse error before '*' token
/usr/include/xfs/xfs_fs.h:356: error: parse error before '}' token
/usr/include/xfs/xfs_fs.h:366: error: field `hreq' has incomplete type
/usr/include/xfs/xfs_fs.h:367: error: parse error before '*' token
/usr/include/xfs/xfs_fs.h:375: error: field `hreq' has incomplete type
/usr/include/xfs/xfs_fs.h:379: error: variable or field `__user' declared void
/usr/include/xfs/xfs_fs.h:379: error: parse error before '*' token
/usr/include/xfs/xfs_fs.h:385: error: variable or field `__user' declared void
/usr/include/xfs/xfs_fs.h:385: error: parse error before '*' token
/usr/include/xfs/xfs_fs.h:386: error: parse error before '*' token
/usr/include/xfs/xfs_fs.h:389: error: parse error before '}' token
/usr/include/xfs/xfs_fs.h:392: error: field `hreq' has incomplete type
/usr/include/xfs/xfs_fs.h:394: error: field `__user' has incomplete type
/usr/include/xfs/xfs_fs.h:394: error: parse error before '*' token
make[2]: *** [dm_handle.lo] Error 1
make[1]: *** [default] Error 2
make[1]: Leaving directory `/tmp/buildd/dmapi-2.2.0'
make: *** [built] Error 2
=========================================================================

Thanks for considering.


--
DARTS - Debian Archive Regression Test Suite
http://darts.alioth.debian.org/

Please note that this report has not been generated fully automatically.
DARTS just helped finding the problem.

---------------------------------------
Received: (at 305055-close) by bugs.debian.org; 21 Apr 2005 01:41:53 +0000
>From [EMAIL PROTECTED] Wed Apr 20 18:41:53 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 1DOQhV-0001wb-00; Wed, 20 Apr 2005 18:41:53 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DOQYG-0005uF-00; Wed, 20 Apr 2005 21:32:20 -0400
From: Nathan Scott <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#305055: fixed in dmapi 2.2.1-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 20 Apr 2005 21:32:20 -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: dmapi
Source-Version: 2.2.1-1

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

dmapi_2.2.1-1.dsc
  to pool/main/d/dmapi/dmapi_2.2.1-1.dsc
dmapi_2.2.1-1.tar.gz
  to pool/main/d/dmapi/dmapi_2.2.1-1.tar.gz
libdm0-dev_2.2.1-1_i386.deb
  to pool/main/d/dmapi/libdm0-dev_2.2.1-1_i386.deb
libdm0_2.2.1-1_i386.deb
  to pool/main/d/dmapi/libdm0_2.2.1-1_i386.deb



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.
Nathan Scott <[EMAIL PROTECTED]> (supplier of updated dmapi 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, 29 Sep 2004 11:28:20 +1000
Source: dmapi
Binary: libdm0 libdm0-dev
Architecture: source i386
Version: 2.2.1-1
Distribution: unstable
Urgency: low
Maintainer: Nathan Scott <[EMAIL PROTECTED]>
Changed-By: Nathan Scott <[EMAIL PROTECTED]>
Description: 
 libdm0     - Data Management API runtime environment
 libdm0-dev - Data Management API static libraries and headers
Closes: 305055
Changes: 
 dmapi (2.2.1-1) unstable; urgency=low
 .
   * New upstream release (closes: #305055)
Files: 
 3883292f470fcdb32f947076d79aee68 531 admin optional dmapi_2.2.1-1.dsc
 66e16cb052a5142229e9b8997589c2b3 47658 admin optional dmapi_2.2.1-1.tar.gz
 1b995049fc5d6f98314f3dad3d26db72 15480 devel extra libdm0-dev_2.2.1-1_i386.deb
 2d0c728f2a398f2477b870a67592b756 12322 libs optional libdm0_2.2.1-1_i386.deb

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

iD8DBQFCZv20m8fl3HSIa2MRAqTxAJ4t+xqW3qBAWXMtBG8eFIBRnw8l9wCdE1jB
c9Tb34AXCg/EhC+YWZ6z9Tg=
=dovR
-----END PGP SIGNATURE-----


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

Reply via email to