Your message dated Wed, 01 Jan 2014 01:33:19 +0000
with message-id <e1vyagr-0005j5...@franck.debian.org>
and subject line Bug#733742: fixed in rpcbind 0.2.1-2
has caused the Debian Bug report #733742,
regarding rpcbind: cannot get uid of '': Transport endpoint is not connected
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
733742: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rpcbind
Version: 0.2.1-1
Severity: grave
Justification: renders package unusable

rpcbind doesn't start anymore and blocќs nis, nfs etc.

Falling back to 0.2.0-8 make my sytems running again.

Elimar
-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'stable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13.0-rc6-galadriel-lxtec-amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages rpcbind depends on:
ii  initscripts  2.88dsf-45
ii  insserv      1.14.0-5
ii  libc6        2.17-97
ii  libtirpc1    0.2.2-5
ii  libwrap0     7.6.q-24
ii  lsb-base     4.1+Debian12

rpcbind recommends no packages.

rpcbind suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: rpcbind
Source-Version: 0.2.1-2

We believe that the bug you reported is fixed in the latest version of
rpcbind, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 733...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anibal Monsalve Salazar <ani...@debian.org> (supplier of updated rpcbind 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 01 Jan 2014 11:54:21 +1100
Source: rpcbind
Binary: rpcbind
Architecture: source mipsel
Version: 0.2.1-2
Distribution: unstable
Urgency: low
Maintainer: Anibal Monsalve Salazar <ani...@debian.org>
Changed-By: Anibal Monsalve Salazar <ani...@debian.org>
Description: 
 rpcbind    - converts RPC program numbers into universal addresses
Closes: 733742
Changes: 
 rpcbind (0.2.1-2) unstable; urgency=low
 .
   * Pass "--with-rpcuser=root" to configure
     Closes: #733742
Checksums-Sha1: 
 23194cc9a7ed0b60f1864880178b66167dbbef7a 1794 rpcbind_0.2.1-2.dsc
 c526a831df49036a24d09c73bdc7cec966b165c8 8732 rpcbind_0.2.1-2.debian.tar.bz2
 b788e7792b86cbd20d841c5de8014b77510492d9 38926 rpcbind_0.2.1-2_mipsel.deb
Checksums-Sha256: 
 15da7846040548170197c41a239174e26c6562dba74db29a6042ca6e2c7d6f8f 1794 
rpcbind_0.2.1-2.dsc
 810b35b2b496a4d92db7ba66cf031e8728a63091fb8d83d97e70a14ba36a78b2 8732 
rpcbind_0.2.1-2.debian.tar.bz2
 7e5df12d8f6ecd1f93eb1cdecfe74e42ea387915c19f0cdcd2e0da55687833d9 38926 
rpcbind_0.2.1-2_mipsel.deb
Files: 
 1fb312cf4df8a6dcd4f681bca69d6080 1794 net standard rpcbind_0.2.1-2.dsc
 e0be61ca623e89e93c3b2ccb52e83d46 8732 net standard 
rpcbind_0.2.1-2.debian.tar.bz2
 4b302a32af2dea12a20efb5a85172301 38926 net standard rpcbind_0.2.1-2_mipsel.deb

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

iQIcBAEBCgAGBQJSw2zzAAoJEHxWrP6UeJfYVTQQAJQcqxTMom9W61gm/eZIR9bb
BfzUrwNsdFDDnD+hW6d9tWIRzJ5Plq5fM06ComDqERrGlO59W8mGO9Zx/6+TGMGp
P2lVPN6xhUgME3fyjC39U1pSEhdcePqcwjC51nedx0MAXq7+0kiuYfbQaOKIvbL3
4ef60Cg0XZE4KrV18PoCHZSzCiaDEXKL9dSfZFRwxHkcGilMBu39dCGepUa7wppF
3+/lgkQA0Y4kxU0Ut3WVHVLmc0QAu7QUVRTwF2djWGG4k/P8Jk7ikMB+7lcyG2Lg
HMH/8Ym3vbFLuJDpuUfysNlPiV7ujyZAu4NTL/x6v/SKYkZYkcggFl56Rr8rHJHZ
1nOk9ZifvO5m9bO2iw3NKkgFwSMKAYFlS+Nzl8oZLnT5wkOd2CFSjH5A4s9Qbpw5
xMvXB7BcyHKqHKbDWSKyDQyDm9dEl2qmuigJdXZNnSdLxXf/N8rHHV+Jogmwsou8
LgXoZ/i4aARvETUZLat9Mva2E5ZCS7EOL/ug49QpU5+lam77hR2iANPmkr7Z/ooH
Pdi+IJ9Ny4fVcgNLu34RFmLvVl9jSMHh01+GBewVkaAtPW3dVvqkUyX0hs+z/Ow0
Db+R+EFS7sIgGFhYJyjH8Fc8NVJTBDfVBYATb58zMUP+4lt14lUopuvQiXFEq0oN
5obG1Aiy0hD8jnvjaEz6
=+1iD
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to