haskellPackages: update stackage and hackage#231162
Conversation
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
github-actions
bot
added
the
6.topic: haskell
sternenseemann
changed the title
Stackage has been updated to include utility-ht-0.0.17
ofborg
bot
added
8.has: package (new)
|
I'm sorry, due to current situation I cancelled the jobset. I expect it to get back in about two days, with much of work done over one or two days following that. I hope it's not an issue; otherwise we could try to find some other approach. |
|
BTW, I expect that you're aware that no "breaking changes" are allowed in these couple of weeks. |
No problem, there's no real urgency in this iteration and I lack time anyways. I've restarted the aborted jobs now since the queue was pretty empty (<2000 jobs). |
|
Yes, probably. |
|
I cancelled the old builds in favor of the new ones. I assume that's what you'd want, but feel free to override that. |
Additionally, we fix an apparent mistake causing ghc-lib-parser to be used as the ghc-lib attribute.
This commit has been generated by maintainers/scripts/haskell/mark-broken.sh based on *evaluation [1795235](https://hydra.nixos.org/eval/1795235) of nixpkgs commit [7398920](https://github.com/NixOS/nixpkgs/commits/7398920e33f6aef596210f787c276ed6568a7e06) as of 2023-05-19 13:57 UTC* from the haskell-updates jobset on hydra under https://hydra.nixos.org/jobset/nixpkgs/haskell-updates
If we want to push only one branch, we'll have to specify branch and remote explicitly. Pushing to origin doesn't work for everyone, since some of us have a origin remote that can't be pushed to. Using plain `git push` has the problem that it'll try pushing all checked out branchs which fails e.g. if some branches (staging, staging-next, …) are behind their remote counterparts. The solution is to require everyone to configure a per branch pushRemote for haskell-updates which will then be used by merge-and-open-pr.sh.
|
When Hydra gets a long a bit more, I'd merge this PR before branch-off (likely later today), as there are no breaking changes present. This will cause a full rebuild of |
|
Yes, the last |
ofborg
bot
added
the
8.has: clean-up
2 participants
This Merge
This PR is the regular merge of the
haskell-updatesbranch intomaster.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-updatesintomasterevery 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 #228965. Come to #haskell:nixos.org if you have any questions.