Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

haskellPackages: update stackage and hackage #166460

Merged
merged 17 commits into from
Apr 3, 2022
Merged

haskellPackages: update stackage and hackage #166460

merged 17 commits into from
Apr 3, 2022

Conversation

maralorn
Copy link
Member

@maralorn maralorn commented Mar 30, 2022

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!)

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

This commit has been generated by maintainers/scripts/haskell/update-stackage.sh
This commit has been generated by maintainers/scripts/haskell/update-hackage.sh
This commit has been generated by maintainers/scripts/haskell/regenerate-hackage-packages.sh
github-actions bot and others added 2 commits March 31, 2022 00:10
Fixes an evaluation error as the versioned attr is missing now.
sternenseemann and others added 3 commits March 31, 2022 13:03
1.0.3.0 hasn't introduced support for aeson 2.0
0.10.1 has propagated into hackage-packages.nix
Applies on next regenerate-hackage-packages.sh.
@roberth
Copy link
Member

roberth commented Mar 31, 2022

Maybe #166571 and #166548 could be merged simultaneously to save a bit on mass-rebuilds.

@sternenseemann
Copy link
Member

Maybe #166571 and #166548 could be merged simultaneously to save a bit on mass-rebuilds.

Yeah, I was thinking that, too, maybe we'll even be able to combine this with the upcoming zlib-related stdenv rebuild, so we'd get 3 changes done in one rebuild.

github-actions bot and others added 2 commits April 1, 2022 00:12
When cross compiling the pkg-config binary is prefixed and cabal
needs to be made aware of this.

Note: the `--with-pkg-config` flag can't be added unconditionally
because if the package doesn't need pkg-config (thus pkg-config
is not in the PATH) cabal consider this a hard failure.
@roberth
Copy link
Member

roberth commented Apr 1, 2022

so we'd get 3 changes done in one rebuild.

Not sure if this is practical without merging into staging-next. Otherwise, you'd have to inhibit builds on master, which seems tricky and requires a timely merge of haskell-updates. Maybe we'd better keep it simple, but it's your call, as you have experience running haskell-updates.

@sternenseemann
Copy link
Member

Well eventually the zlib change is going to land in master which is when we'll have to do a set rebuild in haskell-updates (unless we want to cause the rebuild on master), so we could do it a that point. Another option could of course be merging staging-next into haskell-updates and then waiting for that to be merged — never tried that before and not sure if it's wise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants