all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
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 21:19:15 +0100	[thread overview]
Message-ID: <87lfsdgcos.fsf@gnu.org> (raw)
In-Reply-To: <20191118121535.256353ae.kmx@posteo.net> (Kai Mertens's message of "Mon, 18 Nov 2019 12:15:35 +0100")

Hello,

Kai Mertens <kmx@posteo.net> skribis:

> hmm, I am on i686 – is the trick still applicable?

Sure, you can try the command I gave with
"/gnu/store/ly0x0dk2qm0jk3fgwsrnl5cy8a1ybwkk-guix-900ef20b1.drv" for
instance.

> I will switch to root’s profile with “sudo -i”, but that is ok, right?

Yes, you can do that.  “sudo -i guix pull” means you’ll be updating
root’s Guix.  You’ll probably want to update your user’s Guix as well,
with just “guix pull”.

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

Right, you have to get yourself a newer Guix first.  :-)

HTH!

Ludo’.

  parent reply	other threads:[~2019-11-18 20:20 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
2019-11-18 20:19     ` Ludovic Courtès [this message]
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

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

  git send-email \
    --in-reply-to=87lfsdgcos.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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 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.