From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#39925: `guix pull` failure in multi-machine setup Date: Fri, 06 Mar 2020 11:53:08 +0100 Message-ID: <87wo7xoiuj.fsf@gnu.org> References: <20200305133318.GB2909@zpidnp36> <87ftem7m6d.fsf@gnu.org> <20200306074018.GC2909@zpidnp36> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:59613) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jAAcG-0005SW-Co for bug-guix@gnu.org; Fri, 06 Mar 2020 05:54:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jAAcE-0004pK-C0 for bug-guix@gnu.org; Fri, 06 Mar 2020 05:54:04 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:38167) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jAAcE-0004ot-8M for bug-guix@gnu.org; Fri, 06 Mar 2020 05:54:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jAAcE-0007jE-4j for bug-guix@gnu.org; Fri, 06 Mar 2020 05:54:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <20200306074018.GC2909@zpidnp36> (Lars-Dominik Braun's message of "Fri, 6 Mar 2020 08:40:18 +0100") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Lars-Dominik Braun Cc: 39925@debbugs.gnu.org Hello, Lars-Dominik Braun skribis: >> This is a limitation in =E2=80=98build-aux/build-self.scm=E2=80=99: [=E2= =80=A6] > I don=E2=80=99t understand what=E2=80=99s going on there unfortunately. I= s there a high-level > explanation somewhere in the manual? > >> We could work around it by letting the =E2=80=98GUIX_DAEMON_SOCKET=E2=80= =99 environment >> variable through, along these lines: > Nope, that does not seem to be enough. After pulling on master doing the = same > on a node (with a patched guix) yields: > > ---snip--- > ice-9/eval.scm:293:34: Throw to key `srfi-34' with args `(#" errno: 95] 7f0f325f77b0= >)'. > ---snap--- > > Any ideas? Sounds like this ssh URI is not valid on the nodes, is that right? >> + (when (and (not (file-port? port) daemon-sock= et)) > (when (and (not (file-port? port)) daemon-socket) > I assume: =E2=86=91 > >> [=E2=80=A6] and won=E2=80=99t work with old Guix revisions anyway. > That means `guix time-machine` could not go back beyond a commit that fix= es the > issue, correct? Not a concern for me. Correct. >> However, for your use case, you could perhaps simply pull on one machine >> and use =E2=80=98guix copy=E2=80=99 to send Guix elsewhere? > The store is the same on all machines, since /gnu/store, /var/guix and /h= ome > are all shared via NFS. As far as I understand the manual `guix copy` wou= ld be > useful for store to store transfers on different machines only. Right. So perhaps I don=E2=80=99t quite understand the use case. What abo= ut simply pulling from one of these machines, if everything is shared over NFS? HTH, Ludo=E2=80=99.