From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Time to build ‘staging’!
Date: Sun, 11 Dec 2016 15:03:08 -0500 [thread overview]
Message-ID: <20161211200308.GE20766@jasmine> (raw)
In-Reply-To: <87h96a9sbq.fsf@netris.org>
On Sun, Dec 11, 2016 at 02:30:33PM -0500, Mark H Weaver wrote:
> ludo@gnu.org (Ludovic Courtès) writes:
>
> > Leo Famulari <leo@famulari.name> skribis:
> >
> >> On Sun, Dec 04, 2016 at 05:43:36PM +0100, Marius Bakke wrote:
> >>> Ludovic Courtès <ludo@gnu.org> writes:
> >>>
> >>> > Hi Guix!
> >>> >
> >>> > It’s time to merge master into staging and build it!
> >>> >
> >>> > Leo, Marius: thoughts? Since you’re the one who did most of the work
> >>> > there, I suggest that you do this (Leo has access to Hydra).
> >>>
> >>> I just did a master merge and picked the mupdf update. I think it's good
> >>> to go! :-)
> >>
> >> I've created a staging jobset and asked Hydra to evaluate it:
> >>
> >> https://hydra.gnu.org/jobset/gnu/staging
> >
> > It would seem to be ready to merge:
> >
> > https://hydra.gnu.org/eval/109391?compare=master#tabs-now-fail
> >
> > The few remaining failures on x86_64 seem to be transient. There are
> > more failures on mips, part of which is due to massive test failures in
> > Subversion (see
> > <https://hydra.gnu.org/build/1683944/nixlog/1/tail-reload>), which look
> > fishy.
> >
> > I’d be in favor of merging now though.
> >
> > What do people think?
>
> Sounds fine to me.
Okay, shall I go ahead and do it?
next prev parent reply other threads:[~2016-12-11 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 15:40 Time to build ‘staging’! Ludovic Courtès
2016-12-04 16:43 ` Marius Bakke
2016-12-04 18:11 ` Leo Famulari
2016-12-11 18:40 ` Ludovic Courtès
2016-12-11 19:08 ` Marius Bakke
2016-12-11 19:31 ` Leo Famulari
2016-12-11 19:30 ` Mark H Weaver
2016-12-11 20:03 ` Leo Famulari [this message]
2016-12-11 21:58 ` Leo Famulari
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=20161211200308.GE20766@jasmine \
--to=leo@famulari.name \
--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).