unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Bengt Richter <bokr@bokr.com>
Cc: 43960@debbugs.gnu.org, "Дмитрий Поляков" <liltechdude@gmail.com>
Subject: bug#43960:
Date: Thu, 15 Oct 2020 15:56:41 +0200	[thread overview]
Message-ID: <CAJ3okZ2chcK-J9Bn0+Mxjtyd4U9e6439kL9hYLPo8Mn4JY9ztw@mail.gmail.com> (raw)
In-Reply-To: <20201015135249.GA2949@LionPure>

Hi Bengt,

On Thu, 15 Oct 2020 at 15:53, Bengt Richter <bokr@bokr.com> wrote:

> If there is a left-over from old manual installation advice like
> --8<---------------cut here---------------start------------->8---
> /usr/local/bin/guix:
>     symbolic link to /var/guix/profiles/per-user/root/current-guix/bin/guix
> --8<---------------cut here---------------end--------------->8---
> could it interfere in any way with the above, or subsequent operation?

You mean the step #6 from the manual [1], right?

1: <https://guix.gnu.org/devel/manual/en/guix.html#Binary-Installation>


All the best,
simon




  reply	other threads:[~2020-10-15 13:58 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     ` 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           ` zimoun [this message]
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=CAJ3okZ2chcK-J9Bn0+Mxjtyd4U9e6439kL9hYLPo8Mn4JY9ztw@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=43960@debbugs.gnu.org \
    --cc=bokr@bokr.com \
    --cc=liltechdude@gmail.com \
    /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).