From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Re: [PATCH] gnu: boost: Update to 1.61.0. Date: Tue, 27 Sep 2016 21:13:10 +0200 Message-ID: <20160927191310.GA1964@solar> References: <8737kw2tp8.fsf@gnu.org> <871t0g2o7m.fsf@gnu.org> <20160921161131.GA3358@solar> <20160921172733.GA7544@solar> <8760pnzlbt.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39900) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1boxod-0003RC-Qo for guix-devel@gnu.org; Tue, 27 Sep 2016 15:13:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1boxoa-0006RH-KU for guix-devel@gnu.org; Tue, 27 Sep 2016 15:13:19 -0400 Received: from mailrelay7.public.one.com ([91.198.169.215]:17517) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1boxoa-0006QK-7s for guix-devel@gnu.org; Tue, 27 Sep 2016 15:13:16 -0400 Content-Disposition: inline In-Reply-To: <8760pnzlbt.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me> 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 On Thu, Sep 22, 2016 at 10:16:54PM +0100, Marius Bakke wrote: > Should this not be pushed to core-updates? `guix refresh -l` reports: > > Building the following 190 packages would ensure 395 dependent packages > are rebuilt: [...] > > That will take a while on Hydra, and in the mean time anyone trying to > install any dependent (or sub-dependent) package will have to compile > them locally. > > Unless there is a security issue, isn't this exactly what core-updates > is for? Not quite. Initially, core-updates was for updates of the core packages, that is, those that you can currently see being built on the core-updates branch of hydra. With the lack of performance of hydra, we ended up putting more and more packages requiring large rebuilds into that branch. Often, we also just add a feature branch (something-update) and have it built on hydra, especially also in cases where it is unclear how much we break by the update, to make sure that master remains in a workable state. After the hydra machine crashed, the FSF sysadmins switched to a more powerful set-up, and right now, we can tolerate a larger package churn. In case of doubt when updating a package requiring larger rebuilds, we can also have it depend on the current load on hydra towards which branch we push. Andreas