unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: Offloading to use Guile-SSH instead of lsh
Date: Sun, 27 Nov 2016 23:10:53 +0100	[thread overview]
Message-ID: <87k2bok1zm.fsf@gnu.org> (raw)
In-Reply-To: <87zikmb7ix.fsf@member.fsf.org> ("宋文武"'s message of "Sat, 26 Nov 2016 23:11:34 +0800")

iyzsong@member.fsf.org (宋文武) skribis:

> Leo Famulari <leo@famulari.name> writes:
>
>> On Fri, Nov 25, 2016 at 11:50:22PM +0100, Ludovic Courtès wrote:
>>> Hi!
>>> 
>>> ludo@gnu.org (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)

Bah, what a mess!

‘guix offload’ needs Guile-SSH 0.10.2, but ‘guix offload’ is only
invoked from guix-daemon, and guix-daemon is not updated using ‘guix
pull’ anyway.

I committed a workaround as aa28ecc40af91d7cdff2fb3ab4ad86ad10d43ab7.

Fundamentally, it illustrates that the current strategy of ‘guix pull’
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’.

  reply	other threads:[~2016-11-27 22:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-05 15:41 Offloading to use Guile-SSH instead of lsh Ludovic Courtès
2016-11-06  7:47 ` Efraim Flashner
2016-11-06 17:40   ` Ludovic Courtès
2016-11-25 22:50 ` Ludovic Courtès
2016-11-26  4:42   ` Leo Famulari
2016-11-26 15:11     ` 宋文武
2016-11-27 22:10       ` Ludovic Courtès [this message]
2016-11-28 10:06         ` Efraim Flashner
2016-11-28 14:13           ` ‘guix pull’ and external dependencies Ludovic Courtès
2016-11-29  1:58             ` Chris Marusich
2016-11-29 14:54               ` Ludovic Courtès
2016-12-06  9:34 ` Offloading to use Guile-SSH instead of lsh Ludovic Courtès

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=87k2bok1zm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@member.fsf.org \
    /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).