unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: boost: Update to 1.61.0.
Date: Tue, 27 Sep 2016 21:13:10 +0200	[thread overview]
Message-ID: <20160927191310.GA1964@solar> (raw)
In-Reply-To: <8760pnzlbt.fsf@ike.i-did-not-set--mail-host-address--so-tickle-me>

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

      parent reply	other threads:[~2016-09-27 19:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19  8:13 [PATCH] gnu: boost: Update to 1.61.0 Roel Janssen
2016-09-19 10:11 ` Roel Janssen
2016-09-19 12:26   ` Ricardo Wurmus
2016-09-19 20:31   ` Efraim Flashner
2016-09-19 21:09   ` Eric Bavier
2016-09-20  9:10     ` Roel Janssen
2016-09-20 20:58       ` Eric Bavier
2016-09-20 21:44         ` Leo Famulari
2016-09-22 17:14         ` Eric Bavier
2016-09-22 19:03           ` Roel Janssen
2016-09-21 16:11   ` Andreas Enge
2016-09-21 17:27     ` Andreas Enge
2016-09-22 21:16       ` Marius Bakke
2016-09-23 17:05         ` Eric Bavier
2016-09-27 19:13         ` Andreas Enge [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160927191310.GA1964@solar \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).