unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] gnu: Add libjpeg-turbo.
Date: Sun, 27 Nov 2016 16:36:08 -0500	[thread overview]
Message-ID: <20161127213608.GA30774@jasmine> (raw)
In-Reply-To: <5d79f3b3-6acf-54d8-d790-b4ec0d77656d@tobias.gr>

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

On Sun, Nov 27, 2016 at 10:12:13PM +0100, Tobias Geerinckx-Rice wrote:
> On 27/11/16 21:55, Leo Famulari wrote:
> > Can you double-check that there are no unpatched named bugs in this
> > version?
> 
> Already did ;-)
> 
> According to [1], there are three known CVEs, all fixed by 1.4.2.
> 
> I didn't find any third party security patches being applied anywhere,
> either.
> 
> Do you have suspicions otherwise?

Nope! Just wanted to be sure :)

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

      reply	other threads:[~2016-11-27 21:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-27 20:17 [PATCH 1/2] gnu: Add libjpeg-turbo Tobias Geerinckx-Rice
2016-11-27 20:17 ` [PATCH 2/2] gnu: icecat: Use libjpeg-turbo instead of bundled libjpeg Tobias Geerinckx-Rice
2016-11-27 20:56   ` Leo Famulari
2016-11-27 21:02     ` Tobias Geerinckx-Rice
2016-11-27 21:41       ` Leo Famulari
2016-11-27 21:50         ` Marius Bakke
2016-11-27 22:28           ` Marius Bakke
2016-11-27 22:44             ` Leo Famulari
2016-11-27 22:43           ` Leo Famulari
2016-11-27 23:15         ` Tobias Geerinckx-Rice
2016-11-27 23:20           ` Tobias Geerinckx-Rice
2016-11-27 23:42             ` Leo Famulari
2016-11-27 23:27           ` Leo Famulari
2016-11-27 20:55 ` [PATCH 1/2] gnu: Add libjpeg-turbo Leo Famulari
2016-11-27 21:12   ` Tobias Geerinckx-Rice
2016-11-27 21:36     ` Leo Famulari [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

  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=20161127213608.GA30774@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    /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).