From: John Kehayias <john.kehayias@protonmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Philip Munksgaard <philip@munksgaard.me>, guix-devel@gnu.org
Subject: Re: Create branch for Haskell build changes and updates?
Date: Tue, 27 Jul 2021 21:24:17 +0000 [thread overview]
Message-ID: <38M76MJzGQQSzvRBewMNjeNDrD8T1WKZL-PEzGPzrv11Y41mcghcx4sJc9dOE_yz-FyNZ7A517aJkzUxMR2k18bXcbcfQoC-oFPIUwDvExw=@protonmail.com> (raw)
In-Reply-To: <87mtqf4blh.fsf@elephly.net>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, July 21st, 2021 at 5:10 PM, Ricardo Wurmus wrote:
> Ricardo Wurmus rekado@elephly.net writes:
>
> > Philip Munksgaard philip@munksgaard.me writes:
> >
> > > Who do we talk to to get this in place?
> >
> > Me, for example.
> >
> > Sorry, I got sick and haven’t been doing anything towards
> >
> > getting
> >
> > wip-haskell started.
> >
> > I’ll try to do this tonight:
> >
> > - branch off wip-haskell from core-updates
> > - apply https://issues.guix.gnu.org/49199
> > - create a new job set for wip-haskell
>
> wip-haskell is being built now:
>
> https://ci.guix.gnu.org/eval/65335/dashboard
>
Great, thanks! I was away for a bit and catching up now.
Some failing builds are lacking a proper backtrace, e.g. https://ci.guix.gnu.org/build/680388/details Perhaps it is what is referred to as fixed in this more recent commit in core-updates: https://git.savannah.gnu.org/cgit/guix.git/commit/?h=core-updates&id=a0f880afea3b29e817866de0170ed579738db2d1
In any event, going forward we can apply any Haskell patches here, and probably the big one is to update GHC and Stackage resolver? Is there any automated way to updating a large number of packages to get started? Some will require manual help, but at least we can start with getting all versions to whichever Stackage resolver we update to.
John
next prev parent reply other threads:[~2021-07-27 21:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 17:24 Create branch for Haskell build changes and updates? John Kehayias
2021-07-07 5:47 ` Xinglu Chen
2021-07-07 14:47 ` John Kehayias
2021-07-07 15:02 ` John Soo
2021-07-08 17:45 ` Xinglu Chen
2021-07-09 14:06 ` Ricardo Wurmus
2021-07-09 15:21 ` John Kehayias
2021-07-09 16:44 ` Ricardo Wurmus
2021-07-09 18:45 ` John Kehayias
2021-07-10 15:39 ` Xinglu Chen
2021-07-20 11:58 ` Philip Munksgaard
2021-07-20 16:49 ` Ricardo Wurmus
2021-07-20 19:41 ` Philip Munksgaard
2021-07-21 21:10 ` Ricardo Wurmus
2021-07-27 21:24 ` John Kehayias [this message]
2021-07-27 21:34 ` Ricardo Wurmus
2021-07-20 22:24 ` Ricardo Wurmus
2021-07-24 13:40 ` Xinglu Chen
2021-07-24 15:00 ` Ricardo Wurmus
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='38M76MJzGQQSzvRBewMNjeNDrD8T1WKZL-PEzGPzrv11Y41mcghcx4sJc9dOE_yz-FyNZ7A517aJkzUxMR2k18bXcbcfQoC-oFPIUwDvExw=@protonmail.com' \
--to=john.kehayias@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=philip@munksgaard.me \
--cc=rekado@elephly.net \
/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).