all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jonas Schneider-Bensch <taffinaround@gmail.com>
To: 63546@debbugs.gnu.org
Subject: bug#63546: nix-channel error: opening pseudoterminal master: No such device
Date: Sat, 24 Jun 2023 08:54:14 +0200	[thread overview]
Message-ID: <CAHA-Oa1ufKQak2AGCdfKQ=hBCyowEZe=ZfkEa=TTzVDSC=R-iA@mail.gmail.com> (raw)
In-Reply-To: <CAEEhgEu0pROeYvYf8ZoGsaY=j-cPW+qmj4QUFvckWQfqFJehRw@mail.gmail.com>

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

Perhaps this is a permissions issue with the nix shepherd service? I
haven't tried the patch linked above, but found that I could run

$ sudo nix-channel --update

without running into the issue. Then, I got the same error again when
trying to install any package with nix-env. Once again, I could run

$ sudo nix-env -i <some-package>

which would successfully install it to the root profile. After doing
this, however, I found that I now could run

$ nix-env -i <some-package>

to install the package to my user profile, presumably because the nix
store was populated by the run with sudo.

[-- Attachment #2: Type: text/html, Size: 835 bytes --]

  parent reply	other threads:[~2023-06-25  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  4:44 bug#63546: nix-channel error: opening pseudoterminal master: No such device Nathan Dehnel
2023-06-04 15:50 ` Haider
2023-06-06 16:09 ` Zhu Zihao
2023-06-07 20:03 ` bug#63546: Nix-channel error Haider
2023-06-23  7:55 ` bug#63546: (No Subject) worldofgeese via Bug reports for GNU Guix
2023-06-24  6:54 ` Jonas Schneider-Bensch [this message]
2023-06-27 15:00 ` bug#63546: nix-channel error: opening pseudoterminal master: No such device Collin J. Doering via Bug reports for GNU Guix
2023-07-01  9:54 ` bug#63546: /gnu/store/6wv8x4115jykg58fdgcjfka12vp2vms6-glibc-for-fhs-2.35/lib Haider

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

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

  git send-email \
    --in-reply-to='CAHA-Oa1ufKQak2AGCdfKQ=hBCyowEZe=ZfkEa=TTzVDSC=R-iA@mail.gmail.com' \
    --to=taffinaround@gmail.com \
    --cc=63546@debbugs.gnu.org \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.