From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=)
Subject: Re: [PATCH] version bump libgcrypt -> 1.7
Date: Sun, 24 Apr 2016 16:23:22 +0200
Message-ID: <871t5vgk6d.fsf@gnu.org>
References: <877ffx45n6.fsf@libertad.pw> <8737qkeknd.fsf@gmail.com>
	<87oa98ftn4.fsf@libertad.pw> <20160418203241.GA26832@jasmine>
	<87twiwqkk3.fsf@gnu.org> <20160421163242.GB10513@jasmine>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46990)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1auKwc-0000pJ-1j
	for guix-devel@gnu.org; Sun, 24 Apr 2016 10:23:30 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ludo@gnu.org>) id 1auKwb-0007Dc-5D
	for guix-devel@gnu.org; Sun, 24 Apr 2016 10:23:29 -0400
In-Reply-To: <20160421163242.GB10513@jasmine> (Leo Famulari's message of "Thu,
	21 Apr 2016 12:32:42 -0400")
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>

Leo Famulari <leo@famulari.name> skribis:

> On Wed, Apr 20, 2016 at 07:03:40PM +0200, Ludovic Court=C3=A8s wrote:
>> Leo Famulari <leo@famulari.name> skribis:
>>=20
>> > On Sun, Apr 17, 2016 at 11:53:51AM +0200, ng0 wrote:
>> >> Updated libgcrypt patch.
>> >
>> > Is there a consensus on upgrading from 1.6.5 and making the change on
>> > core-updates?
>>=20
>> OK for doing it in =E2=80=98core-updates=E2=80=99!
>
> Done in 81068f178.
>
>> In an ideal world, we=E2=80=99d do it in a separate branch to check for
>> breakage, but currently we lack the computational resources to do so.
>
> I'm going to build a new system with some changes to core packages. I
> could test this change as well. Are there any libgcrypt-dependent
> packages I should pay particular attention to?

Not particularly.  This new version is API- and ABI-compatible, so I=E2=80=
=99m
rather confident.

Ludo=E2=80=99.