unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Andreas Enge <andreas@enge.fr>
Cc: 30540-done@debbugs.gnu.org
Subject: bug#30540: ssh: No user exists for uid 1000
Date: Mon, 19 Feb 2018 19:30:44 -0500	[thread overview]
Message-ID: <20180220003044.GA6440@jasmine.lan> (raw)
In-Reply-To: <20180219230645.GA5650@jurong>

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

On Tue, Feb 20, 2018 at 12:06:45AM +0100, Andreas Enge wrote:
> it looks like the glibc change when merging core-updates caused us to be
> bitten by a bug that is known on NixOS:
>    https://github.com/NixOS/nixpkgs/issues/31762
> 
> When I type "ssh whatever" (literally, or replacing "whatever" by a real
> server name), then the error message
>    No user exists for uid 1000
> is printed and the ssh command is not executed.

The issue is that glibc 2.26 deprecated the "compat" query type of the
Name Service Switch.

We discussed this previously in <https://bugs.gnu.org/30298>.

One can adjust to the change by either using the nscd daemon [0] or
editing /etc/nsswitch.conf and replacing instances of 'compat' with
'files'.

On Debian Stretch, I found that `apt-get install nscd` was sufficient.

I'm going to merge this report with #30298.

[0] We already "strongly recommend" using nscd:
https://www.gnu.org/software/guix/manual/html_node/Application-Setup.html#Name-Service-Switch-1

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-02-20  0:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 23:06 bug#30540: ssh: No user exists for uid 1000 Andreas Enge
2018-02-20  0:30 ` Leo Famulari [this message]
2018-02-20 10:08   ` Andreas Enge
2018-02-20 11:54     ` Leo Famulari
2018-02-20 12:08       ` Andreas Enge
2018-02-20 12:52         ` Leo Famulari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180220003044.GA6440@jasmine.lan \
    --to=leo@famulari.name \
    --cc=30540-done@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).