all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Catonano <catonano@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: not an ELF file
Date: Wed, 24 May 2017 13:10:21 +0200	[thread overview]
Message-ID: <CAJ98PDx2M1tQ6Wq_FcTmnzcZ5E-D8=G_dpd5Ovvbf561RQSoaA@mail.gmail.com> (raw)
In-Reply-To: <87o9ui4le9.fsf@gnu.org>

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

2017-05-24 12:08 GMT+02:00 Ludovic Courtès <ludo@gnu.org>:

> Catonano <catonano@gmail.com> skribis:
>
> > sudo guix pull succeeded
> >
> > guix pull fails with
> > guix pull: error: guile-ssh-rexec-bug.patch: patch not found
>
> Hmm, could you run “rm ~/.config/guix/latest”?
>

I could. But then, without a working guix, how would I reinstate it ?

Anyway, I linked .config/guix/latest to a local checkked out master branch
I had

It seems to work

Ricardo made me aware that I could run "guix pull" from within any checked
out guix and that would reset the .coni/guix/latest  to point to a guix
subjected to the "guix pull" command

So it seems this is solved

I believe that these tricks related to .config/guix/latest  should be
discussed, to some extent, in the manual

It's not just a configuration matter
It's about the substantial day to day use

I will open a new thread for this

In the meantime: thank you

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

      reply	other threads:[~2017-05-24 11:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23 20:14 not an ELF file Catonano
2017-05-23 20:21 ` Catonano
2017-05-23 20:35 ` Ludovic Courtès
2017-05-23 20:55   ` Catonano
2017-05-23 21:05     ` Catonano
2017-05-24  3:35       ` Catonano
2017-05-24 10:08         ` Ludovic Courtès
2017-05-24 11:10           ` Catonano [this message]

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='CAJ98PDx2M1tQ6Wq_FcTmnzcZ5E-D8=G_dpd5Ovvbf561RQSoaA@mail.gmail.com' \
    --to=catonano@gmail.com \
    --cc=help-guix@gnu.org \
    --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.