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 #227288. Come to #haskell:nixos.org if you have any questions.

[thielema]

On Wed, 3 May 2023, maralorn wrote: Builder tries to build fresh release of comfort-glpk-0.0.1 from Hackage, but it cannot find utility-ht-0.0.17. However, it is already released on Hackage: https://hackage.haskell.org/package/utility-ht-0.0.17 There is a utility-ht_0_0_17 attribute. So we need to override the input of comfort-glpk to use that one.

Why is the new version of comfort-glpk used automatically, but not the new version of utility-ht? I like to understand this inconsistency, because it means that for every fix I release to Hackage I have to add a temporary exception to configuration-common.nix.

[thielema]

On Wed, 3 May 2023, maralorn wrote: There is a utility-ht_0_0_17 attribute. So we need to override the input of comfort-glpk to use that one.

Can we simply update utility-ht to version 0.0.17?

[maralorn]

Fair point. The reason is, that utility-ht is in stackage-lts and comfort-glpk is not.
The tooling defaults to prefer the stackage version, if available.

If you want, we can exempt utility-ht from being hold back by stackage. That will only cause problems if any of the packages in stackage is incompatible with a newer utility-ht version.

[sternenseemann]

If you want, we can exempt utility-ht from being hold back by stackage.

No need, Stackage only forbids breaking updates according to PVP. There is actually no way that 0.0.17 is considered breaking, so Stackage will update to it. This is merely a case of unfortunate timing where our bump is after the release, but before the Stackage CI having a chance to verify that the version update is okay. We can probably preempt the bump and sort it out when Stackage catches up.