| 9 Aug 2025 |
 sterni (he/him) | it's mostly meant to fail our CI, but it's hard to implement that | 22:12:42 |
 emily | right | 22:14:00 |
| sterni (he/him) | in my experience bindings etc. are pretty tricky because no one tests these when updating the base package, so I wanted to make it visible for us here at least | 22:14:35 |
| sterni (he/him) | but we should probably revert it | 22:14:49 |
| sterni (he/him) | the problem is also that you can't just update the number on the bump yet because the package wants to link against libLLVM21-git | 22:15:33 |
| sterni (he/him) | at least last I checked | 22:15:40 |
| emily | well, we do build quite a lot of stuff when bumping LLVM | 22:32:12 |
| emily | at least | 22:32:14 |
| emily | so it may be a special case in terms of bindings | 22:32:17 |
| 10 Aug 2025 |
| sterni (he/him) | Haskell bindings get frequently overlooked in my experience | 00:44:17 |
| sterni (he/him) | though we haven't had Haskell LLVM bindings where an up to date version is readily available | 00:44:43 |
| sterni (he/him) | llvm-hs never uploaded anything after 9.0.1 to Hackage and I never bothered to work out how usable the llvm-12 branch was | 00:45:40 |
| sterni (he/him) | now that's all kind of irrelevant | 00:45:46 |
| emily | I mean more "when we bump LLVM people are building full Darwin systems" | 02:00:07 |
| 11 Aug 2025 |
 lambdatheultimatealias | I can see a few of us have fixes in Hackage for Ghc 9.12. Should we be waiting for the next run of the Hackage update script on the haskell-updates branch or running it ourselves and submitting the relevant patch as a PR? Also is there a way of knowing in general whether another pull from Hackage is planned to avoid unnecessary PRs? | 10:49:49 |
| sterni (he/him) | I'll probably do another one, maybe we'll get Stackage LTS 24.4 even | 14:57:19 |
| 13 Aug 2025 |
|  Mrjtjmn joined the room. | 05:53:57 |
|  aveltras joined the room. | 09:38:45 |
