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

Format: 1.7
Date: Wed, 10 Jan 2007 20:35:22 -0800
Source: fuse
Binary: libfuse2 libfuse-dev fuse-utils
Architecture: source i386
Version: 2.5.3-4.2
Distribution: unstable
Urgency: low
Maintainer: Bartosz Fenski <[EMAIL PROTECTED]>
Changed-By: Jurij Smakov <[EMAIL PROTECTED]>
Description: 
 fuse-utils - Filesystem in USErspace (utilities)
 libfuse-dev - Filesystem in USErspace (development files)
 libfuse2   - Filesystem in USErspace library
Closes: 404904
Changes: 
 fuse (2.5.3-4.2) unstable; urgency=low
 .
   * Non-maintainer upload (with maintainer's approval).
   * Ensure the correct alignment of the ccmsg array in receive_fd()
     from lib/mount.c by declaring it as size_t instead of char and
     adjusting the size accordingly. This resolves the issue of
     sshfs crashing with SIGBUS on sparc. Thanks to Sebastian Fontius
     for debugging and testing, and to Miklos Szeredi for the patch.
     (closes: #404904)
Files: 
 31a5377caf6d9586f4720fd0fe506921 605 libs optional fuse_2.5.3-4.2.dsc
 cc680341c64f687ba4b2ebc503640c48 7937 libs optional fuse_2.5.3-4.2.diff.gz
 8f8b162c67c4bfbc82237461ed465e43 56646 utils optional 
fuse-utils_2.5.3-4.2_i386.deb
 56d012903f08415d90d87796cdb92bb4 93692 libdevel optional 
libfuse-dev_2.5.3-4.2_i386.deb
 ebe1ae7ab70b8521dcbe19d838f08560 50416 libs optional 
libfuse2_2.5.3-4.2_i386.deb

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

iD8DBQFFpcH0jjectMmeA8wRAizXAJ9HplfBJp4YAQjVlzm2BhMHZlfvJgCcC9Tk
mj7bQz9fTtn5mD4F2DicsRI=
=wzh7
-----END PGP SIGNATURE-----


Accepted:
fuse-utils_2.5.3-4.2_i386.deb
  to pool/main/f/fuse/fuse-utils_2.5.3-4.2_i386.deb
fuse_2.5.3-4.2.diff.gz
  to pool/main/f/fuse/fuse_2.5.3-4.2.diff.gz
fuse_2.5.3-4.2.dsc
  to pool/main/f/fuse/fuse_2.5.3-4.2.dsc
libfuse-dev_2.5.3-4.2_i386.deb
  to pool/main/f/fuse/libfuse-dev_2.5.3-4.2_i386.deb
libfuse2_2.5.3-4.2_i386.deb
  to pool/main/f/fuse/libfuse2_2.5.3-4.2_i386.deb


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

Reply via email to