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

Merged
merged 33 commits into from
Apr 9, 2024
Merged

haskellPackages: update stackage and hackage #300455

merged 33 commits into from
Apr 9, 2024

Conversation

ncfavier
Copy link
Member

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 #296524. 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
@vcunat
Copy link
Member

vcunat commented Apr 1, 2024

Let me delay these builds for a couple days, until PR #298548 gets merged (hopefully, in a day or two).

@maralorn
Copy link
Member

maralorn commented Apr 7, 2024

Currently only two relevant appearing build errors on the branch:

I’ll look into the eventlog thing, not immediately sure what to do about carp.

We also have an eval error on darwin:

in job ‘haskell.compiler.ghc963Binary.x86_64-darwin’:
error: Failed to evaluate ghc-binary-9.6.3: «broken»: is marked as broken

What’s going on there?

github-actions bot and others added 2 commits April 8, 2024 00:13
The build is broken because the package hasn't been updated for text >= 2 yet
@jluttine
Copy link
Member

jluttine commented Apr 8, 2024

Currently only two relevant appearing build errors on the branch:

* [ ]  [[📱❌]](https://hydra.nixos.org/build/254958066) [[🐧❌]](https://hydra.nixos.org/build/254964054) [carp](https://hydra.nixos.org/eval/1805483?filter=carp) @jluttine

* [ ]  [[📱❌]](https://hydra.nixos.org/build/254945690) [[🐧❌]](https://hydra.nixos.org/build/254969151) [haskellPackages.eventlog2html](https://hydra.nixos.org/eval/1805483?filter=haskellPackages.eventlog2html) @maralorn

I’ll look into the eventlog thing, not immediately sure what to do about carp.

Carp repo seems pretty inactive. I asked if it's still maintained at all: carp-lang/Carp#1462

@maralorn
Copy link
Member

maralorn commented Apr 8, 2024

@jluttine So, would it be okay for you if we marked Carp broken for the time being?

@jluttine jluttine mentioned this pull request Apr 8, 2024
13 tasks
@jluttine
Copy link
Member

jluttine commented Apr 8, 2024

@jluttine So, would it be okay for you if we marked Carp broken for the time being?

Sure! Here's a PR: #302534

@maralorn maralorn merged commit ae67af3 into master Apr 9, 2024
6 of 7 checks passed
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.

9 participants