From mboxrd@z Thu Jan  1 00:00:00 1970
From: mhw@netris.org
Subject: Re: [PATCH] gnu: glibc: Fix CVE-2014-5519
Date: Thu, 28 Aug 2014 01:34:38 -0400
Message-ID: <87vbpd18k1.fsf@netris.org>
References: <874mwz2ha5.fsf@netris.org> <87y4uanv7d.fsf@gnu.org>
	<20140827093105.GA18955@debian> <87r402ktr6.fsf@gnu.org>
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]:56511)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mhw@netris.org>) id 1XMsMU-0002TM-Ai
	for guix-devel@gnu.org; Thu, 28 Aug 2014 01:35:11 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mhw@netris.org>) id 1XMsMO-0004iU-W4
	for guix-devel@gnu.org; Thu, 28 Aug 2014 01:35:06 -0400
In-Reply-To: <87r402ktr6.fsf@gnu.org> ("Ludovic
	\=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\=
	\=\?utf-8\?Q\?s\?\= message of "Wed, 27 Aug 2014 14:21:49 +0200")
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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org

ludo@gnu.org (Ludovic Court=C3=A8s) writes:

> Andreas Enge <andreas@enge.fr> skribis:
>
>> On Wed, Aug 27, 2014 at 11:22:14AM +0200, Ludovic Court=C3=A8s wrote:
>>> So I=E2=80=99m inclined to just leave it on core-updates for now.  WDYT?
>>
>> As the fix entails essentially a complete rebuild of our packages, how a=
bout
>> merging core-updates back into master now?
>
> I=E2=80=99m not sure what the status of core-updates is.  There are poten=
tially
> disruptive changes in there, which is why I=E2=80=99d be a bit wary.  Mar=
k?

I've been building core-updates on i686, and it seems fine.  While the
changes force a full rebuild, they do not seem likely to cause many
problems.

I think we should ask hydra to build all of core-updates and then merge
core-updates into master.

What do others think?

      Mark