all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 43960@debbugs.gnu.org, "Дмитрий Поляков" <liltechdude@gmail.com>
Subject: bug#43960:
Date: Thu, 15 Oct 2020 11:47:30 +0200	[thread overview]
Message-ID: <86zh4n253h.fsf@gmail.com> (raw)
In-Reply-To: <87pn5jc4bt.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 15 Oct 2020 09:53:58 +0200")

Hi,

On Thu, 15 Oct 2020 at 09:53, Ludovic Courtès <ludo@gnu.org> wrote:

> 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?

If I remember correctly (which is neither a reasonable response :-)), it
should highly come from the user config.  And the investigation needs
more information, e.g., as Tobias asks: 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

All the best,
simon




  reply	other threads:[~2020-10-15  9:48 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       ` zimoun [this message]
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

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

  git send-email \
    --in-reply-to=86zh4n253h.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=43960@debbugs.gnu.org \
    --cc=liltechdude@gmail.com \
    --cc=ludo@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.