Skip to content

fix unix dependency correctly#10677

Merged
mergify[bot] merged 1 commit intohaskell:masterfrom
geekosaur:unix-i386-fix-2
Dec 26, 2024
Merged

fix unix dependency correctly#10677
mergify[bot] merged 1 commit intohaskell:masterfrom
geekosaur:unix-i386-fix-2

Conversation

@geekosaur
Copy link
Collaborator

Patching cabal.release.project still allows the buggy unix release to be installed via Hackage.

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:

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

@geekosaur
Copy link
Collaborator Author

Technically this should have a changelog, but practically that's already been covered.

@geekosaur
Copy link
Collaborator Author

The delay here is I need to regenerate the bootstrap JSONs. About to push them.
NTS: cabal-bootstrap-gen still doesn't support XDG paths, and keeps choking on the anchor I dropped to prevent things from using the old path.

@geekosaur geekosaur added merge me Tell Mergify Bot to merge and removed attention: needs-review labels Dec 26, 2024
@mergify mergify bot added merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days ready and waiting Mergify is waiting out the cooldown period labels Dec 26, 2024
Patching `cabal.release.project` still allows the buggy `unix`
release to be installed via Hackage.
@mergify mergify bot merged commit 4b2e5f0 into haskell:master Dec 26, 2024
51 checks passed
@geekosaur
Copy link
Collaborator Author

@mergify backport 3.14

@mergify
Copy link
Contributor

mergify bot commented Dec 26, 2024

backport 3.14

✅ Backports have been created

Details

@geekosaur
Copy link
Collaborator Author

@mergify backport 3.14.1.1

@mergify
Copy link
Contributor

mergify bot commented Dec 26, 2024

backport 3.14.1.1

✅ Backports have been created

Details

mergify bot added a commit that referenced this pull request Dec 26, 2024
mergify bot added a commit that referenced this pull request Dec 27, 2024
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).
@geekosaur
Copy link
Collaborator Author

@9999years reports that this doesn't work with 9.10.1 and Nix (which pins dependencies its own way).

@geekosaur
Copy link
Collaborator Author

And it looks like that is a Nixpkgs issue: the bug has existed for 13-14 years, so our bound is correct and their pin must be moved.

@geekosaur geekosaur deleted the unix-i386-fix-2 branch January 31, 2025 23:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge priority: high 🔥 ready and waiting Mergify is waiting out the cooldown period

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants