cabal.release.project: pick newer unix that fixes important bugs on i386 and arm#10664
Merged
mergify[bot] merged 1 commit intomasterfrom Dec 23, 2024
Merged
cabal.release.project: pick newer unix that fixes important bugs on i386 and arm#10664mergify[bot] merged 1 commit intomasterfrom
unix that fixes important bugs on i386 and arm#10664mergify[bot] merged 1 commit intomasterfrom
Conversation
geekosaur
approved these changes
Dec 23, 2024
Kleidukos
approved these changes
Dec 23, 2024
geekosaur
added
merge me
mergify
bot
added
merge delay passed
Collaborator
|
@mergify backport 3.14 |
Contributor
✅ Backports have been createdDetails
|
2 tasks
Collaborator
|
@mergify backport 3.14.1.1 |
Contributor
✅ Backports have been createdDetails
|
2 tasks
mergify bot
added a commit
that referenced
this pull request
Dec 26, 2024
Backport #10664: cabal.release.project: pick newer `unix` that fixes important bugs on i386 and arm
sternenseemann
added a commit
to sternenseemann/nixpkgs
that referenced
this pull request
Jan 16, 2025
Cabal has recently introduced a lower bound for unix so a certain bug fix for 32bit platforms (in combination with a toolchain that sets _FILE_OFFSET_BITS=64) is included: haskell/cabal#10664 haskell/cabal#10677 I don't think it's actually possible to encounter this problem with nixpkgs since we haven't transitioned to 64bit time_t for 32bit platforms unlike Debian. To prevent confusing behavior in edge cases, backport the patch to all GHC versions that lack it and lift the bound on Cabal 3.14 (which is honestly a strange way to “fix” this problem).
sternenseemann
added a commit
to NixOS/nixpkgs
that referenced
this pull request
Jan 16, 2025
Cabal has recently introduced a lower bound for unix so a certain bug fix for 32bit platforms (in combination with a toolchain that sets _FILE_OFFSET_BITS=64) is included: haskell/cabal#10664 haskell/cabal#10677 I don't think it's actually possible to encounter this problem with nixpkgs since we haven't transitioned to 64bit time_t for 32bit platforms unlike Debian. To prevent confusing behavior in edge cases, backport the patch to all GHC versions that lack it and lift the bound on Cabal 3.14 (which is honestly a strange way to “fix” this problem).
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
4 participants
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.
Template B: This PR does not modify behaviour or interface
E.g. the PR only touches documentation or tests, does refactorings, etc.
Include the following checklist in your PR: