!RbXGJhHMsnQcNIDFWN:nixos.org

Haskell in Nixpkgs/NixOS

743 Members
For discussions and questions about Haskell with Nix, cabal2nix and haskellPackages in nixpkgs | Current Docs: https://haskell4nix.readthedocs.io/ | More Nix: #community:nixos.org | More Haskell: #haskell-space:matrix.org148 Servers

Load older messages


SenderMessageTime
29 Mar 2026
@sternenseemann:systemli.orgsterni (he/him)on x86_64-linux10:28:10
@sternenseemann:systemli.orgsterni (he/him)found a GHC 9.12.4 panic -.-12:03:20
@sternenseemann:systemli.orgsterni (he/him)* found a GHC 9.12.4 panic -.- https://gitlab.haskell.org/ghc/ghc/-/issues/2712112:40:58
@alexfmpe:matrix.orgalexfmpeSigh12:45:44
@alexfmpe:matrix.orgalexfmpehttps://gitlab.haskell.org/ghc/ghc/-/issues/27061#note_66691212:49:06
@alexfmpe:matrix.orgalexfmpeThis really needs to hapoen12:49:31
@alexfmpe:matrix.orgalexfmpeWe even have a bunch of cross platforms with one-line level of support 12:50:17
@alexfmpe:matrix.orgalexfmpeHow do we dump all that on ghc hq as a regression test suite or whatever12:50:50
@b:chreekat.netchreekatThis is the kind of thing that needs a gsoc project12:54:30
@alexfmpe:matrix.orgalexfmpeHehehe12:58:19
@alexfmpe:matrix.orgalexfmpeSomewhat related, I wonder if the ghc.nix shell could be massively reduced by being based in the shell for our hadrian derivation or something. 13:02:15
@alexfmpe:matrix.orgalexfmpeNot sure if relevant here but when opening issues on ghc I tend to add a nixpkgs hash and the invocation just in case they can't reproduce it out of the box13:06:10
@ashinnv:matrix.orgM̸̙̜̔̇Ǎ̴͎̙͔G̸̞̈N̸͔͍̝͗͋̾Ő̷͖̼͈̽̚L̷̻͚̓̔I̷̛͔̰̟̔Å̴̩̍ ̷̦̒̇͝M̷̱̠̺̉̎A̵̼̎͗͘Ỹ̸̬̲͂̕H̷̙̖͂Ē̷͉̦̌͒M̶͈̥̽̐ (you don't get my real name) changed their display name from M̸̙̜̔̇Ǎ̴͎̙͔G̸̞̈N̸͔͍̝͗͋̾Ő̷͖̼͈̽̚L̷̻͚̓̔I̷̛͔̰̟̔Å̴̩̍ ̷̦̒̇͝M̷̱̠̺̉̎A̵̼̎͗͘Ỹ̸̬̲͂̕H̷̙̖͂Ē̷͉̦̌͒M̶͈̥̽̐ to M̸̙̜̔̇Ǎ̴͎̙͔G̸̞̈N̸͔͍̝͗͋̾Ő̷͖̼͈̽̚L̷̻͚̓̔I̷̛͔̰̟̔Å̴̩̍ ̷̦̒̇͝M̷̱̠̺̉̎A̵̼̎͗͘Ỹ̸̬̲͂̕H̷̙̖͂Ē̷͉̦̌͒M̶͈̥̽̐ (you don't get my real name).13:22:43
@sternenseemann:systemli.orgsterni (he/him) alexfmpe: well I did test it ahead of time, but I only tried a couple of packages that were affected by the subword division issue and cabal2nix iirc 18:19:53
30 Mar 2026
@zumuzumu:matrix.orgBig man joined the room.04:41:17
@mangoiv.:matrix.orgMangoIV It can be. It just grew organically over many years. 08:48:09
@janus.troelsen:matrix.orgJanus I am wondering whether the plan is for nixpkgs to patch packages using memory to use ram instead? That would be interesting to see, as it could provide a relatively painless experience compared to all the builds currently failing (when mixing these) using the cabal solver... 08:49:21
@maralorn:maralorn.demaralorn Janus: We are generally very conservative about doing switches like that. 10:32:49
@maralorn:maralorn.demaralorn sterni: I am sorry, that I can’t be of more help right now. But it’s simply too much. I still intend to ramp up my engagement when I got everything else under control. 10:34:03
@maralorn:maralorn.demaralornI was wondering about the nightly switch you suggested. If we did one know could we push it through until branch-off?10:34:37
@maralorn:maralorn.demaralorn* I was wondering about the nightly switch you suggested. If we did one now could we push it through until branch-off?10:34:54
@maralorn:maralorn.demaralornSeems a bit tight to me. So maybe we should wait and do it immediately after?10:35:27
@janus.troelsen:matrix.orgJanusAww that's too bad! Because I think that Vincent is being deliberately difficult to work with. I do understand the Hackage position, but I also know nixpkgs doesn't have any issue with adding downstream jailbreaks, which, in my mind, is a related tradeoff.10:59:55
@maralorn:maralorn.demaralornMaybe we can be more flexible with memory/ram, with crypton/cryptonite our stance was that security critical decisions have to be made by upstream.11:02:53
@sternenseemann:systemli.orgsterni (he/him)we did on occasion patch stuff, but IIRC only when it was clear those patches were on their way to being upstreamed and released.11:03:33
@sternenseemann:systemli.orgsterni (he/him)I don't really see the point in investing time in patching packages that will never be changed upstream since this just means a lot of time down the drain when everyone else will need to get away from those packages anyways11:04:24
@sternenseemann:systemli.orgsterni (he/him)So basically I'd say we should just decide this on a case by case basis.11:04:40
@sternenseemann:systemli.orgsterni (he/him) maralorn: given the GHC 9.12.4 panic we encountered now, I also am not confident 11:06:17
@sternenseemann:systemli.orgsterni (he/him)but maybe we should start the migration and see how it works out until the cut off point though I think we'd need to be finished by the end of April more or less since e.g. the pandoc upgrade seems a little risky to do so late11:08:52
@sternenseemann:systemli.orgsterni (he/him)We could look into upgrading some packages (pandoc, hledger, …?) before branch off so we are not horribly outdated on that front at least11:09:52

Show newer messages


Back to Room ListRoom Version: 6