summary |
shortlog |
log |
commit | commitdiff |
tree
raw |
patch |
inline | side by side (from parent 1:
806343c)
libtirpc does not support the old portmapper protocol. (It does
implement the old portmap client library functions, but still uses
rpcbind protocol.) There's no easy way to add fallback support, and
it doesn't look like we can switch between libtirpc and the portmapper
client at run-time. So require use of rpcbind.
+nfs-utils (1:1.2.3-2) UNRELEASED; urgency=low
+
+ * Depend on rpcbind unconditionally, as libtirpc does not support the
+ old portmapper protocol (Closes: #619877)
+
+ -- Ben Hutchings <ben@decadent.org.uk> Fri, 08 Apr 2011 05:12:29 +0100
+
nfs-utils (1:1.2.3-1) unstable; urgency=low
* New upstream release
nfs-utils (1:1.2.3-1) unstable; urgency=low
* New upstream release
Package: nfs-common
Architecture: any
Package: nfs-common
Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, rpcbind | portmap, adduser, ucf, lsb-base (>= 1.3-9ubuntu3), netbase (>= 4.24), initscripts (>= 2.86.ds1-38.1)
+Depends: ${shlibs:Depends}, ${misc:Depends}, rpcbind, adduser, ucf, lsb-base (>= 1.3-9ubuntu3), netbase (>= 4.24), initscripts (>= 2.86.ds1-38.1)
Recommends: python
Provides: nfs-client
Conflicts: nfs-client
Recommends: python
Provides: nfs-client
Conflicts: nfs-client