From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: Starting 'core-updates' Date: Tue, 1 May 2018 10:23:20 -0400 Message-ID: <20180501142320.GA14610@jasmine.lan> References: <8736zp571h.fsf@netris.org> <871sf7hv7o.fsf@gnu.org> <877eoxaj01.fsf@fastmail.com> <87po2ntreb.fsf@gnu.org> <87lgd3h3c5.fsf@fastmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="yrj/dFKFPuw6o+aM" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50188) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fDWBi-0005PC-VR for guix-devel@gnu.org; Tue, 01 May 2018 10:23:27 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fDWBf-0003Ns-Pe for guix-devel@gnu.org; Tue, 01 May 2018 10:23:26 -0400 Content-Disposition: inline In-Reply-To: <87lgd3h3c5.fsf@fastmail.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Marius Bakke Cc: guix-devel@gnu.org --yrj/dFKFPuw6o+aM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 01, 2018 at 04:12:42PM +0200, Marius Bakke wrote: > I was running a bit late with my patches and pushed them to a separate > branch before noticing the 'rhash' update on 'master'. Now there have > been a couple of world-rebuilding commits on the 'core-updates-next' > branch since, so I wonder how to move forward. >=20 > * Start 'core-updates' as-is. > * Pick all updates from the -next branch that won't rebuild the world > (that is everything apart from "xz" and "file"). > * Take all the -next commits, remove the Perl graft, and do a new 'core' > evaluation. >=20 > Any preferences? Due to the "rhash" update, I suppose we can take > anything from -next that depends on CMake also with option #1. I haven't been paying attention this cycle. But if anyone has, then I think it's best to do option 1 along with the rhash, since most of the bug-fixing work will still be valid. --yrj/dFKFPuw6o+aM Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEsFFZSPHn08G5gDigJkb6MLrKfwgFAlroeFUACgkQJkb6MLrK fwhFOBAA51HdwdQ/hC2fBD/kuMNBvl7uC/lrtOQPxRQofKVzSurspoK10NVCXTb5 JEUyRUWySGk4oyZusGsYth/zLpvLUtG23cPVKPuNqf+6Y6+C1Fk4SP9YrQMXTSSw vqgTCvO/Ps+rplTpQR2UQD4L9Ck30YDo8h5QPvUKq3XbGGMIyeOeGjgSFv8V7u2U O+Ps/FW4hJxmjPcLDDoZWEsPfbM+6mc/lgryJ9tDnwnGDI1T1hO2hKZmZB0UfdB1 y4UJTiYy/CGkDY2yoLuDgovnZi9xBzgJF93jVUyqzzH8QGwmnUpOZf8H/Z9+vqE6 md57mHJtc0klXwWb2Kwh/AYfVNtkAek2IH9svLMzIGJBXlSAAj/H3UJIfgI+Jvqw ZQYuPZTVGGWUX67FoHPO4iErKmPFcG47CztGhVhuJ3NTxoMfmfmSH7+RCRXK/LRU RjiObrQxrOAL6zOL/dZNIPXM+DozYRfCelGOfi59StG2iST/4p7v0YvddQwOqxMu qq7ultid7HFNj8e+VDcTCl5kykR1IwfkoXDs5HiTbmwfcS4E26U8vS7ez52b44OF 4CiRMcQqmBKeIVrmFXB8zOq9u/Ao5Pa39s71oDk+zR/Ssm9w+Y5uMlnd/nVzLNp3 +qc+nCNpmbE7xyzS/n6LfKTnkO0C+44pagAiFdZq03gl1x2r1yk= =zmwr -----END PGP SIGNATURE----- --yrj/dFKFPuw6o+aM--