From: Ricardo Wurmus <rekado@elephly.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: core-updates, last call?
Date: Sun, 18 Feb 2018 00:16:09 +0100 [thread overview]
Message-ID: <87lgfr5hs6.fsf@elephly.net> (raw)
In-Reply-To: <20180217202408.GA18836@jasmine.lan>
Leo Famulari <leo@famulari.name> writes:
> On Sat, Feb 17, 2018 at 03:00:59PM -0500, Mark H Weaver wrote:
>> Ricardo Wurmus <rekado@elephly.net> writes:
>> > I’ll merge core-updates into master now.
>>
>> Is that premature? There are still over 500 newly failed jobs on
>> core-updates compared to master.
>>
>> https://hydra.gnu.org/eval/109914?compare=109912
>
> Since GHC is still broken, I agree it's premature.
But it’s not broken. Some of our messages crossed, but the latest
status is that with my change to ghc-mtl we can build ghc-resourcet
now. So GHC is fine and all of the Haskell packages are fine.
We just didn’t start a new evaluation since then.
> Otherwise, are there any in particular that count as "blockers"?
>
> We've been preparing this branch for quite a while and nobody has been
> motivated to fix them...
I don’t see any blockers any more.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-02-17 23:16 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 12:48 heads-up: Haskell updates Ricardo Wurmus
2018-02-14 14:20 ` Ludovic Courtès
2018-02-14 16:46 ` Ricardo Wurmus
2018-02-14 18:46 ` Mark H Weaver
2018-02-14 19:19 ` Ricardo Wurmus
2018-02-14 19:39 ` Ricardo Wurmus
2018-02-14 19:44 ` Ricardo Wurmus
2018-02-14 21:23 ` Mark H Weaver
2018-02-14 21:39 ` Andreas Enge
2018-02-14 22:42 ` Ricardo Wurmus
2018-02-14 22:47 ` Danny Milosavljevic
2018-02-15 8:41 ` Mark H Weaver
2018-02-15 9:17 ` Ricardo Wurmus
2018-02-15 10:38 ` Mark H Weaver
2018-02-15 14:02 ` Timothy Sample
2018-02-15 15:05 ` Ricardo Wurmus
2018-02-17 12:50 ` Ricardo Wurmus
2018-02-17 13:04 ` Ricardo Wurmus
2018-02-17 15:18 ` Andreas Enge
2018-02-17 16:11 ` Ricardo Wurmus
2018-02-17 20:00 ` Mark H Weaver
2018-02-17 20:24 ` core-updates, last call? Leo Famulari
2018-02-17 23:16 ` Ricardo Wurmus [this message]
2018-02-18 21:45 ` Pjotr Prins
2018-02-18 22:44 ` Ricardo Wurmus
2018-02-18 20:42 ` heads-up: Haskell updates Chris Marusich
2018-02-15 10:29 ` Mark H Weaver
2018-02-15 11:04 ` Danny Milosavljevic
2018-02-15 11:08 ` Danny Milosavljevic
2018-02-15 11:12 ` Andreas Enge
2018-02-15 15:44 ` Ricardo Wurmus
2018-02-15 17:03 ` Danny Milosavljevic
2018-02-15 17:46 ` Leo Famulari
2018-02-15 18:12 ` Mark H Weaver
2018-02-16 15:26 ` Danny Milosavljevic
2018-02-16 16:31 ` Marius Bakke
2018-02-16 17:43 ` Ricardo Wurmus
2018-02-16 18:12 ` Marius Bakke
2018-02-16 18:29 ` Leo Famulari
2018-02-16 22:14 ` Mark H Weaver
2018-02-16 18:15 ` Mark H Weaver
2018-02-17 0:33 ` Ricardo Wurmus
2018-02-17 12:11 ` Oleg Pykhalov
2018-02-17 12:18 ` Ricardo Wurmus
2018-02-17 12:55 ` Oleg Pykhalov
2018-02-17 13:00 ` Ricardo Wurmus
2018-02-17 13:38 ` Timothy Sample
2018-02-17 14:42 ` Ricardo Wurmus
2018-02-17 16:04 ` Timothy Sample
2018-02-17 23:22 ` Ricardo Wurmus
2018-02-17 15:51 ` Oleg Pykhalov
2018-02-17 19:48 ` Mark H Weaver
2018-02-17 19:54 ` Mark H Weaver
2018-02-17 21:51 ` Danny Milosavljevic
2018-02-17 22:32 ` Timothy Sample
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=87lgfr5hs6.fsf@elephly.net \
--to=rekado@elephly.net \
--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).