unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 38226@debbugs.gnu.org, Kai Mertens <kmx@posteo.net>
Subject: bug#38226: guix pull: error: build failed: [...] ice-9/boot-9.scm:109:20: Syntax error:
Date: Mon, 18 Nov 2019 13:08:10 +0100	[thread overview]
Message-ID: <CAJ3okZ0uOQn26BaFi7o7B_pgANzOHhbaELo_e-vw98hFCcH0uA@mail.gmail.com> (raw)
In-Reply-To: <87eey6jjds.fsf@gnu.org>

Hi Ludo,

On Sun, 17 Nov 2019 at 22:15, Ludovic Courtès <ludo@gnu.org> wrote:

> The only thing that’s missing here is that currently “guix build
> /gnu/store/….drv” fails if the .drv doesn’t already exist, which is why
> the trick above resorts to a lower-level mechanism.

I miss how to fetch this missing .drv. :-)


For example this evaluation built a recent enough Guix, right?

--8<---------------cut here---------------start------------->8---
$ wget -q -O - 'http://ci.guix.gnu.org/build/1943556' | jq '."derivation"'
--8<---------------cut here---------------start------------->8---

outputs the derivation file. But how do you fetch it?

I have not found in the Cuirass API doc. Maybe I missing the obvious.

Then, once I have downloaded this derivation, the old Guix should be
able to build it, right? No daemon issue?

--8<---------------cut here---------------start------------->8---
$ guix build "/gnu/store/bz1qqy225p1jlicwf07iiqr79icqddcv-guix-4de11dda7.drv"
--8<---------------cut here---------------start------------->8---

This will populate the store with a new guix. Then I need to pull as
root, in order to also update the daemon, right?

--8<---------------cut here---------------start------------->8---
# /gnu/store/<hash-returned-by-previous-build>-guix-4de11dda7/bin/guix pulll
--8<---------------cut here---------------start------------->8---




> Perhaps ‘guix pull’ should have a ‘--rescue’ option to do the trick
> above?

Is it possible?
We need to track on Cuirass one recent enough derivation of Guix for
each architecture, right?



All the best,
simon

  parent reply	other threads:[~2019-11-18 12:09 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
2019-11-18 12:08   ` zimoun [this message]
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=CAJ3okZ0uOQn26BaFi7o7B_pgANzOHhbaELo_e-vw98hFCcH0uA@mail.gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=38226@debbugs.gnu.org \
    --cc=kmx@posteo.net \
    --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 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).