From: Mark H Weaver <mhw@netris.org>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 02/03: gnu: nghttp2: Update to 1.31.1 [fixes CVE-2018-1000168].
Date: Thu, 12 Apr 2018 15:29:54 -0400 [thread overview]
Message-ID: <878t9sb4ul.fsf@netris.org> (raw)
In-Reply-To: <87vacwb8b5.fsf@fastmail.com> (Marius Bakke's message of "Thu, 12 Apr 2018 20:15:10 +0200")
Marius Bakke <mbakke@fastmail.com> writes:
> Mark H Weaver <mhw@netris.org> writes:
>
>> Hi Marius,
>>
>> mbakke@fastmail.com (Marius Bakke) writes:
>>
>>> mbakke pushed a commit to branch master
>>> in repository guix.
>>>
>>> commit 65bfe30d8a4e930599603f6d835023bbd0dbcb9a
>>> Author: Marius Bakke <mbakke@fastmail.com>
>>> Date: Thu Apr 12 19:43:31 2018 +0200
>>>
>>> gnu: nghttp2: Update to 1.31.1 [fixes CVE-2018-1000168].
>>>
>>> * gnu/packages/web.scm (nghttp2): Update to 1.31.1.
>>
>> Thank you for this, but it would entail far too many builds to update on
>> the 'master' branch. 'curl' depends on 'nghttp2'. According to 'guix
>> refresh -l', it would require 2839 rebuilds on x86_64.
>
> On 'master', nghttp2 only has 1 dependent, the reverse curl dependency
> was added in this 'core-updates'.
Ah, sorry for the mistake. I just reverted my revert.
> Since we haven't started the "full" core-updates on Hydra yet, I figured
> it was okay. What do you think?
Okay. I just merged master into core-updates, so that those of us
tracking core-updates can start rebuilding it again.
Thanks,
Mark
prev parent reply other threads:[~2018-04-12 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180412174905.23638.55280@vcs0.savannah.gnu.org>
[not found] ` <20180412174906.CDFB12052F@vcs0.savannah.gnu.org>
2018-04-12 18:09 ` 02/03: gnu: nghttp2: Update to 1.31.1 [fixes CVE-2018-1000168] Mark H Weaver
2018-04-12 18:15 ` Marius Bakke
2018-04-12 19:29 ` Mark H Weaver [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=878t9sb4ul.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.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.