unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: Successfully running GNOME on core-updates + staging
Date: Sun, 22 Apr 2018 21:55:39 +0200	[thread overview]
Message-ID: <871sf7hv7o.fsf@gnu.org> (raw)
In-Reply-To: <8736zp571h.fsf@netris.org> (Mark H. Weaver's message of "Sat, 21 Apr 2018 03:54:02 -0400")

Hi Mark,

Mark H Weaver <mhw@netris.org> skribis:

> I've successfully updated my x86_64 GuixSD system to my private branch
> based on 'core-updates' with recent 'master' and 'staging' merged into
> it.  This system includes a full GNOME desktop environment plus a few
> programs based on Qt.  It all works quite well.
>
> My branch includes a few draft fixes and workarounds that I haven't yet
> pushed, but nothing that would require many rebuilds to update later.
>
> So, I think it might be time to ask Hydra to build all of core-updates,
> after staging is merged into it.

I agree.  There was an issue with cross-compiling ‘bootstrap-tarballs’
that Marius reported a few days ago, which I’m looking into right now.
I don’t expect the fix(es) to trigger a full rebuild.

If Marius and others don’t object, I’d say go for it!

Thanks,
Ludo’.

  reply	other threads:[~2018-04-22 19:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-21  7:54 Successfully running GNOME on core-updates + staging Mark H Weaver
2018-04-22 19:55 ` Ludovic Courtès [this message]
2018-04-23 18:13   ` Marius Bakke
2018-04-25 12:14     ` Ludovic Courtès
2018-04-25 13:23       ` Efraim Flashner
2018-05-01 14:12       ` Starting 'core-updates' Marius Bakke
2018-05-01 14:23         ` Leo Famulari
2018-05-01 18:23           ` Mark H Weaver
2018-05-01 20:46             ` Ludovic Courtès
2018-05-01 21:21               ` Mark H Weaver

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=871sf7hv7o.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).