all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars-Dominik Braun <lars@6xq.net>
To: 50843@debbugs.gnu.org
Cc: john.kehayias@protonmail.com, public@yoctocell.xyz,
	rekado@elephly.net, philip@munksgaard.me
Subject: [bug#50843] [PATCHES] Stackage update to 18.10.
Date: Mon, 27 Sep 2021 13:14:00 +0200	[thread overview]
Message-ID: <YVGneDu8dDQORdvM@noor.fritz.box> (raw)

Hi everyone,

I just pushed to the wip-haskell branch (it’s based on master),
which now contains various changes to haskell-build-system as well
as an update to Stackage 18.10 or the latest Hackage package version
where applicable. CI is currently building the changes[1], but from
local building I know all but three packages using haskell-build-system
build. These are ngless, cabal-install and idris. I need your help to
fix them!  There are also packages that cannot be updated via `guix
refresh` currently. They have been left mostly untouched.

I was also thinking about unconditionally adding
--allow-newer/--allow-older to haskell-build-system, so patching
.cabal-files is not necessary any more. Thoughs?

Let’s use this issue to track/review the changes and provide feedback
on them.

Thank you very much,
Lars

[1] https://ci.guix.gnu.org/eval/23961





             reply	other threads:[~2021-09-27 11:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-27 11:14 Lars-Dominik Braun [this message]
2021-09-27 18:31 ` [bug#50843] [PATCHES] Stackage update to 18.10 John Kehayias via Guix-patches via
2021-09-29 12:02   ` Lars-Dominik Braun
2021-10-01 17:24 ` Xinglu Chen
2021-10-02  9:45   ` Lars-Dominik Braun
2021-10-03 11:35     ` Xinglu Chen
2021-10-04  7:27 ` zimoun
2021-10-08  7:28 ` bug#50843: " Lars-Dominik Braun
2021-10-08 13:53   ` [bug#50843] " Xinglu Chen
2021-10-08 14:23     ` John Kehayias via Guix-patches via
     [not found] ` <handler.50843.D50843.163367810626298.notifdone@debbugs.gnu.org>
2021-10-08 22:47   ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YVGneDu8dDQORdvM@noor.fritz.box \
    --to=lars@6xq.net \
    --cc=50843@debbugs.gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=philip@munksgaard.me \
    --cc=public@yoctocell.xyz \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.