| 12 Dec 2025 |
 emily | right | 17:00:41 |
| emily | I'm just assuming you didn't use to get this | 17:00:47 |
 alexfmpe | not sure, first time I try to build this particular project | 17:01:09 |
| alexfmpe | hmm hang on | 17:01:15 |
| alexfmpe | I think changing this to crypto.3 fixed it | 17:01:53 |
| alexfmpe | can't confirm right now because I did a clean afterwards and now github is dying on me or something | 17:02:11 |
| emily | I feel like it should work with just crypto and we're holding it wrong or something. but maybe not. | 17:04:00 |
| emily | have you tried 25.05, 24.11? | 17:04:08 |
| alexfmpe | I'll see if I can get away with this stupid workaround just to complete the task I was aiming for, then circle back to investigate this properly | 17:10:17 |
| emily | fair enough | 17:11:27 |
| 13 Dec 2025 |
|  NixOS Moderation Bot unbanned  @mightyiam:matrix.org. | 05:59:25 |
|  Ethan changed their display name from Ethan Bodzioney to Ethan. | 22:13:39 |
| 14 Dec 2025 |
 MangoIV | which combination of things do I have to use currently to not get the segfault? | 13:45:44 |
 maralorn | MangoIV: You need to avoid hls 9.10 with hlint plugin. So either you switch ghc version or disable hlint either via nix or in your editor config. | 14:02:18 |
| MangoIV | thanks for the help! <3 | 14:08:57 |
| maralorn | Related: https://github.com/NixOS/nixpkgs/pull/470758 | 15:19:22 |
|  Tillerino joined the room. | 18:25:55 |
| 16 Dec 2025 |
|  @not-jack:matrix.org left the room. | 22:01:57 |
|  dutchie joined the room. | 22:35:00 |
| dutchie | Hi, I'm having an issue where haskell.packages.ghc912.unicode-data doesn't build in nixpkgs-unstable or haskell-updates. It looks like it's using the wrong Unicode version at some point:
Test suite test: RUNNING...
Unicode.Char
Unicode blocks
Characters not in any block are unassigned [✔]
Examples [✔]
Characters are in the definition of their corresponding block [✔]
Characters in a block definition have the corresponding block [✔]
Unicode general categories
[WARNING] Cannot test '\2199': incompatible Unicode version (unassigned char). Expected 15.1.0, but got: 16.0.0
[WARNING] Cannot test '\6990': incompatible Unicode version (unassigned char). Expected 15.1.0, but got: 16.0.0
[WARNING] Cannot test '\6991': incompatible Unicode version (unassigned char). Expected 15.1.0, but got: 16.0.0
[WARNING] Cannot test '\7039': incompatible Unicode version (unassigned char). Expected 15.1.0, but got: 16.0.0
[WARNING] Cannot test '\7305': incompatible Unicode version (unassigned char). Expected 15.1.0, but got: 16.0.0
[WARNING] Cannot test '\7306': incompatible Unicode version (unassigned char). Expected 15.1.0, but got: 16.0.0
# snip a bazillion similar warnings
[WARNING] Cannot test '\124409': incompatible Unicode version (unassigned char). Expected 15.1.0, but got: 16.0.0
[WARNING] Cannot test '\124410': incompatible Unicode version (unassigned char). Expected 15.1.0, but got: 16.0.0
Compare to base [✔]
isNumber implies a numeric value [✔]
Failures:
test/Unicode/CharSpec.hs:206:21:
1) Unicode.Char.Case toUpper
predicate failed on: '\411'
To rerun use: --match "/Unicode.Char/Case/toUpper/" --seed 909632297
test/Unicode/CharSpec.hs:227:21:
2) Unicode.Char.Case toTitle
predicate failed on: '\411'
To rerun use: --match "/Unicode.Char/Case/toTitle/" --seed 909632297
Randomized with seed 909632297
Finished in 0.6187 seconds
41 examples, 2 failures
Test suite test: FAIL
Test suite logged to: dist/test/unicode-data-0.6.0-test.log
0 of 1 test suites (0 of 1 test cases) passed.
I can't see any upstream bugs but not really sure what's going on
| 22:37:31 |
| 17 Dec 2025 |
 sterni | looks link a mismatch between database and whatever it is checking against | 08:29:32 |
| sterni | question where is the db coming from | 08:29:53 |
| sterni | ah it checks against base so you either need to downgrade GHC so it doesn’t know about those chars as well or upgrade unicode-data, current version is 0.8.0 which supports Unicode 17.0.0 | 08:34:57 |
| sterni | or disable the test suite of course | 08:35:32 |
| dutchie | it's still 0.6.0 in all the stackage lts versions, should it be upgraded to 0.8.0 in nixpkgs for GHC 9.12 in nixpkgs despite that? | 08:39:15 |
| dutchie | not sure how rigorously the policy is to stick to the Stackage set | 08:39:35 |
| sterni | we don’t enforce stackage constraints for non default package sets since it isn’t possible really anyways | 08:41:43 |
| sterni | it’s questionable whether it should be constrained so rigorously anyways in stackage | 08:42:13 |
| sterni | unicode data db updates shouldn’t really break a well designed program?! | 08:42:37 |
 ncfavier | Is there a way to override the version of Cabal used to build Setup.hs? lhs2tex needs Cabal 3.10, but using the obvious override doesn't work (I suspect because Cabal 3.12 is bundled with GHC and it picks the latest available version). I also found https://github.com/NixOS/nixpkgs/pull/443130 but that doesn't seem to help here. | 13:32:29 |
