From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#22831: [PATCH 2/2] WIP: gnu: openssl: Restrict allowed references for openssl. Date: Tue, 1 Mar 2016 16:04:40 -0500 Message-ID: <20160301210440.GA18336@jasmine> References: <20160301072025.GA26797@jasmine> <877fhmorj1.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56185) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aarTe-0006HD-O1 for bug-guix@gnu.org; Tue, 01 Mar 2016 16:05:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aarTa-0008Ez-TO for bug-guix@gnu.org; Tue, 01 Mar 2016 16:05:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:59636) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aarTa-0008Ek-Qw for bug-guix@gnu.org; Tue, 01 Mar 2016 16:05:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aarTa-0008Uk-FM for bug-guix@gnu.org; Tue, 01 Mar 2016 16:05:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: <877fhmorj1.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 22831@debbugs.gnu.org On Tue, Mar 01, 2016 at 09:46:26PM +0100, Ludovic Courtès wrote: > Leo Famulari skribis: > > > From 00807e4421757f8d9204f1601de9a8286a408f91 Mon Sep 17 00:00:00 2001 > > From: Leo Famulari > > Date: Mon, 29 Feb 2016 19:24:20 -0500 > > Subject: [PATCH] gnu: openssl: Restrict allowed references for openssl. > > > > * gnu/packages/tls.scm (openssl)[arguments]: Add #:allowed-references. > > For some reason I hadn’t seen it in M-x debbugs-gnu for this report > today, but the patch looks good to me! > > If we apply it now, it won’t trigger a rebuild (yay!), but will still > trigger a bunch of regrafting, which is slightly annoying. What about > applying it in the next ‘security-updates’ branch? Sure. Is it okay if I create that branch? > > Thanks! > > Ludo’.