haskellPackages: update stackage and hackage

[maralorn]

This Merge

This PR is the regular merge of the haskell-updates branch into master.

This branch is being continually built and tested by hydra at https://hydra.nixos.org/jobset/nixpkgs/haskell-updates. You may be able to find an up-to-date Hydra build report at cdepillabout/nix-haskell-updates-status.

We roughly aim to merge these haskell-updates PRs at least once every two weeks. See the @NixOS/haskell team calendar for who is currently in charge of this branch.

haskellPackages Workflow Summary

Our workflow is currently described in pkgs/development/haskell-modules/HACKING.md.

The short version is this:

• We regularly update the Stackage and Hackage pins on haskell-updates (normally at the beginning of a merge window).
• The community fixes builds of Haskell packages on that branch.
• We aim at at least one merge of haskell-updates into master every two weeks.
• We only do the merge if the mergeable job is succeeding on hydra.
• If a maintained package is still broken at the time of merge, we will only merge if the maintainer has been pinged 7 days in advance. (If you care about a Haskell package, become a maintainer!)

More information about Haskell packages in nixpkgs can be found in the nixpkgs manual.

---

This is the follow-up to #226832. Come to #haskell:nixos.org if you have any questions.

[maralorn]

@Gabriella439 Currently we pin dhall to 1.41.2 from stackage, but the newest dhall-nix release requires dhall 1.42.
The simplest solution is to manually pin dhall-nix to the previous version, would that be okay with you?

Edit: Same problem holds for dhall-nixpkgs.

[thielema]

On Sat, 22 Apr 2023, maralorn wrote: We can apply a patch (e.g. one disabling the deprecated example), especially if we can fetch them from remotes. We are not huge fans of checking in patches into nixpkgs. You can look for examples using fetchpatch in configuration-common.nix.

I don't know whether patches are the right way to go. I succeeded to build the examples with GHC-9.4.5 using certain Git commits of imported packages. In my cabal.project file I have added ~~~~ source-repository-package type: git location: https://gitlab.com/rd--/hps tag: 7cc3d7b981a71967619dfef24e3f525e58530cf9 source-repository-package type: git location: https://gitlab.com/rd--/hcg-minus tag: e5254e43a5e76ebffbb238e4b7e43114a5be695d source-repository-package type: git location: https://gitlab.com/rd--/hmt-base tag: d8520843ee3de93b4a8b8bb539116d55360b6f58 ~~~~ Then I need some patches in my med-module package. I can release them to Hackage. However, the author of hps, hcg-minus, hmt-base says, that those packages are deprecated and thus he hesitates to release them to Hackage. Is it possible to define a Nix-Haskell-package with sources pulled from a git commit?

I don’t know how much you care about those examples. I would probably suggest just disabling them, but I’ll leave it up to you.

My idea was to provide the users with prebuilt executables that are hard to build by themselves.

[sternenseemann]

I think it is less of a nightmare going forward if we not manually try to keep deprecated packages working unless we absolutely have to. Especially if they are only required by example binaries. I'm personally not convinced building examples is necessarily worth it in nixpkgs in the first place, they should at least use separate bin outputs to decrease download sizes for those that only depend on the library — Haskell binaries are quite big due to static linking.

[maralorn]

I also think continuing support for three deprecated libraries in nixpkgs is unwise.

[maralorn]

@thielema I would like to merge this PR now. I assume the med-module issue is not very urgent. I will, for now, disable the examples so that the package at least builds. Feel free open a PR fixing the examples somehow whenever you feel like it.