From: Lars-Dominik Braun <lars@6xq.net>
To: Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: 71427@debbugs.gnu.org
Subject: [bug#71427] Request for merging "haskell-team" branch
Date: Wed, 12 Jun 2024 21:53:36 +0200 [thread overview]
Message-ID: <Zmn8wAzB17mD0ajN@noor.fritz.box> (raw)
In-Reply-To: <a548015e6d6d93a1d34f097cf47ec24dab397ea9.camel@gmail.com>
Hi,
> > and Stackage was upgraded to the corresponding version 20.26.
> That commit really lacks a readable message, though.
I know it does not conform to Guix standards. What do you suggest? One
commit per package is not feasible.
> Further, I think our work is far from done; just attempting to update
> pandoc has me yak-shaving the depths of haskell-*.scm with no end in
> sight. If that's our only haskell application, we're in luck, but I
> fear there might be more.
Is Haskell-world, you can’t just update pandoc. Pandoc is part of the
curated set of Stackage packages and those *must not* be updated,
unless there is a new Stackage release which matches our GHC compiler
(there is not). Otherwise, well, dependency hell…
I’m also pushing a fix for ghc-aeson, which should fix most other
packages as well.
Lars
next prev parent reply other threads:[~2024-06-12 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 6:36 [bug#71427] Request for merging "haskell-team" branch Lars-Dominik Braun
2024-06-12 17:12 ` Liliana Marie Prikler
2024-06-12 19:53 ` Lars-Dominik Braun [this message]
2024-06-13 4:23 ` Liliana Marie Prikler
2024-06-14 6:24 ` Lars-Dominik Braun
2024-06-14 16:54 ` Liliana Marie Prikler
2024-06-29 6:58 ` bug#71427: " Lars-Dominik Braun
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=Zmn8wAzB17mD0ajN@noor.fritz.box \
--to=lars@6xq.net \
--cc=71427@debbugs.gnu.org \
--cc=liliana.prikler@gmail.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).