[bug#71427] Request for merging "haskell-team" branch

[Liliana Marie Prikler]

Am Mittwoch, dem 12.06.2024 um 21:53 +0200 schrieb Lars-Dominik Braun:
> 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.
I think mentioning each file and package would be good enough™.
If parts can be split off into more commits, that's fine, but
everything that needs to be bumped along with the variable, needs to be
bumped.

> > 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…
Is there any other way to get pandoc-3.2 then?  I have a package that
appears to depend on that.
Perhaps we could do -next variants, but there'd still be a lot of them.

> I’m also pushing a fix for ghc-aeson, which should fix most other
> packages as well.
Neat.

Cheers