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

[Lars-Dominik Braun]

Hi,

> 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.

I mean, if a 250-line-ish long, auto-generated commit message is
okay…?[1] It’s usefulness is disputable, but I can’t do this by
hand for ~230 packages.

> 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.

You could try a fresh import with `guix import hackage -r pandoc`, but
you’ll probably run into issues with packages requiring more recent
GHC-provided packages. Then you can either try to build a newer GHC[2]
or download the entire Hackage database and use a solver to find a
combination of packages that works with our current GHC (i.e. what
Stackage does by hand, afaik).

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

This is done now. Let’s convince everyone else that skipping the merge
queue is fine in this case…

Lars

[1] git show | sed -nre 's#^\+\+\+ b/(.*)#* \1#gp; s/^@@.*\(define-public 
(.*)/(\1): Update./gp' | uniq
[2] https://issues.guix.gnu.org/issue/67921