Your message dated Tue, 01 Jun 2010 09:54:00 +0000
with message-id <[email protected]>
and subject line Bug#565037: fixed in mhddfs 0.1.31-1
has caused the Debian Bug report #565037,
regarding mhddfs: ftbfs with gcc-4.5
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.)


-- 
565037: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565037
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mhddfs
Version: 0.1.28-1
Severity: normal
Tags: sid
User: [email protected]
Usertags: ftbfs-gcc-4.5

The package fails to build in a test rebuild on at least amd64 with
gcc-4.5/g++-4.5, but succeeds to build with gcc-4.4/g++-4.4.
For the compiler version used, see:
http://lists.debian.org/debian-devel/2010/01/msg00230.html

The full build log can be found at:
http://people.debian.org/~lucas/logs/2010/01/08b/mhddfs_0.1.28-1_lsid64b.buildlog
The last lines of the build log are cwat the end of this report.

The reason of the build failure is likely in the package (compiler or
linker message found in the build log), if this turns out as a gcc bug,
please reassign to the gcc-4.5 package. If the build ends with a
message "confused by earlier errors, bailing out", please
ignore it for now; these compiler errors are filed separately.


[...]
make clean
make[1]: Entering directory 
`/build/user-mhddfs_0.1.28-1-amd64-YXuPfx/mhddfs-0.1.28'
rm -fr obj mhddfs pwrite_test statvfs rename
/bin/sh: fusermount: not found
fusermount -u rename-test || true
rm -fr rename-test/mnt
make[1]: Leaving directory 
`/build/user-mhddfs_0.1.28-1-amd64-YXuPfx/mhddfs-0.1.28'
rm -f build-stamp
dh_clean 
 dpkg-source -b mhddfs-0.1.28
dpkg-source: info: using source format `1.0'
dpkg-source: info: building mhddfs using existing mhddfs_0.1.28.orig.tar.gz
dpkg-source: info: building mhddfs in mhddfs_0.1.28-1.diff.gz
dpkg-source: warning: diff 
`/build/user-mhddfs_0.1.28-1-amd64-YXuPfx/mhddfs_0.1.28-1.diff.gz.new.D_cFqw' 
doesn't contain any patch
dpkg-source: info: building mhddfs in mhddfs_0.1.28-1.dsc
 debian/rules build
dh_testdir
make
make[1]: Entering directory 
`/build/user-mhddfs_0.1.28-1-amd64-YXuPfx/mhddfs-0.1.28'
mkdir -p obj
touch obj/obj-stamp
gcc -Wall -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse   -DFUSE_USE_VERSION=26 
-MMD -c src/debug.c -o obj/debug.o
gcc -Wall -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse   -DFUSE_USE_VERSION=26 
-MMD -c src/flist.c -o obj/flist.o
gcc -Wall -D_FILE_OFFSET_BITS=64 -I/usr/include/fuse   -DFUSE_USE_VERSION=26 
-MMD -c src/main.c -o obj/main.o
src/main.c:34:24: fatal error: attr/xattr.h: No such file or directory
compilation terminated.
make[1]: *** [obj/main.o] Error 1
make[1]: Leaving directory 
`/build/user-mhddfs_0.1.28-1-amd64-YXuPfx/mhddfs-0.1.28'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2



--- End Message ---
--- Begin Message ---
Source: mhddfs
Source-Version: 0.1.31-1

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

mhddfs_0.1.31-1.diff.gz
  to main/m/mhddfs/mhddfs_0.1.31-1.diff.gz
mhddfs_0.1.31-1.dsc
  to main/m/mhddfs/mhddfs_0.1.31-1.dsc
mhddfs_0.1.31-1_amd64.deb
  to main/m/mhddfs/mhddfs_0.1.31-1_amd64.deb
mhddfs_0.1.31.orig.tar.gz
  to main/m/mhddfs/mhddfs_0.1.31.orig.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.
Dmitry E. Oboukhov <[email protected]> (supplier of updated mhddfs 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: RIPEMD160

Format: 1.8
Date: Tue, 01 Jun 2010 12:07:00 +0400
Source: mhddfs
Binary: mhddfs
Architecture: source amd64
Version: 0.1.31-1
Distribution: unstable
Urgency: low
Maintainer: Dmitry E. Oboukhov <[email protected]>
Changed-By: Dmitry E. Oboukhov <[email protected]>
Description: 
 mhddfs     - file system for unifying several mount points into one
Closes: 512649 565037 580785
Changes: 
 mhddfs (0.1.31-1) unstable; urgency=low
 .
   * Fixed statvfs if a few shares are placed onto one device, closes: #580785.
   * Added libattr1-dev in B-D, fixed FTBFS, closes: #565037.
   * Closes unreproducible bugreport (a few months passed), closes: #512649.
Checksums-Sha1: 
 50dd7c532933d5b21ec8d4aed8f6673d326876f0 1055 mhddfs_0.1.31-1.dsc
 8ebfd201c2347bf6a3b9bf4f40de9f3a3b6d2983 38436 mhddfs_0.1.31.orig.tar.gz
 9cb490760c7e9f952182259d4057e91390ea42da 20 mhddfs_0.1.31-1.diff.gz
 9cbbddd98b64d44a990cfbafcba165f8221b5a54 25116 mhddfs_0.1.31-1_amd64.deb
Checksums-Sha256: 
 b661f504921552cac6634854679a8b9c21b9f146657e392857408d9d88080951 1055 
mhddfs_0.1.31-1.dsc
 aeb1c1316b7191bfcad0e5bc017332c7401767fd9708ce2e4c4e04dad572468d 38436 
mhddfs_0.1.31.orig.tar.gz
 2bcf5acdf3e9c2ce7dfeec8e602a700170cfcdb30d04ee7a34703ced82020cf4 20 
mhddfs_0.1.31-1.diff.gz
 6e4ec3cf8d7460940abbf5d83fe92f3cd4f5f56303eec6a39de485d7588ca499 25116 
mhddfs_0.1.31-1_amd64.deb
Files: 
 3fd0fd92c7e811f41927f7d5762bf2c9 1055 utils extra mhddfs_0.1.31-1.dsc
 04bc37989cdab0dfbb65c0d3d616ed29 38436 utils extra mhddfs_0.1.31.orig.tar.gz
 402eb748321a571ed09251605a1312e6 20 utils extra mhddfs_0.1.31-1.diff.gz
 68392326289f0984b6f1fa476605a510 25116 utils extra mhddfs_0.1.31-1_amd64.deb

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

iEYEAREDAAYFAkwEwtEACgkQq4wAz/jiZTcZeQCgn0BmjRA6Q/Y99m2wBDQEbFyd
05cAoJYHOLEeebfmxY5VW8bDFIP9A9uE
=xsl5
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to