unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 43960@debbugs.gnu.org, "Дмитрий Поляков" <liltechdude@gmail.com>
Subject: bug#43960:
Date: Thu, 15 Oct 2020 09:53:58 +0200	[thread overview]
Message-ID: <87pn5jc4bt.fsf@gnu.org> (raw)
In-Reply-To: <878scbib5u.fsf@nckx> (Tobias Geerinckx-Rice's message of "Mon, 12 Oct 2020 19:53:01 +0200")

Hi,

Tobias Geerinckx-Rice <me@tobias.gr> skribis:

> Дмитрий Поляков 写道：
>> 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.

I don’t think it’s a reasonable response: it’s a fact that we naturally
tend to read manuals sparsely, at best.

Since the pastes vanished, how did ‘sudo guix pull’ lead to incompatible
bytecode warnings?

Thanks,
Ludo’.




  reply	other threads:[~2020-10-15  7:55 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   ` bug#43960: Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-10-15  7:53     ` Ludovic Courtès [this message]
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=87pn5jc4bt.fsf@gnu.org \
    --to=ludo@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).