all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Update harfbuzz to 1.0.6 (CVE-2016-2052)
Date: Fri, 29 Jan 2016 09:41:45 +0200	[thread overview]
Message-ID: <20160129094145.76c50cce@debian-netbook> (raw)
In-Reply-To: <cover.1454047197.git.leo@famulari.name>

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

On Fri, 29 Jan 2016 01:01:19 -0500
Leo Famulari <leo@famulari.name> wrote:

> This patch updates harfbuzz to 1.0.6, fixing CVE-2016-2052 [0].
> 
> However, 587 packages depend on harfbuzz [1]. Where should the patch be
> applied?
> 
> [0]
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-2052
> 
> [1]
> Building the following 199 packages would ensure 388 dependent packages 
> are rebuilt: avidemux-2.6.10 python-pyqt-5.5 pumpa-0.9.1 
[snip]
> Leo Famulari (1):
>   gnu: harfbuzz: Update to 1.0.6 [fixes CVE-2016-2052].
> 
>  gnu/packages/gtk.scm | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 

how about the security-updates branch?

-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-01-29  7:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-29  6:01 [PATCH 0/1] Update harfbuzz to 1.0.6 (CVE-2016-2052) Leo Famulari
2016-01-29  6:01 ` [PATCH 1/1] gnu: harfbuzz: Update to 1.0.6 [fixes CVE-2016-2052] Leo Famulari
2016-01-29  8:02   ` Mark H Weaver
2016-01-29  7:41 ` Efraim Flashner [this message]
2016-01-29  8:04   ` [PATCH 0/1] Update harfbuzz to 1.0.6 (CVE-2016-2052) Leo Famulari

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=20160129094145.76c50cce@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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.