haskellPackages: stackage LTS 24.16 -> LTS 24.19#460624
haskellPackages: stackage LTS 24.16 -> LTS 24.19#460624wolfgangwalther merged 51 commits intostagingfrom
Conversation
(cherry picked from commit 02b355a)
I've decided to wait on upstream feedback on Tritlo/duckdb-haskell#2 before trying to get it to build again. (cherry picked from commit 3c9a1a3)
This dependency is only needed for the "plugin-tutorial" executable. This is only built with GHC 9.6 and 9.8, but the expression is created with GHC 9.10. Thus add the missing dependency. It would be better to just disable that tutorial, but I didn't find a quick way of doing that - toggling the related flag did not work. This only fixed the build for GHC 9.6 for me, GHC 9.8 failed with a different error right after. (cherry picked from commit a36931c)
It was complaining about different versions of some regex dependency in the closure, the differing one introduced by hls-plugin-api. GHC 9.6 didn't fail that way, but I figured such a change can't hurt either, for consistency. (cherry picked from commit 7f8ab22)
all-cabal-hashes: 2025-10-22T21:20:29Z -> 2025-11-11T08:13:55Z (generated by maintainers/scripts/haskell/update-package-set.sh) haskellPackages.cabal2nix-unstable: 2025-10-31 -> 2025-11-11 This eliminates the need for 2f1f72d.
nixpkgs-ci
bot
added
the
2.status: merge conflict
nixpkgs-ci
bot
added
10.rebuild-linux: 501+
By default text-icu sets homebrew=true. This can cause a nix build of text-icu to accidentally link the homebrew icu. It can also cause "doesn't work on my machine" issues when an old homebrew version with icu is installed on a mac and is accidentally picked up.
nixpkgs-ci
bot
added
10.rebuild-darwin: 5001+
|
@wolfgangwalther Maybe we should merge the -fexternal-interpreter stuff, too? Edit: I see you're considering it already. I think we can go ahead when you feel okay with it and iterate on it. The PR has become impossible to work with due to the very long history and many force pushes. Ideally, we bump pkgsStatic to 9.10 since that seems to be possible. The problem with going newer is that less stuff will work in general. In my experience older package set have more working packages than newer than default package sets. |
|
I'd like to go ahead with the external interpreter PR within my two-week cycle, yes. Before we merge it in here right now, we should consider whether we'd like to still backport this iteration to staging-25.11 or not. I think it could be a consideration only right now, even if we don't do it usually, because 25.11 is only in beta and the branches have not diverged much, yet. I'd only do it if the current rebuild doesn't give us any other regressions, though. Even if we don't backport it, maybe we should still wait for the rebuild to finish. If that gives us a haskell-updates branch that is mostly mergeable right now, we should do that first and then merge the external interpreter immediately afterwards to start the next round. |
|
Sounds good, merging on the weekend seems realistic. Backporting the external interpreter things should be permissible since it does not break anything (we could also make it off by default), even after release if I'm not missing anything. But we should be sure at the point of backporting that it's the “final” API we are happy with. |
|
text-icu failure is already known: haskell/text-icu#103 |
Also seems to be flaky, so re-running should do it. Not blocking on it. |
This commit has been generated by maintainers/scripts/haskell/mark-broken.sh based on *evaluation [1820566](https://hydra.nixos.org/eval/1820566) of nixpkgs commit [62a3860](https://github.com/NixOS/nixpkgs/commits/62a3860c3400eec2f9d236fbd6590e04102b15b2) as of 2025-11-29 12:05 UTC* from the haskell-updates jobset on hydra under https://hydra.nixos.org/jobset/nixpkgs/haskell-updates
| - zoovisitor | ||
| - zuramaru | ||
| - zwirn | ||
| - _4Blocks |
There was a problem hiding this comment.
This doesn't cause issues?!
There was a problem hiding this comment.
Nope, did not. I think broken.yaml and transitive-broken.yaml map to a different data type in cabal2nix, right?
There was a problem hiding this comment.
Ah, I see now. This did cause problems, but it didn't cause hackage2nix to error out. It did however not match the package, so removed the hydraPlatforms = none line we want here. I reversed that manually, will fix the type thing manually for now, too.
The script didn't pick this up correctly, so manually fixing for now.
|
I opened a backport PR for this at #466256. |
5 participants
This Merge
This PR is the regular merge of the
haskell-updatesbranch intostaging.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-updatesPRs 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:
haskell-updates(normally at the beginning of a merge window).haskell-updatesintostagingevery two weeks.mergeablejob is succeeding on hydra.maintainedpackage 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 #452254. Come to #haskell:nixos.org if you have any questions.