From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: Offloading to use Guile-SSH instead of lsh Date: Sun, 27 Nov 2016 23:10:53 +0100 Message-ID: <87k2bok1zm.fsf@gnu.org> References: <87poma53yi.fsf@gnu.org> <87oa13qimp.fsf@gnu.org> <20161126044257.GA15256@jasmine> <87zikmb7ix.fsf@member.fsf.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51955) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cB7f1-0007Lr-CK for guix-devel@gnu.org; Sun, 27 Nov 2016 17:11:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cB7ey-0000vF-7X for guix-devel@gnu.org; Sun, 27 Nov 2016 17:10:59 -0500 In-Reply-To: <87zikmb7ix.fsf@member.fsf.org> (=?utf-8?B?IuWui+aWh+atpiIn?= =?utf-8?B?cw==?= message of "Sat, 26 Nov 2016 23:11:34 +0800") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: =?utf-8?B?5a6L5paH5q2m?= Cc: guix-devel@gnu.org iyzsong@member.fsf.org (=E5=AE=8B=E6=96=87=E6=AD=A6) skribis: > Leo Famulari writes: > >> On Fri, Nov 25, 2016 at 11:50:22PM +0100, Ludovic Court=C3=A8s wrote: >>> Hi! >>>=20 >>> ludo@gnu.org (Ludovic Court=C3=A8s) skribis: >>>=20 >>> > The =E2=80=98wip-guile-ssh=E2=80=99 branch is finally getting into sh= ape. As soon as >>> > a new Guile-SSH release is out, I=E2=80=99ll merge it on master. >>>=20 >>> Done! >>>=20 >>> It seems to work well in my own tests, but more feedback is welcome. >> >> It looks like there is a spurious module import of (ssh key) with the >> latest code: >> >> $ guix pull=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20 >>=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20= =20=20=20 >> ... >> 2870: 1 [resolve-interface (ssh key) #:select ...] >> In unknown file: >> ?: 0 [scm-error misc-error #f "~A ~S" ("no code for module" (ssh key)= ) #f] >> >> ERROR: In procedure scm-error: >> ERROR: no code for module (ssh key) >> builder for `/gnu/store/z958zcva82idmanswyw7zg00zyack221-guix-latest.drv= ' failed with exit code 1 >> guix pull: error: build failed: build of `/gnu/store/z958zcva82idmanswyw= 7zg00zyack221-guix-latest.drv' failed > > I push a commit 5aed7f10f to add guile-ssh to the load-path of the pull > builder (the commit message refers a wrong commit, sorry) to fix it. > > But as ng0 report in #guix, the 0.11 install media is still broken. > Since I add guile-ssh's go files to load-compiled-path, which are > broken before commit 92b7258. > > Should I remove guile-ssh from %load-compiled-path in > build-aux/build-self.scm? (assuming the offload script build fine with > guile-ssh-0.9.0 of the guix-0.11) Bah, what a mess! =E2=80=98guix offload=E2=80=99 needs Guile-SSH 0.10.2, but =E2=80=98guix of= fload=E2=80=99 is only invoked from guix-daemon, and guix-daemon is not updated using =E2=80=98guix pull=E2=80=99 anyway. I committed a workaround as aa28ecc40af91d7cdff2fb3ab4ad86ad10d43ab7. Fundamentally, it illustrates that the current strategy of =E2=80=98guix pu= ll=E2=80=99 of relying on user-provided packages is flawed: we can get a broken Guile-SSH, or one with the wrong version, or none at all, and that really sucks. Updating Guix should be like updating a normal package: you get the package itself and all its dependencies that are known to work. Ludo=E2=80=99.