unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Christopher Baines <mail@cbaines.net>, 67250@debbugs.gnu.org
Subject: bug#67250: builtin:git-download capability detection not working for the bordeaux build farm
Date: Mon, 20 Nov 2023 10:59:53 +0100	[thread overview]
Message-ID: <86zfz8219i.fsf@gmail.com> (raw)
In-Reply-To: <87pm08f41q.fsf@cbaines.net>

Hi Chris,

On Fri, 17 Nov 2023 at 21:39, Christopher Baines <mail@cbaines.net> wrote:

> The bordeaux build farm depends on computing the derivations on one
> machine, then potentially building them on a different machine.
>
> Some of the build machines don't have a new enough guix-daemon that
> understands builtin:git-download, so derivations that use this are
> sometimes failing (e.g. [1])

Do you mean that the drv file is generated using a new daemon then this
drv file is “offloaded” to another machine using an older daemon and
thus fails to build it?


> One potential approach to address this is somehow have the data service
> indicate that it wants compatible derivations when computing them,
> rather than to have guix do feature detection against the guix-daemon
> that is being used at the point the derivations are being computed.

Other solutions are: downgrade the daemon of one of the machine or
update the daemon of other machines, no?

Why would the latter not be possible?

Cheers
simon




  reply	other threads:[~2023-11-20 10:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-17 21:39 bug#67250: builtin:git-download capability detection not working for the bordeaux build farm Christopher Baines
2023-11-20  9:59 ` Simon Tournier [this message]
2023-11-20 10:29   ` Christopher Baines
2023-11-22 10:19 ` Ludovic Courtès
2023-11-28 14:10   ` Simon Tournier
2024-05-18 13:32     ` Christopher Baines
2023-11-28 16:54   ` Christopher Baines
2024-05-18 13:22     ` Christopher Baines

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=86zfz8219i.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=67250@debbugs.gnu.org \
    --cc=mail@cbaines.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).