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

Format: 1.7
Date: Thu,  6 Jul 2006 19:37:58 +0200
Source: nfs-utils
Binary: nhfsstone nfs-kernel-server nfs-common
Architecture: source i386
Version: 1:1.0.8+1.0.9pre1-2
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
Closes: 376976
Changes: 
 nfs-utils (1:1.0.8+1.0.9pre1-2) unstable; urgency=low
 .
   * Provide LSB dependency information in the nfs-common and nfs-kernel-server
     init scripts; replaces the obsolete chkconfig info. (Closes: #376976)
   * Update the long descriptions.
Files: 
 4628bbae6745f67025ab6643440c545a 854 net standard 
nfs-utils_1.0.8+1.0.9pre1-2.dsc
 0cebd536f1f9850139f9f3a7eaee914e 21919 net standard 
nfs-utils_1.0.8+1.0.9pre1-2.diff.gz
 3a132f0a5df0aa605897c86a7308201f 116852 net optional 
nfs-kernel-server_1.0.8+1.0.9pre1-2_i386.deb
 7feb2c5cd7653a13c8f3113536cb9e53 136322 net standard 
nfs-common_1.0.8+1.0.9pre1-2_i386.deb
 f06393768999edb9bf5ceca72b25053a 58922 net extra 
nhfsstone_1.0.8+1.0.9pre1-2_i386.deb

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

iD8DBQFErVK5XKRQ3lK3SH4RAns9AJ4jYzo/a741UPhz2fIlt9KHER2DBgCfe18b
mKPzew7OvdgsIuPcXkHukrM=
=WXbW
-----END PGP SIGNATURE-----


Accepted:
nfs-common_1.0.8+1.0.9pre1-2_i386.deb
  to pool/main/n/nfs-utils/nfs-common_1.0.8+1.0.9pre1-2_i386.deb
nfs-kernel-server_1.0.8+1.0.9pre1-2_i386.deb
  to pool/main/n/nfs-utils/nfs-kernel-server_1.0.8+1.0.9pre1-2_i386.deb
nfs-utils_1.0.8+1.0.9pre1-2.diff.gz
  to pool/main/n/nfs-utils/nfs-utils_1.0.8+1.0.9pre1-2.diff.gz
nfs-utils_1.0.8+1.0.9pre1-2.dsc
  to pool/main/n/nfs-utils/nfs-utils_1.0.8+1.0.9pre1-2.dsc
nhfsstone_1.0.8+1.0.9pre1-2_i386.deb
  to pool/main/n/nfs-utils/nhfsstone_1.0.8+1.0.9pre1-2_i386.deb


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

Reply via email to