| 19 Aug 2025 |
 bglgwyng | Does haskell.nix internally generate plan.json and use it? Or it just uses pre-built package sets. | 06:18:16 |
 maralorn | bglgwyng: haskell.nix uses plan.json (at least that’s one of the available modes) | 06:53:04 |
 Artem | FTW: I made this typo again: liquidhaskell-boot = doJailbreak super.smtlib-backends-tests; and that's why liquidhaskell couldn't find a module in liquidhaskell-boot... | 14:09:50 |
| Artem | * FTR: I made this typo again: liquidhaskell-boot = doJailbreak super.smtlib-backends-tests; and that's why liquidhaskell couldn't find a module in liquidhaskell-boot... | 14:17:52 |
|  @xvwx:matrix.dapp.org.uk left the room. | 14:23:55 |
| Artem | what is the better commit message / PR title for a nixpkgs PR:
haskellPackages.{liquidhaskell, liqquidhaskell-boot, liquid-fixpoint, smtlib-backends-process, smtlib-backends-tests}: unbreak
or
haskellPackages.liquidhaskell and dependencies: unbreak
| 14:28:57 |
| Artem | * what is the better commit message / PR title for a nixpkgs PR:
haskellPackages.{liquidhaskell, liqquidhaskell-boot, liquid-fixpoint, smtlib-backends-process, smtlib-backends-tests}: unbreak
or
haskellPackages.liquidhaskell and dependencies: unbreak
?
| 14:29:02 |
 symphorien | the ci parses commit messages, so if you do one commit per package it will build the right packages | 14:34:20 |
| Artem | ouch, I did one commit for everything! just to double-check: is one commit per package a requirement? | 14:40:19 |
| symphorien | no | 14:42:05 |
 emily | it will parse {a,b} in commit messages too | 14:56:04 |
| Artem | all right, I'll go with the explicit list then | 14:59:09 |
| symphorien | oh cool | 15:16:34 |
 alexfmpe | waaaat | 16:30:59 |
| alexfmpe | where can I find these tidbits | 16:31:14 |
| emily | it's in the ofborg repo docs I think | 16:31:57 |
| alexfmpe | TIL | 16:42:39 |
| alexfmpe | https://github.com/NixOS/ofborg?tab=readme-ov-file#automatic-building | 16:42:40 |
| 20 Aug 2025 |
 Pierre Thierry | I've looked at documentation and source code but I don't see how I can use developPackage and add additional packages to the environment (ideally they would only be added when using a shell). I guess that's done with the modifier attribute? | 18:02:08 |
| Pierre Thierry | (I'd like to add packages like HLS and hlint) | 18:02:32 |
| Artem | how do I get a sense of when the GHC 9.10 bump will be merged into staging? I saw a long list of failures but surely not everything has to be fixed before the merge. I also saw "We only do the merge if the mergeable job is succeeding on hydra" but how do I get a sense of close it is to succeeding? | 19:39:21 |
