From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 48564@debbugs.gnu.org
Subject: bug#48564: ‘channel-with-substitutes-available’ makes assumptions about job names
Date: Thu, 27 May 2021 11:20:41 +0200 [thread overview]
Message-ID: <878s40r0ra.fsf@inria.fr> (raw)
In-Reply-To: <87bl8x60lq.fsf@gnu.org> (Mathieu Othacehe's message of "Wed, 26 May 2021 16:17:21 +0200")
Heya,
Mathieu Othacehe <othacehe@gnu.org> skribis:
>>> (define* (channel-with-substitutes-available chan url
>>> #:key
>>> (specification "master"))
>>
>
> I have fixed the evaluation complete? field issue with
> a2155f41f53eeb5000857e7160c5ad0916dc9bfa.
Good catch!
> Regarding the idea we had, things are I fear a little more complex. If
> we consider what you would like to achieve:
>
> (list (channel-with-substitutes-available
> %default-guix-channel
> "https://ci.guix.gnu.org"
> #:spec "master")
> (channel-with-substitutes-available
> (channel
> (name 'guix-hpc)
> (url "https://gitlab.inria.fr/guix-hpc/guix-hpc.git"))
> "https://guix.bordeaux.inria.fr"
> #:spec "guix-hpc"))
>
>
> The first channel-with-substitutes-available could use the commit M1
> from the Savannah Guix master branch, while the second
> channel-with-substitutes-available could use the commit H1 from the
> HPC gitlab master branch.
>
> If the commit H1 is evaluated by the Inria Cuirass against an older
> Savannah Guix master commit let say M2, then "guix pull" will rebuild
> the guix-hpc derivation I guess.
>
> Maybe we need something that looks like:
>
> (channels-with-substitutes-available
> (list %default-guix-channel
> (channel
> (name 'guix-hpc)
> (url "https://gitlab.inria.fr/guix-hpc/guix-hpc.git")))
> (list "https://ci.guix.gnu.org"
> "https://guix.bordeaux.inria.fr")
> (specs "master" "guix-hpc"))
>
> that would make sure to use a couple of Guix and HPC commits that
> have been evaluated together on the Inria Cuirass server.
>
> This looks more complex though :(
Hmm yeah. Actually, in this example, it would make sense to take both
commits from guix.bordeaux.inria.fr, since that instance necessarily has
info about the two channels. But yeah, it remains a bit complex.
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-05-27 9:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 12:58 bug#48564: ‘channel-with-substitutes-available’ makes assumptions about job names Ludovic Courtès
2021-05-21 13:28 ` Mathieu Othacehe
2021-05-21 14:30 ` Ludovic Courtès
2021-05-26 14:17 ` Mathieu Othacehe
2021-05-27 9:20 ` Ludovic Courtès [this message]
2021-05-27 20:34 ` 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=878s40r0ra.fsf@inria.fr \
--to=ludovic.courtes@inria.fr \
--cc=48564@debbugs.gnu.org \
--cc=othacehe@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.