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

Format: 1.7
Date: Sun, 16 Jul 2006 01:59:13 +0200
Source: nfs-utils
Binary: nhfsstone nfs-kernel-server nfs-common
Architecture: source i386
Version: 1:1.0.9-4
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar <[EMAIL PROTECTED]>
Changed-By: Steinar H. Gunderson <[EMAIL PROTECTED]>
Description: 
 nfs-common - NFS support files common to client and server
 nfs-kernel-server - Kernel NFS server support
 nhfsstone  - NFS benchmark program
Changes: 
 nfs-utils (1:1.0.9-4) unstable; urgency=low
 .
   * Remove versioned dependency on coreutils, as we don't use it indirectly,
     only via ucf (so the dependency should be there). This makes the package
     somewhat easier to backport to sarge.
   * Remove the word "Debian" from our patch against the exports(5) man page,
     as Debian is not the only distribution using these packages.
Files: 
 050ad4d6c1e6c231540011bdab7c126d 805 net standard nfs-utils_1.0.9-4.dsc
 3c52309fcda8a702c23d11d890b94032 20769 net standard nfs-utils_1.0.9-4.diff.gz
 9f8410ec236293f152f974ebbedceeab 122032 net optional 
nfs-kernel-server_1.0.9-4_i386.deb
 e59f91ae25dddb6d551a784463d9f5f2 123094 net standard 
nfs-common_1.0.9-4_i386.deb
 24289086375bf1de7292e7c4334e5153 64216 net extra nhfsstone_1.0.9-4_i386.deb

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

iD8DBQFEuYMvXKRQ3lK3SH4RAsZOAKCpa0Wkqd0m3eIV6Gvw5fukX4I1jgCfQF94
uuSJM4EBmGqycR8ErLn0jFY=
=BK9o
-----END PGP SIGNATURE-----


Accepted:
nfs-common_1.0.9-4_i386.deb
  to pool/main/n/nfs-utils/nfs-common_1.0.9-4_i386.deb
nfs-kernel-server_1.0.9-4_i386.deb
  to pool/main/n/nfs-utils/nfs-kernel-server_1.0.9-4_i386.deb
nfs-utils_1.0.9-4.diff.gz
  to pool/main/n/nfs-utils/nfs-utils_1.0.9-4.diff.gz
nfs-utils_1.0.9-4.dsc
  to pool/main/n/nfs-utils/nfs-utils_1.0.9-4.dsc
nhfsstone_1.0.9-4_i386.deb
  to pool/main/n/nfs-utils/nhfsstone_1.0.9-4_i386.deb


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

Reply via email to