From: Mark H Weaver <mhw@netris.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Staging
Date: Fri, 21 Apr 2017 14:59:23 -0400 [thread overview]
Message-ID: <87y3uty4c4.fsf@netris.org> (raw)
In-Reply-To: <20170421174734.GD3370@jasmine> (Leo Famulari's message of "Fri, 21 Apr 2017 13:47:34 -0400")
Leo Famulari <leo@famulari.name> writes:
> On Fri, Apr 21, 2017 at 03:57:41PM +0200, Marius Bakke wrote:
>> Looks like the queue was cancelled.
>>
>> https://hydra.gnu.org/eval/109614?compare=master
>>
>> Should we try to build out the remaining packages? There have been a few
>> large updates in 'master', might be useful to merge that first. Or just
>> go the other way around.. ;-)
>
> Most likely the queue was paused to make way for the security-updates
> jobset:
>
> https://hydra.gnu.org/jobset/gnu/security-updates
Yes, I cancelled the builds in 'staging' so that Hydra would focus on
rebuilding 'security-updates', whose patches have since been applied to
master.
Unfortunately, the recent 'imlib2' update rendered most of that
rebuilding obsolete, and now we need to rebuild the web browsers,
libreoffice, and Qt/KDE all over again. Oh well.
Anyway, here's what I'd recommend: after the most important packages are
rebuilt on 'master', let's merge 'master' into 'staging' and start
another evaluation of 'staging'.
What do you think?
Mark
next prev parent reply other threads:[~2017-04-21 18:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170412162650.31333-1-mbakke@fastmail.com>
[not found] ` <87r30unafo.fsf@openmailbox.org>
[not found] ` <8737d9obe8.fsf@fastmail.com>
[not found] ` <87d1calthj.fsf@fastmail.com>
2017-04-17 20:09 ` Staging Leo Famulari
2017-04-18 17:00 ` Staging Marius Bakke
2017-04-18 18:52 ` [staging] Mesa FTBFS on 32-bit architectures Leo Famulari
2017-04-18 19:30 ` Leo Famulari
2017-04-18 23:52 ` Leo Famulari
2017-04-19 0:02 ` Marius Bakke
2017-04-19 0:13 ` Leo Famulari
2017-04-19 0:17 ` Marius Bakke
2017-04-19 22:03 ` Leo Famulari
2017-04-19 0:37 ` Leo Famulari
2017-04-21 13:57 ` Staging Marius Bakke
2017-04-21 17:47 ` Staging Leo Famulari
2017-04-21 18:59 ` Mark H Weaver [this message]
2017-04-21 19:05 ` Staging Leo Famulari
2017-04-23 9:45 ` Staging Marius Bakke
2017-04-23 9:49 ` Staging Marius Bakke
2017-04-25 18:33 ` Staging Leo Famulari
2017-04-27 4:49 ` Staging merged! Leo Famulari
2017-04-27 6:40 ` Ricardo Wurmus
2017-04-27 13:50 ` Ludovic Courtès
2018-02-20 1:46 Staging Leo Famulari
2018-02-20 3:54 ` Staging Marius Bakke
2018-02-20 9:45 ` Staging Efraim Flashner
2018-02-20 11:57 ` Staging Leo Famulari
2018-02-20 12:07 ` Staging Andreas Enge
2018-02-20 13:05 ` Staging Arun Isaac
2018-02-20 13:14 ` Staging Efraim Flashner
2018-02-20 13:17 ` Staging Andreas Enge
2018-02-20 14:23 ` Staging Efraim Flashner
2018-02-23 22:29 ` Staging Ludovic Courtès
2018-02-21 18:22 ` Staging Leo Famulari
2018-02-23 16:55 ` Staging Leo Famulari
2018-02-22 17:09 ` Staging Ricardo Wurmus
2018-02-22 17:29 ` Staging Gábor Boskovits
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=87y3uty4c4.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).