haskellPackages: update stackage and hackage#351154
Merged
sternenseemann merged 40 commits intomasterfrom Nov 7, 2024
Merged
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
I do not know why we are ignoring Stackage for this package. fe7d494#commitcomment-148356941
This reverts commit accf933 with some additional modifications.
Fails to compile due to a newly exposed type in deepseq 1.5.10: <typeable/generic-arbitrary#18>.
- crypton is maintained, contrary to cryptonite - since the Hackage scrypt package uses SSE2, we can't build it on non-x86 platforms (non x86_64 even probably). The best option is to disable the Scrypt module. To prevent cabal from pulling in scrypt in spite of that, we need to patch build-depends to respect the flag.
Member
Author
|
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.
This was forgotten when the mailctl attribute was removed.
twain 2.2.0.0 means that we can finally stop depending on out of date versions of http2 and warp.
Member
Author
|
@maralorn From what I can tell all important regressions have been fixed (mergeable and maintained succeed locally), but you should probably have another look before merging. The |
This commit has been generated by maintainers/scripts/haskell/mark-broken.sh based on *evaluation [1809809](https://hydra.nixos.org/eval/1809809) of nixpkgs commit [84527c8](https://github.com/NixOS/nixpkgs/commits/84527c8ca39ea9a3186b33390ca312e5eb9c2db3) as of 2024-11-06 13:00 UTC* from the haskell-updates jobset on hydra under https://hydra.nixos.org/jobset/nixpkgs/haskell-updates
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 #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 tomasterand finalize this iteration.