Your message dated Fri, 07 Mar 2008 11:17:03 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#465128: fixed in btrfs-tools 0.13-2
has caused the Debian Bug report #465128,
regarding btrfs-tools_0.12-1(ia64/unstable): FTBFS: lacking 64-bit support?
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
465128: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=465128
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: btrfs-tools
Version: 0.12-1
Severity: serious

There was an error while trying to autobuild your package:

> Automatic build of btrfs-tools_0.12-1 on mundy by sbuild/ia64 98
> Build started at 20080210-1301

[...]

> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 5), uuid-dev

[...]

> ls btrfsctl.c
> btrfsctl.c
> gcc -Wp,-MMD,./.btrfsctl.o.d,-MT,btrfsctl.o -Wall -fno-strict-aliasing 
> -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -g -Werror -c btrfsctl.c
> gcc -g -Werror -o btrfsctl btrfsctl.o 
> ls ctree.c
> ctree.c
> gcc -Wp,-MMD,./.ctree.o.d,-MT,ctree.o -Wall -fno-strict-aliasing 
> -D_FILE_OFFSET_BITS=64 -D_FORTIFY_SOURCE=2 -g -Werror -c ctree.c
> cc1: warnings being treated as errors
> ctree.c: In function 'btrfs_cow_block':
> ctree.c:231: warning: format '%Lu' expects type 'long long unsigned int', but 
> argument 3 has type 'u64'
> ctree.c:231: warning: format '%Lu' expects type 'long long unsigned int', but 
> argument 4 has type 'u64'
> make[1]: *** [ctree.o] Error 1
> make[1]: Leaving directory `/build/buildd/btrfs-tools-0.12'
> make: *** [build-stamp] Error 2
> dpkg-buildpackage: failure: debian/rules build gave error exit status 2

A full build log can be found at:
http://buildd.debian.org/build.php?arch=ia64&pkg=btrfs-tools&ver=0.12-1




--- End Message ---
--- Begin Message ---
Source: btrfs-tools
Source-Version: 0.13-2

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

btrfs-tools_0.13-2.diff.gz
  to pool/main/b/btrfs-tools/btrfs-tools_0.13-2.diff.gz
btrfs-tools_0.13-2.dsc
  to pool/main/b/btrfs-tools/btrfs-tools_0.13-2.dsc
btrfs-tools_0.13-2_i386.deb
  to pool/main/b/btrfs-tools/btrfs-tools_0.13-2_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.
Daniel Baumann <[EMAIL PROTECTED]> (supplier of updated btrfs-tools 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: Fri,  7 Mar 2008 12:04:00 +0100
Source: btrfs-tools
Binary: btrfs-tools
Architecture: source i386
Version: 0.13-2
Distribution: unstable
Urgency: medium
Maintainer: Daniel Baumann <[EMAIL PROTECTED]>
Changed-By: Daniel Baumann <[EMAIL PROTECTED]>
Description: 
 btrfs-tools - Checksumming Copy on Write Filesystem
Closes: 465128
Changes: 
 btrfs-tools (0.13-2) unstable; urgency=medium
 .
   * Excluding alpha and ia64 from architectures, doesn't build there
     (Closes: #465128).
Files: 
 fd1188d20bb1fb1b8b65d290ce5051c0 687 admin optional btrfs-tools_0.13-2.dsc
 702892059d9235f5f9ebf2a933a89fec 2447 admin optional btrfs-tools_0.13-2.diff.gz
 64332383a11ae2307062117fc4c5ff50 136054 admin optional 
btrfs-tools_0.13-2_i386.deb

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

iD8DBQFH0SFi+C5cwEsrK54RAvzPAKDcfgMp9EVcl58Z5+Nlhf3gq8sh0ACgkVJ1
uA+Pq8C2A+56FEKCYMGuCMk=
=MLcJ
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to