all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: libssh vulnerability
Date: Sun, 21 Oct 2018 15:19:19 -0400	[thread overview]
Message-ID: <20181021191919.GB18445@jasmine.lan> (raw)
In-Reply-To: <87o9bope37.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]

On Sat, Oct 20, 2018 at 01:17:48PM -0700, Chris Marusich wrote:
> Will this change trigger many rebuilds?  It has many dependents:
> 
> --8<---------------cut here---------------start------------->8---
> $ guix refresh -l libssh2
> Building the following 1321 packages would ensure 3307 dependent
> packages are rebuilt: [...]
> --8<---------------cut here---------------end--------------->8---

It's true that libssh2 has too many dependents to update without a
graft. However, libssh, which is what was changed, only has a handful of
dependents, which is convenient for us :)

------
$ guix refresh -l libssh
Building the following 9 packages would ensure 12 dependent packages are rebuilt: kodi@18.0_alpha-8.ec16dbc wireshark@2.6.4 guile2.0-guix@0.15.0-5.1d0be47 cuirass@0.0.1-20.fe2b73c emacs-guix@0.5 gwl@0.1.1 hpcguix-web@0.0.1-3.53e09ea guile2.2-ssh@0.11.3 tmate@2.2.1
------

It's confusing, but libssh and libssh2 are totally separate projects.
And for the record, they are also not related to OpenSSH, which is the
one we all know and use directly.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-10-21 19:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17  1:20 openssh vulnerability Christopher Lemmer Webber
2018-10-17  4:47 ` Mike Gerwitz
2018-10-17  5:42   ` Leo Famulari
2018-10-17 13:15     ` Christopher Lemmer Webber
2018-10-20 20:17       ` Chris Marusich
2018-10-21 19:19         ` Leo Famulari [this message]
2018-10-21 20:14           ` libssh vulnerability Chris Marusich

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=20181021191919.GB18445@jasmine.lan \
    --to=leo@famulari.name \
    --cc=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.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 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.