From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Дмитрий Поляков" <liltechdude@gmail.com>
Cc: 43960@debbugs.gnu.org
Subject: bug#43960:
Date: Mon, 12 Oct 2020 19:53:01 +0200 [thread overview]
Message-ID: <878scbib5u.fsf@nckx> (raw)
In-Reply-To: <CAAxPsTFE9A_YBGbvMAgEpJz=mXMbZM66C-Q6HfMCop0RdvsMFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
Дмитрий Поляков 写道:
> When I type with sudo:
> lil@guix ~
> $ sudo guix pull
Never run ‘guix pull’ with sudo!
Why is explained in the manual (3.7 After System Installation).
While guix could detect and warn about it (and I'm sure that's
already been proposed) you should always read the manual before
typing commands.
Please run (and post the output of):
$ type guix
$ ls -l ~/.config/guix/current
$ sudo rm ~/.config/guix/current
$ /run/current-system/profile/bin/guix pull
$ hash guix
$ type guix
This should print
guix is /home/nckx/.config/guix/current/bin/guix
If so, the following command will reconfigure your system using
your guix, not root's guix:
$ sudo guix system reconfigure /etc/config.scm
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2020-10-12 17:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 12:54 bug#43960: incompatible bytecode version Дмитрий Поляков
2020-10-12 15:29 ` zimoun
2020-10-12 16:07 ` bug#43960: Дмитрий Поляков
2020-10-12 17:53 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2020-10-15 7:53 ` bug#43960: Ludovic Courtès
2020-10-15 9:47 ` bug#43960: zimoun
2020-10-15 13:52 ` bug#43960: Bengt Richter
2020-10-15 13:56 ` bug#43960: zimoun
2020-10-15 16:39 ` bug#43960: Bengt Richter
2020-10-19 17:01 ` bug#43960: zimoun
2020-10-25 22:33 ` bug#43960: Miguel Ángel Arruga Vivas
2020-10-26 15:06 ` bug#43960: zimoun
2021-11-21 6:18 ` bug#43960: incompatible bytecode version Maxim Cournoyer
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=878scbib5u.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=43960@debbugs.gnu.org \
--cc=liltechdude@gmail.com \
--cc=me@tobias.gr \
/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).