Re: Offloading to use Guile-SSH instead of lsh

[宋文武]

Leo Famulari <address@hidden> writes:

> On Fri, Nov 25, 2016 at 11:50:22PM +0100, Ludovic Courtès wrote:
>> Hi!
>> 
>> address@hidden (Ludovic Courtès) skribis:
>> 
>> > The ‘wip-guile-ssh’ branch is finally getting into shape.  As soon as
>> > a new Guile-SSH release is out, I’ll merge it on master.
>> 
>> Done!
>> 
>> 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                                         
>                           
> ...
> 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/z958zcva82idmanswyw7zg00zyack221-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)