unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Kai Mertens <kmx@posteo.net>
Cc: 38226@debbugs.gnu.org
Subject: bug#38226: guix pull: error: build failed: [...] ice-9/boot-9.scm:109:20: Syntax error:
Date: Mon, 18 Nov 2019 13:23:58 +0100	[thread overview]
Message-ID: <CAJ3okZ33Z7X3Q6ZKQf0iwGGrYujSLFg5KeRw7b57vSick1M7pg@mail.gmail.com> (raw)
In-Reply-To: <20191118121535.256353ae.kmx@posteo.net>

Hi Kai,

On Mon, 18 Nov 2019 at 12:19, Kai Mertens <kmx@posteo.net> wrote:

> On Sun, 17 Nov 2019 22:14:07 +0100
> Ludovic Courtès <ludo@gnu.org> wrote:

> > Here’s a trick to do that (for commit 57c7bfec6, on x86_64-linux):
>
> hmm, I am on i686 – is the trick still applicable?
> I will switch to root’s profile with “sudo -i”, but that is ok, right?
> (If you please send your OK – then I will try it...)

I think the evaluation [1] should do the job for i686.

[1] https://ci.guix.gnu.org/build/1943561/details




> I guess I cannot use a simple “sudo -i guix package -u guix” as a
> workaround for the failing “sudo -i guix pull”, as it would bring up
> the same issue?

The issue you encounter comes from a compatibility break in Guix. Four
years later (more or less I guess), inferiors has bee introduced in
Guix. They allow to go back and forward with "guix pull --commit=".
Well, other said, your version of Guix is too old to be updated using
the usual way.

The only way is to apply the Ludo's "trick".  If I understand well:
 1. Fetch a recent enough derivation of Guix
 2. Build this derivation with your old Guix
 3. Manually pull to populate the store
 4. Then the profile ~/.config/guix/ should be ok


> Oh, I don't feel competent enough to give ideas, but “pull --rescue”
> sounds too generic to me. Maybe there will be other use cases that will
> require a (different) rescue trick in future. Instead, your commit
> 9c9982dc0 suggests a “pull --substitute-missing-derivations” to me.

If I understand well, your version of Guix is too old to use the
feature described in commit 9c9982dc0.

And if I still understand correctly, "pull --rescue" should be
mechanism to easily update an old Guix (before the overhaul in 0.15.0)
instead of doing all the dance.


All the best,
simon

  reply	other threads:[~2019-11-18 12:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-16  2:26 bug#38226: guix pull: error: build failed: [...] ice-9/boot-9.scm:109:20: Syntax error: Kai Mertens
2019-11-17 21:14 ` Ludovic Courtès
2019-11-18 11:15   ` Kai Mertens
2019-11-18 12:23     ` zimoun [this message]
2019-11-18 20:19     ` Ludovic Courtès
2019-11-18 12:08   ` zimoun
2019-11-18 16:22     ` Ludovic Courtès
2019-11-18 16:44       ` zimoun
2019-11-18 20:10         ` Ludovic Courtès
2019-11-19 11:49           ` zimoun
2019-11-20 14:15             ` Ludovic Courtès
2019-11-20 14:21   ` Kai Mertens
2020-02-18 13:27     ` zimoun
2020-05-22  0:22 ` bug#38226: guix pull: error: build failed: zimoun

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=CAJ3okZ33Z7X3Q6ZKQf0iwGGrYujSLFg5KeRw7b57vSick1M7pg@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=38226@debbugs.gnu.org \
    --cc=kmx@posteo.net \
    /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).