From: Chris Marusich <cmmarusich@gmail.com>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: openssh vulnerability
Date: Sat, 20 Oct 2018 13:17:48 -0700 [thread overview]
Message-ID: <87o9bope37.fsf@gmail.com> (raw)
In-Reply-To: <87woqgiuiv.fsf@dustycloud.org> (Christopher Lemmer Webber's message of "Wed, 17 Oct 2018 09:15:36 -0400")
[-- Attachment #1: Type: text/plain, Size: 1250 bytes --]
Christopher Lemmer Webber <cwebber@dustycloud.org> writes:
> Leo Famulari writes:
>
>> [...]
>>
>> Patch at <https://bugs.gnu.org/33067>
>
> Yay, thanks Leo!
Thank you for the fix! It looks like this change
(eed00f93e8999712191e39c59c15e23461520f43) went to master:
--8<---------------cut here---------------start------------->8---
$ git branch -a --contains eed00f93e8999712191e39c59c15e23461520f43
* (HEAD detached at 7d1f21c69)
master
remotes/origin/HEAD -> origin/master
remotes/origin/master
remotes/origin/wip-next-browser3
--8<---------------cut here---------------end--------------->8---
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---
I looked into this email thread mainly because I was curious to see how
we would apply the security update. I thought we would use grafts
somehow, but this looks like we just changed the package definition on
master, which will result in more rebuilds than usual - right?
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-10-20 20:18 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 [this message]
2018-10-21 19:19 ` libssh vulnerability Leo Famulari
2018-10-21 20:14 ` 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=87o9bope37.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=cwebber@dustycloud.org \
--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.