From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Dealing with mass rebuilds
Date: Tue, 20 Oct 2015 21:45:54 +0200 [thread overview]
Message-ID: <8737x5e32l.fsf_-_@gnu.org> (raw)
In-Reply-To: <87zizd2ymv.fsf@netris.org> (Mark H. Weaver's message of "Tue, 20 Oct 2015 14:17:12 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> Andreas Enge <andreas@enge.fr> writes:
>
>> andreas pushed a commit to branch master
>> in repository guix.
>>
>> commit 075c3ebd2dc3d8223e23025ceb5026810dfaa98d
>> Author: Andreas Enge <andreas@enge.fr>
>> Date: Sun Oct 18 12:20:02 2015 +0200
>>
>> gnu: curl: Update to 7.45.0.
>
> To avoid unnecessary rebuilds on hydra, I reverted this commit on
> master, and instead pushed it to the 'dbus-update' branch, which will
> hopefully be merged soon.
We’re talking of ~150 dependent packages, which to me sounded OK¹.
If we delay obvious changes like this too much, the risk is to end up
with upgrade-everything branches that take ages to get merged (what is
happening with ‘dbus-update’.)
The Nixpkgs folks have a ‘staging’ branch for changes that cause mass
rebuilds but are well tested, such that they can be merged into ‘master’
anytime². Perhaps something we should do as well?
Ludo’.
¹ https://lists.gnu.org/archive/html/guix-devel/2015-10/msg00653.html
² http://comments.gmane.org/gmane.linux.distributions.nixos/13447
next prev parent reply other threads:[~2015-10-20 19:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151020161651.4759.8347@vcs.savannah.gnu.org>
[not found] ` <E1ZoZal-0001Fl-M5@vcs.savannah.gnu.org>
2015-10-20 18:17 ` 01/01: gnu: curl: Update to 7.45.0 Mark H Weaver
2015-10-20 19:45 ` Ludovic Courtès [this message]
2015-10-20 19:56 ` Dealing with mass rebuilds Efraim Flashner
2015-10-20 21:47 ` Andreas Enge
2015-10-21 7:27 ` Efraim Flashner
2015-10-21 16:41 ` Ludovic Courtès
2015-10-21 16:45 ` Ludovic Courtès
2015-10-22 20:11 ` Paul van der Walt
2015-10-25 21:34 ` Ludovic Courtès
2015-10-22 18:20 ` Mark H Weaver
2015-10-22 18:32 ` Andreas Enge
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=8737x5e32l.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
/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).