!RbXGJhHMsnQcNIDFWN:nixos.org

Haskell in Nixpkgs/NixOS

705 Members
For discussions and questions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs | Current Docs: https://haskell4nix.readthedocs.io/142 Servers

Load older messages

SenderMessageTime
14 Dec 2025
@mangoiv.:matrix.orgMangoIVwhich combination of things do I have to use currently to not get the segfault? 13:45:44
@maralorn:maralorn.demaralorn 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.:matrix.orgMangoIVthanks for the help! <3 14:08:57
@maralorn:maralorn.demaralornRelated: https://github.com/NixOS/nixpkgs/pull/47075815:19:22
@tillerino:matrix.orgTillerino joined the room.18:25:55
16 Dec 2025
@not-jack:matrix.org@not-jack:matrix.org left the room.22:01:57
@josh:quadrivium.ukdutchie joined the room.22:35:00
@josh:quadrivium.ukdutchie

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
@sternenseemann:systemli.orgsternilooks link a mismatch between database and whatever it is checking against08:29:32
@sternenseemann:systemli.orgsterniquestion where is the db coming from08:29:53
@sternenseemann:systemli.orgsterniah 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.008:34:57
@sternenseemann:systemli.orgsternior disable the test suite of course08:35:32
@josh:quadrivium.ukdutchieit'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
@josh:quadrivium.ukdutchienot sure how rigorously the policy is to stick to the Stackage set08:39:35
@sternenseemann:systemli.orgsterniwe don’t enforce stackage constraints for non default package sets since it isn’t possible really anyways08:41:43
@sternenseemann:systemli.orgsterni it’s questionable whether it should be constrained so rigorously anyways in stackage 08:42:13
@sternenseemann:systemli.orgsterniunicode data db updates shouldn’t really break a well designed program?!08:42:37
@ncfavier:matrix.orgncfavierIs 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
@alex:tunstall.xyzAlex I recall it being possible but difficult to override boot packages.
Was it maralorn who knew how to do it? 		14:21:55
@maralorn:maralorn.demaralorn ncfavier: I don’t remember exactly. It is possible in my memory, but it is always finicky and I would need to read the generic-builder.nix code to figure it out again. 14:42:54
@sellout:matrix.orgselloutI am fighting with this again after supposedly solving it just recently. Trying recover what I did last time (or if I was just mistaken then).15:22:02
@sellout:matrix.orgsellout I thought I had just put Cabal = hfinal.Cabal_3_10_3_0 and same for Cabal-syntax in an overlay, then set it in custom-setup in the Cabal file … but cabal2nix doesn’t care about the custom-setup, so there must have been a third piece. 15:25:02
@sellout:matrix.orgsellout Actually, I think this is right – the issue I was just running into was because I set a flag in configureFlags rather than passing it to callCabal2NixWithOptions (which only mattered because there are build-depends conditionalized by the flag). 17:53:14
@lenny:flipdot.orgLenny.

heyo, a dependency I use got marked broken in 25.11 and is still broken on master.
It looks like there is a fix out here https://github.com/dustin/mqtt-hs/commit/211d5742df9295f75f04ad58a51e6c42f1320515

Do the packages from hackage get updated automatically, or should I open a PR that does something similar to https://github.com/NixOS/nixpkgs/pull/470484/files?

19:04:31
@ncfavier:matrix.orgncfavierOh well, I suppose the package should be fixed to work with recent versions anyway.19:05:42
@lenny:flipdot.orgLenny. *

heyo, a dependency I use got marked broken in 25.11 and is still broken on nixpkgs master.
It looks like there is a fix out here https://github.com/dustin/mqtt-hs/commit/211d5742df9295f75f04ad58a51e6c42f1320515

Do the packages from hackage get updated automatically, or should I open a PR that does something similar to https://github.com/NixOS/nixpkgs/pull/470484/files?

19:06:48
@maralorn:maralorn.demaralornOn master the update will happen automatically eventually.19:08:40
@maralorn:maralorn.demaralornIf you want this fixed on 25.11 manual intervention is required.19:09:00
@lenny:flipdot.orgLenny.I think master/unstable is fine for now! How long that usually take? (the fixed release was uploaded to hackage on 24th of oct) Is there a job I can trigger/watch?19:12:15
@lenny:flipdot.orgLenny. * 19:12:21

Show newer messages

Back to Room ListRoom Version: 6