unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Mark H Weaver <mhw@netris.org>
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 20:15:10 +0200	[thread overview]
Message-ID: <87vacwb8b5.fsf@fastmail.com> (raw)
In-Reply-To: <87d0z4b8kf.fsf@netris.org>

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

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'.

Since we haven't started the "full" core-updates on Hydra yet, I figured
it was okay.  What do you think?

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

  reply	other threads:[~2018-04-12 18:15 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 [this message]
2018-04-12 19:29       ` Mark H Weaver

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=87vacwb8b5.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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).