From: Timothy Sample <samplet@ngyro.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: merge wip-haskell?
Date: Mon, 17 Aug 2020 11:22:27 -0400 [thread overview]
Message-ID: <875z9hguvg.fsf@ngyro.com> (raw)
In-Reply-To: 87v9hkqq1u.fsf@elephly.net
Hey Ricardo,
Ricardo Wurmus <rekado@elephly.net> writes:
> Ricardo Wurmus <rekado@elephly.net> writes:
>
>> Timothy Sample <samplet@ngyro.com> writes:
>>
>>> I just pushed “wip-haskell-updates-2” which integrates my work from
>>> <https://issues.guix.gnu.org/39309>. I left the original branch intact
>>> to make it easy to compare.
>>
>> I rebased this on top of “master” and pushed it as “wip-haskell”. I
>> updated my changes to pandoc and pandoc-citeproc so that the statically
>> linked variants are now separate packages.
>>
>> The evaluations on ci.guix.gnu.org failed due to a few minor bugs in the
>> extra-directories code (missing “match” case for inputs with declared
>> outputs, and a missing list wrapper in one package). I fixed up that
>> commit [...].
Sorry for the mistakes. Thanks for fixing them up. :)
> I just merged “wip-haskell” into “master” (after merging “master” into
> “wip-haskell”).
Fantastic!
I noticed a few surprising failures like Agda and git-annex. With
git-annex, I had to create a fake "static" output to appease the daemon
(cf. e13fefbcffa50144d9301d67b61928ac3c964fb3). It’s a little funny,
but I suppose can’t be helped until there is progress on
<https://issues.guix.gnu.org/41569>.
Is it true that now that “wip-haskell” is removed from Cuirass there’s
no longer any way to see the build failures? I can’t find them, but my
Cuirass skills are rather mediocre. :) Either way, I have fast-enough
machine I can use to track down some of the other failures. Maybe I
will try and do it along with the Stackage update.
-- Tim
next prev parent reply other threads:[~2020-08-17 15:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 8:13 merge wip-haskell? Ricardo Wurmus
2020-08-06 13:45 ` John Soo
2020-08-07 17:46 ` Timothy Sample
2020-08-07 19:53 ` Ricardo Wurmus
2020-08-09 4:29 ` Timothy Sample
2020-08-12 12:21 ` Ricardo Wurmus
2020-08-13 15:37 ` Ricardo Wurmus
2020-08-15 8:19 ` Ricardo Wurmus
2020-08-17 15:22 ` Timothy Sample [this message]
2020-08-24 15:38 ` Ludovic Courtès
2020-08-07 15:03 ` Jakub Kądziołka
2020-08-07 15:12 ` John Soo
2020-08-07 15:46 ` Jakub Kądziołka
2020-08-07 15:59 ` Ricardo Wurmus
2020-08-07 16:08 ` John Soo
2020-08-24 15:44 ` Ludovic Courtès
2020-08-24 17:54 ` Ricardo Wurmus
2020-08-28 13:53 ` Ludovic Courtès
2020-08-28 14:05 ` John Soo
2020-08-28 17:29 ` Timothy Sample
2020-08-29 15:34 ` Timothy Sample
2020-08-29 15:54 ` John Soo
2020-08-07 16:27 ` Ricardo Wurmus
2020-08-07 16:55 ` Jakub Kądziołka
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=875z9hguvg.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
--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).