From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: Re: Starting 'core-updates' Date: Tue, 01 May 2018 14:23:28 -0400 Message-ID: <87zi1j5j6n.fsf@netris.org> References: <8736zp571h.fsf@netris.org> <871sf7hv7o.fsf@gnu.org> <877eoxaj01.fsf@fastmail.com> <87po2ntreb.fsf@gnu.org> <87lgd3h3c5.fsf@fastmail.com> <20180501142320.GA14610@jasmine.lan> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34922) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fDZxT-0005t7-4g for guix-devel@gnu.org; Tue, 01 May 2018 14:25:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fDZxP-0002zo-TU for guix-devel@gnu.org; Tue, 01 May 2018 14:24:59 -0400 Received: from world.peace.net ([64.112.178.59]:58904) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fDZxP-0002xB-Q8 for guix-devel@gnu.org; Tue, 01 May 2018 14:24:55 -0400 In-Reply-To: <20180501142320.GA14610@jasmine.lan> (Leo Famulari's message of "Tue, 1 May 2018 10:23:20 -0400") 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: Leo Famulari Cc: guix-devel@gnu.org Leo Famulari writes: > 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. >> >> * 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. >> >> 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. I agree. I've been running core-updates for a long time now. It works. The 'rhash' update has forced a great deal of rebuilding on it (my X200 has been rebuilding all night, and is still going), but I do not expect that it will cause any new problems. The further updates on -next might very well cause more bugs that need to be investigated and fixed. The reason that I moved my own systems so agressively to core-updates this cycle is because I no longer trust that grafting works properly on 'master', and so security flaws might not be fully addressed there. I'm disappointed that there have been so many delays since then, and I'd prefer not to add any more. What do you think? Mark