From: Timothy Sample <samplet@ngyro.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Stackage LTS 14
Date: Mon, 04 Nov 2019 00:16:11 -0500 [thread overview]
Message-ID: <87sgn4xlus.fsf@ngyro.com> (raw)
In-Reply-To: <87h83oz1bx.fsf@ngyro.com> (Timothy Sample's message of "Fri, 01 Nov 2019 00:07:30 -0400")
Hi all,
Timothy Sample <samplet@ngyro.com> writes:
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> Yes, you can take over wip-haskell-updates.
>
> Great! I’ve pushed a new branch with updated Haskell packages. It’s a
> little messy yet, but I want the build farm to help me find build
> problems before cleaning up too much. I updated all the packages using
> “guix refresh”, and then built and fixed enough to build “ghc-aeson”.
> There were a lot of problems, some of which I fixed with “squash!”
> commits that I can squash later. (I’m hoping that using “squash!”
> commits to fix the “guix refresh” commits will make collaboration
> easier, but maybe it will just give me a headache later when I have to
> squash everything – we’ll see!)
The build farm seems to have stalled, but I have not!
I have “xmonad”, “darcs”, “ghc-pandoc”, and “git-annex” all building
(locally) on top of GHC 8.6, which means that we’re nearly there.
Unfortunately, the mess is getting to be too much, so I plan to clean it
up tomorrow and then push a new, cleaner version of
“wip-haskell-updates”. There are few minor things to discuss, which I
will gather as I tidy up the commits.
After that, I’m hoping that some others will help with a few of the
final problems (especially the R packages, about which I know little).
I have not checked on Agda or Idris yet either. In any case, you might
as well wait until I do the cleaning.
Stay tuned!
-- Tim
next prev parent reply other threads:[~2019-11-04 5:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-21 20:42 Adding Purescript John Soo
2019-10-22 0:32 ` Stackage LTS 14 (was: Adding Purescript) Timothy Sample
2019-10-22 11:57 ` Ricardo Wurmus
2019-10-23 17:59 ` Marius Bakke
2019-11-01 4:07 ` Stackage LTS 14 Timothy Sample
2019-11-04 5:16 ` Timothy Sample [this message]
2019-11-09 5:12 ` Timothy Sample
2019-11-12 6:58 ` Timothy Sample
2019-11-12 16:16 ` John Soo
2019-11-12 20:18 ` Timothy Sample
2019-11-14 9:38 ` John Soo
2019-11-14 14:53 ` Timothy Sample
2019-11-14 15:18 ` Marius Bakke
2019-11-14 19:03 ` John Soo
2019-11-14 20:30 ` Timothy Sample
2019-11-14 21:09 ` John Soo
2019-11-17 0:42 ` Timothy Sample
2019-11-17 16:13 ` Timothy Sample
2019-11-19 22:16 ` Marius Bakke
2019-11-21 2:20 ` Timothy Sample
2019-11-21 4:40 ` John Soo
2019-11-21 10:12 ` Efraim Flashner
2019-11-21 18:32 ` Marius Bakke
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=87sgn4xlus.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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).