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 #351154

Open
wants to merge 23 commits into
base: master
Choose a base branch
from

Conversation

sternenseemann
Copy link
Member

@sternenseemann sternenseemann commented Oct 25, 2024

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

Marked as draft since we need to wait for the last iteration to be merged as part of #348827. After that we can switch the target branch to master and finalize this iteration.

github-actions bot and others added 7 commits October 22, 2024 00:16
This commit has been generated by maintainers/scripts/haskell/update-hackage.sh
This commit has been generated by maintainers/scripts/haskell/update-stackage.sh
This commit has been generated by maintainers/scripts/haskell/regenerate-hackage-packages.sh
I do not know why we are ignoring Stackage for this package.
fe7d494#commitcomment-148356941
This reverts commit accf933 with some
additional modifications.
@sternenseemann
Copy link
Member Author

sternenseemann commented Oct 31, 2024

  • eval errors
  • large-hashable (I'll do that)

These jobs weren't actually generated since we don't add doDistribute to
Cabal-syntax*. It doesn't really matter since the Cabal job always
causes the corresponding Cabal-syntax to be built.
Unfortunately, it won't be possible to build 9.12 nor, in all
likelihood, 9.14 with Cabal 3.12 or 3.14 (which are shipped with GHC 9.8
and 9.10, respectively) due to
<https://gitlab.haskell.org/ghc/ghc/-/commit/145a6477854d4003a07573d5e7ffa0c9a64ae29c>.
Since this has been confirmed by upstream, we'll have to bite the bullet
and adjust our hadrian bootstrapping logic to deal with that.
Fortunately, we at least have gotten a hackage released version of Cabal
3.14, so we don't need to bootstrap from an in tree Cabal version.
For Cabal, using a more recent version of process is practically never
necessary since it has support for a very wide range. The process
override is a relic from when we were testing cabal-install with all GHC
versions. cabal-install(-solvers) needs directory >=1.3.7.0 which in
turn needs a recent version of process to work. Consequently, the used
Cabal version needed to use the same process version or we'd have
inconsistent dependencies when building cabal-install. Since we only
support cabal-install with GHCs that ship new enough versions of both
process and directory out of the box, we can drop these overrides.
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.

1 participant