Your message dated Sat, 19 Mar 2022 18:29:02 +0100 with message-id <4b512fde181875e8800a4526d149362b46101e43.camel@decadent.org.uk> and subject line Re: nfs-common: Wrong uid/gid with latest version using NFSv4 has caused the Debian Bug report #644948, regarding nfs-common: Wrong uid/gid with latest version using NFSv4 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 owner@bugs.debian.org immediately.) -- 644948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644948 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: nfs-common: Wrong uid/gid with latest version using NFSv4
- From: "Nils S. Normann" <nilssn@gmail.com>
- Date: Mon, 10 Oct 2011 19:09:03 -0600
- Message-id: <20111011010903.2848.8166.reportbug@Tramp.hjemmenettverk>
Package: nfs-common Version: 1:1.2.5-2 Severity: important After upgrade to nfs-common 1:1.2.5-2 I noticed that uid/gid's are displayed as 'nobody' and 'nogroup' respectively. This is the case checking with both Nautilus and terminal. Downgrading to 1:1.2.4-1 from Testing fixes the problem. I am using Squeeze with nfs-kernel-server version 1:1.2.2-4 on the server side. -- Package-specific info: -- rpcinfo -- program vers proto port 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 45260 status 100024 1 tcp 50813 status -- /etc/default/nfs-common -- NEED_STATD= STATDOPTS= NEED_IDMAPD=yes NEED_GSSD= -- /etc/idmapd.conf -- [General] Verbosity = 0 Pipefs-Directory = /var/lib/nfs/rpc_pipefs [Mapping] Nobody-User = nobody Nobody-Group = nogroup -- /etc/fstab -- -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nfs-common depends on: ii adduser 3.113 ii initscripts 2.88dsf-13.11 ii libc6 2.13-21 ii libcap2 1:2.22-1 ii libcomerr2 1.42~WIP-2011-10-05-2 ii libdevmapper1.02.1 2:1.02.65-1 ii libevent-1.4-2 1.4.14b-stable-1 ii libgssapi-krb5-2 1.9.1+dfsg-3 ii libgssglue1 0.3-3.1 ii libk5crypto3 1.9.1+dfsg-3 ii libkeyutils1 1.5.2-2 ii libkrb5-3 1.9.1+dfsg-3 ii libnfsidmap2 0.24-1 ii libtirpc1 0.2.2-5 ii libwrap0 7.6.q-21 ii lsb-base 3.2-28 ii rpcbind 0.2.0-6 ii ucf 3.0025+nmu2 Versions of packages nfs-common recommends: ii python 2.7.2-9 nfs-common suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 644948-done@bugs.debian.org
- Subject: Re: nfs-common: Wrong uid/gid with latest version using NFSv4
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Sat, 19 Mar 2022 18:29:02 +0100
- Message-id: <4b512fde181875e8800a4526d149362b46101e43.camel@decadent.org.uk>
- In-reply-to: <20111011010903.2848.8166.reportbug@Tramp.hjemmenettverk>
- References: <20111011010903.2848.8166.reportbug@Tramp.hjemmenettverk>
Closing this, as the problem appears to have been a misconfiguration rather than a bug. Ben. -- Ben Hutchings Beware of programmers who carry screwdrivers. - Leonard BrandweinAttachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---