From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Dealing with mass rebuilds
Date: Thu, 22 Oct 2015 14:20:08 -0400 [thread overview]
Message-ID: <871tcmkbon.fsf@netris.org> (raw)
In-Reply-To: <8737x5e32l.fsf_-_@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\?\= \=\?utf-8\?Q\?\=22's\?\= message of "Tue, 20 Oct 2015 21:45:54 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> 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¹.
After applying the 'giflib' and 'curl' updates to the 'dbus-update'
branch (and also merging master), the number of queued jobs on that
jobset went from about 1000 to over 2200. Based on this, and also based
on my past memories of curl security updates, I suspect that this is
another case where "guix refresh -l" drastically underestimated the
number of rebuilds.
Mark
next prev parent reply other threads:[~2015-10-22 18:20 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 ` Dealing with mass rebuilds Ludovic Courtès
2015-10-20 19:56 ` 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871tcmkbon.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.