all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Artyom Poptsov <poptsov.artyom@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: libssh upgraded; guile-ssh fails its tests
Date: Fri, 04 Apr 2014 22:07:06 +0200	[thread overview]
Message-ID: <87k3b46eqd.fsf@gnu.org> (raw)
In-Reply-To: <87mwg1vyyr.fsf@elephant.savannah> (Artyom Poptsov's message of "Fri, 04 Apr 2014 20:30:52 +0400")

Artyom Poptsov <poptsov.artyom@gmail.com> skribis:

>> Upgrading libssh from 0.5.5 to 0.6.3 turned out to break Guile-SSH
>> 0.6.0.  I attach some of the test logs.  Any idea what’s going on?
>
> Well, I think the problem is that there are changes in the API between
> libssh 0.5 and libssh 0.6.  So Guile-SSH must be updated to be able to
> work with libssh 0.6.  I have plans to migrate Guile-SSH to libssh 0.6,
> but this work is still to be done.

OK.

> And it worth mention that according to the Guile-SSH 0.6.0 documenation
> it requires libssh 0.5.4 or 0.5.5, so you shouldn't be surprised that
> Guile-SSH 0.6.0 breaks on libssh 0.6 ;-)

Indeed.  :-)

The important thing is that libssh 0.6.3 fixes a security issue:
<https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2014-0017>.

The patch being simple, I’ve adjusted it for 0.5.5, and used that for
Guile-SSH in the meantime:

  http://git.savannah.gnu.org/cgit/guix.git/commit/?id=9c333da6f1b465e70767254ab19d9ec27681bb7b

Thanks,
Ludo’.

      parent reply	other threads:[~2014-04-04 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-02 17:06 libssh upgraded; guile-ssh fails its tests Mark H Weaver
2014-04-04 15:51 ` Ludovic Courtès
2014-04-04 16:30   ` Artyom Poptsov
2014-04-04 18:07     ` Mark H Weaver
2014-04-04 19:17       ` Artyom Poptsov
2014-04-04 20:07     ` Ludovic Courtès [this message]

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=87k3b46eqd.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=poptsov.artyom@gmail.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.