From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45563) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1en319-0004Q6-3c for guix-patches@gnu.org; Sat, 17 Feb 2018 08:59:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1en314-0001fB-9t for guix-patches@gnu.org; Sat, 17 Feb 2018 08:59:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:39722) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1en314-0001eu-6D for guix-patches@gnu.org; Sat, 17 Feb 2018 08:59:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1en313-0006qf-Oh for guix-patches@gnu.org; Sat, 17 Feb 2018 08:59:01 -0500 Subject: [bug#30441] [PATCH] gnu: boost: Update to 1.66.0. Resent-Message-ID: Date: Sat, 17 Feb 2018 14:58:07 +0100 From: Andreas Enge Message-ID: <20180217135807.GB17522@jurong> References: <20180212233358.4911-1-arunisaac@systemreboot.net> <20180213194633.GA1536@jasmine.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180213194633.GA1536@jasmine.lan> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Leo Famulari Cc: 30441@debbugs.gnu.org Hello, On Tue, Feb 13, 2018 at 02:46:33PM -0500, Leo Famulari wrote: > This is a change for the next core-updates cycle, so I put it on my > local core-updates-next branch. But please try to remember it, too :) would it not be better to build it (after the next core-updates merge, or even the next release) on a feature branch? There are new releases of mpfr and mpc; it would be nice to have a quick core-updates run with these packages that really belong to the core (together with a few others, maybe, like glibc?) right after the next guix release. Andreas