all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Grigory Shepelev <shegeley@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>, 52559@debbugs.gnu.org
Subject: bug#52559: guix pull fails with `Unknown command: nix fish: nix show-derivation "~/.fr-sqOEpp/....-module-import-compiled.drv"
Date: Mon, 27 Dec 2021 17:27:13 +0300	[thread overview]
Message-ID: <CAGJuR-61yEhVuu3=BxNJHU5YmBk=4ZgFkOqB_HG-mT=d4djKpQ@mail.gmail.com> (raw)
In-Reply-To: <cdb13df88d20375a138a8a5cbeaa1d82e34eac70.camel@telenet.be>

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

After the last letter my laptop's motherboard broke. It was replaced
recently but all the data was lost from the SSD due to encryption...
TLDR: I made a backup and reinstalled the system.
But the problem still persists. How can I safely move root's profile into
the user's one?  Tinkering with any root-related things is a danger zone
for me, so I won't do anything on my own until there are any clear
instructions.
As previously: from root "guix pull" works perfectly. From users it has the
same problem (nix-related error).


пт, 17 дек. 2021 г. в 09:59, Maxime Devos <maximedevos@telenet.be>:

> Grigory Shepelev schreef op vr 17-12-2021 om 09:21 [+0300]:
> > Although I was able to "guix pull" with "sudo", as root user
> > normally. As far as I know guix pull updates only per-user when
> > called.
> > Can I use the result from root somehow?
>
> Determine the full store path of root's guix & run that.
>
> Greetings,
> Maxime
>
>

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

  parent reply	other threads:[~2021-12-27 14:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 17:46 bug#52559: guix pull fails with `Unknown command: nix fish: nix show-derivation "~/.fr-sqOEpp/....-module-import-compiled.drv" Grigory Shepelev
2021-12-16 18:29 ` Maxime Devos
2021-12-16 19:15   ` Grigory Shepelev
2021-12-16 19:29     ` Grigory Shepelev
2021-12-16 19:32       ` Grigory Shepelev
2021-12-16 19:52     ` Grigory Shepelev
     [not found]   ` <CAGJuR-64F703LMjNeN=UfmzBcBPA1qVTY8bz-1umoxDaB+qcGQ@mail.gmail.com>
2021-12-16 20:26     ` Maxime Devos
2021-12-16 20:49       ` Grigory Shepelev
2021-12-16 20:54         ` Grigory Shepelev
2021-12-16 21:12           ` Grigory Shepelev
     [not found]             ` <d96e92826149aed480f5a9dc3a1f3bc891bc0a83.camel@telenet.be>
     [not found]               ` <CAGJuR-7E9Oztcig0_vzFGETXU6fXakh+wQzpxe0wcrw-n=8hhg@mail.gmail.com>
2021-12-16 21:24                 ` bug#52559: Fwd: " Grigory Shepelev
2021-12-16 21:32             ` Maxime Devos
2021-12-16 21:50             ` Maxime Devos
2021-12-17  5:50               ` Grigory Shepelev
2021-12-17  6:21                 ` Grigory Shepelev
2021-12-17  6:59                   ` Maxime Devos
2021-12-17  9:07                     ` Grigory Shepelev
2021-12-27 14:27                     ` Grigory Shepelev [this message]
2021-12-27 15:53                       ` Maxime Devos
2021-12-27 18:01                         ` Grigory Shepelev
2021-12-27 20:08                           ` Maxime Devos
2022-01-17 19:02                             ` Grigory Shepelev
2022-01-17 19:31                               ` Maxime Devos
2022-01-17 19:37                                 ` Grigory Shepelev
2021-12-17  6:53                 ` Maxime Devos
2021-12-16 21:13         ` Maxime Devos
2021-12-16 18:30 ` Maxime Devos
2021-12-16 18:32 ` Maxime Devos

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='CAGJuR-61yEhVuu3=BxNJHU5YmBk=4ZgFkOqB_HG-mT=d4djKpQ@mail.gmail.com' \
    --to=shegeley@gmail.com \
    --cc=52559@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /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.