all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 46756@debbugs.gnu.org, pkill9 <pkill9@runbox.com>
Subject: bug#46756: guix deploy not copying remote-gexp.scm
Date: Wed, 27 Oct 2021 21:20:43 -0400	[thread overview]
Message-ID: <87fssmaqs4.fsf_-_@gmail.com> (raw)
In-Reply-To: <handler.46756.D46756.163537507421947.notifdone@debbugs.gnu.org> (GNU bug Tracking System's message of "Wed, 27 Oct 2021 22:52:02 +0000")

Hi!

help-debbugs@gnu.org (GNU bug Tracking System) writes:

> I believe this is fixed by b19250eec6f92308f237a09a43e8e3e2355345b9,
> lemme know!
>
> Following our discussion on IRC, I noticed that derivations would
> actually be built locally, and thus their output (‘remote-exp.scm’
> above) would not be found.
>
> Why are they getting built locally?  Because ‘guix deploy’ installs a
> build handler.  Thus, when ‘remote-eval’ makes this call:
>
>   (build-derivations remote inputs)
>
> the build handler kicks in and starts building locally rather than on
> ‘remote’.  In fact, that’s more of a bug in ‘build-accumulator’ in (guix
> store); it should check whether it’s talking to the right store.
>
> Thanks,
> Ludo’.

It works a treat!  Thank you! :-)

It'll make keeping my remote machine updated with 'guix deploy' much
smoother.

Thanks again,

Maxim




  parent reply	other threads:[~2021-10-28  1:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-24 17:59 bug#46756: guix deploy not copying remote-gexp.scm pkill9
2021-04-03  4:38 ` Maxim Cournoyer
2021-10-27 22:51   ` Ludovic Courtès
2021-09-08  1:52 ` Katherine Cox-Buday
     [not found] ` <handler.46756.D46756.163537507421947.notifdone@debbugs.gnu.org>
2021-10-28  1:20   ` Maxim Cournoyer [this message]
2021-10-28 20:00     ` Ludovic Courtès
2021-10-29 20:23       ` Maxim Cournoyer

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=87fssmaqs4.fsf_-_@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=46756@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=pkill9@runbox.com \
    /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.