From: Mark H Weaver <mhw@netris.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-Devel <guix-devel@gnu.org>
Subject: Re: ‘staging’ merged!
Date: Wed, 01 May 2019 18:54:38 -0400 [thread overview]
Message-ID: <874l6dn5ti.fsf@netris.org> (raw)
In-Reply-To: <87k1feb7u0.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sun, 28 Apr 2019 15:03:19 +0200")
Hi Ludovic,
Ludovic Courtès <ludo@gnu.org> writes:
> I’m happy to report that I’ve finally merged ‘staging’! The branch
> brings lots of updates, notably GNOME 2.28 (was 2.24).
>
> Up-to-date substitutes are available from <https://ci.guix.info>.
I notice that 'staging' was not built on Hydra before it was merged, or
at least not more than a couple of days before. Now that Hydra is
finally building it, many problems are becoming evident, especially on
armhf-linux.
Have we abandoned the practice of building out experimental branches on
Hydra before merging them? Does Berlin now have a significantly better
interface that would allow us to spot problems like the ones that Hydra
is now (belatedly) bringing to light? Was Berlin able to build out
'staging' on armhf-linux before this merge?
Mark
next prev parent reply other threads:[~2019-05-01 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-28 13:03 ‘staging’ merged! Ludovic Courtès
2019-05-01 22:54 ` Mark H Weaver [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-02-09 14:57 Ludovic Courtès
2019-02-09 15:06 ` Amirouche Boubekki
2019-02-10 0:02 ` Chris Marusich
2019-02-09 17:51 ` Björn Höfling
2019-02-09 19:33 ` Christopher Baines
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=874l6dn5ti.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 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).