+nfs-utils (1:1.0.9-8) unstable; urgency=medium
+
+ * In the init scripts, don't attempt to use pid files; the daemons don't
+ leave them, and --make-pidfile gives wrong pid files since all the daemons
+ fork by themselves. Thus, multiple invocations of "start" could leave
+ multiple daemons lying around, which could cause all sorts of problems.
+
+ -- Steinar H. Gunderson <sesse@debian.org> Thu, 17 Aug 2006 17:24:11 +0200
+
+nfs-utils (1:1.0.9-7) unstable; urgency=low
+
+ * New sourceful upload to force rebuild against librpcsecgss3, to get all
+ architectures in sync and make sure rpc.gssd actually has a proper library
+ to link against.
+ * Build-depend against librpcsecgss-dev (>= 0.14-2), since that's when
+ the package name bump happened.
+
+ -- Steinar H. Gunderson <sesse@debian.org> Sat, 12 Aug 2006 19:55:35 +0200
+
+nfs-utils (1:1.0.9-6) unstable; urgency=low
+
+ * Enable idmapd by default if we find an /etc/exports file, as NFSv4 exports
+ need idmapd. (See the init script for the complete reasoning). Also start
+ nfs-common on initial installation of nfs-kernel-server, as we don't want
+ to reboot or restart nfs-common manually just to get idmapd working the
+ first time. (Closes: #381366)
+
+ -- Steinar H. Gunderson <sesse@debian.org> Mon, 7 Aug 2006 21:27:37 +0200
+
nfs-utils (1:1.0.9-5) unstable; urgency=low
* Put rpc.svcgssd back into place; removing it was obviously not what