haskellPackages: update stackage and hackage #262645
Merged
Conversation
This file contains 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
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
maralorn
requested review from
cdepillabout and
sternenseemann
as code owners
haskell.compiler.ghc*Binary: fix globbing
The original change missed that we used to erroneously provide LLVM on aarch64-linux, but not on aarch64-darwin which was later fixed in #246045. Since the change was tested on aarch64-linux prior to this, tls ended up being broken on both aarch64-linux and aarch64-darwin. This commit resolves the situation by introducing a helper function to achieve the effect of passing -fllvm while ensuring LLVM is provided. Resolves #260013.
Merged
|
I assume it's OK for me to cancel non-current builds in the corresponding Hydra jobset, e.g. now it was several thousand. |
ofborg
bot
added
8.has: clean-up
8.has: package (new)
ofborg
bot
added
11.by: package-maintainer
This is verified using testers.hasPkgConfigModules which leads to a slight refactor of the expression.
This is verified using testers.hasPkgConfigModules which leads to a slight refactor of the expression.
This is verified using testers.hasPkgConfigModules which leads to a slight refactor of the expression.
This is verified using testers.hasPkgConfigModules which leads to a slight refactor of the expression.
…skell unleash-client-haskell: Unbreak and add maintainer
|
I think the monad-bayes situation is the only thing which needs fixing. This PR has been open quite a while. I don’t think waiting for the upstream fix to be merged and then bumping hackage is a good option, because the branch is otherwise ready to merge. Let’s either apply the patch or disable the checks now and rip them out in the next iteration. |
|
Fine with me if a link to the upstream fix is mentioned: tweag/monad-bayes#326 |
13 tasks
haskellPackages.servant-JuicyPixels: unbreak
|
Applying the monad-bayes patch isn't enough because the files are still missing from the Hackage tarball, so I've disabled the tests. |
This is a manual merge of the PR #265678 since it has a merge conflict
I didn't update our My guess is that the underlying COIN-OR/Clp C++ library was updated fixing the problem? (Gotta love when QuickCheck in Haskell is able to find problems in the underlying C/C++ libraries 😄 ) |
This commit has been generated by maintainers/scripts/haskell/mark-broken.sh based on *evaluation [1801560](https://hydra.nixos.org/eval/1801560) of nixpkgs commit [f10a9c9](https://github.com/NixOS/nixpkgs/commits/f10a9c90947faa4a399e6c98c9fa0ee5c4ae51c5) as of 2023-11-10 04:13 UTC* from the haskell-updates jobset on hydra under https://hydra.nixos.org/jobset/nixpkgs/haskell-updates
taskell depends on an old version of brick that no longer compiles
vcunat
referenced
this pull request
Nov 11, 2023
…+abi issue ...into staging-next We have lots of binaries in cache.nixos.org for this combination already.
|
On Thu, 9 Nov 2023, Dennis Gosnell wrote:
@thielema
I have released a work-around in the Haskell bindings to Hackage. The tests of
coinor-clp should work, again.
I didn't update our haskellPackages.coinor-clp version in this PR (and it doesn't look like there
was a commit fixing it), but it is now compiling correctly.
My guess is that the underlying COIN-OR/Clp C++ library was updated fixing the problem?
They have fixed something, but I do not know whether they already released
the fix.
(Gotta love when QuickCheck in Haskell is able to find problems in the
underlying C/C++ libraries :-))
I have actually also found bugs in OpenBLAS this way.
Since QuickCheck tests with random inputs, tests may fail or succeed
randomly. Since the test failure showed up only after several runs at
Hydra, I think the failure conditions are not met too often. Thus my
current guess is, that neither my Haskell work-around nor the COIN/OR fix
is used but simply the failure conditions are not triggered by accident.
|
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 #259060. Come to #haskell:nixos.org if you have any questions.