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 17:44:43 +0100 [thread overview]
Message-ID: <CAJ3okZ3hOLcWKAhPW8NiJQDMSZuszQK1g2o15yogecgSb51f2A@mail.gmail.com> (raw)
In-Reply-To: <87zhgtgno6.fsf@gnu.org>
Hi Ludo,
On Mon, 18 Nov 2019 at 17:22, Ludovic Courtès <ludo@gnu.org> wrote:
> zimoun <zimon.toutoune@gmail.com> skribis:
> > 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?
> >
> > $ wget -q -O - 'http://ci.guix.gnu.org/build/1943556' | jq '."derivation"'
> >
> >
> > outputs the derivation file. But how do you fetch it?
>
> You don’t explicitly fetch it. Instead, you run “guix build /….drv”,
> and the daemon automatically attempts to substitute it if it’s not
> available in your store (note that you need commit
> 9c9982dc0c8c38ce3821b154b7e92509c1564317.)
I do not have when I tested.
The commit is from yesterday evening. ;-)
(that's a real rolling release :-D)
But if you have this commit, you do not need the dance that you
described to "guix pull" with a very very old Guix version -- say
before the 0.15 overhaul.
> Now, I noticed that it doesn’t work so well when ‘guix publish --cache’
> is used, as is the case on berlin. The reason is that the daemon will
> query substitutes one by one: guix-xyz.drv, then guix-xyz-builder, and
> so on. And because of the ‘--cache’ behavior, they’ll all have to be
> baked separately.
--8<---------------cut here---------------start------------->8---
$ guix build "/gnu/store/bz1qqy225p1jlicwf07iiqr79icqddcv-guix-4de11dda7.drv"
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
cannot build missing derivation
‘/gnu/store/bz1qqy225p1jlicwf07iiqr79icqddcv-guix-4de11dda7.drv’
guix build: error: build of
`/gnu/store/bz1qqy225p1jlicwf07iiqr79icqddcv-guix-4de11dda7.drv'
failed
$ guix describe
Generation 55 Nov 18 2019 13:21:24 (current)
guix 900ef20
repository URL: https://git.savannah.gnu.org/git/guix.git
branch: master
commit: 900ef20b1da66ad71145082c883dc12f31fafa54
--8<---------------cut here---------------end--------------->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?
>
> Yeah well, that needs more thought. :-)
I am not sure to clearly understand what we are talking about. :-)
All the best,
simon
next prev parent reply other threads:[~2019-11-18 16:46 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
2019-11-18 16:22 ` Ludovic Courtès
2019-11-18 16:44 ` zimoun [this message]
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=CAJ3okZ3hOLcWKAhPW8NiJQDMSZuszQK1g2o15yogecgSb51f2A@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 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.