| 19 Feb 2026 |
 woobilicious | do we have a link to the failing test? I assume it's on hydra somewhere | 05:46:01 |
| woobilicious | lol, why is hydra's UI so confusing, do periods break hydra search? wtf | 05:51:57 |
| woobilicious | Ahh it hasn't been tested since v10.9 in 2023 | 05:59:01 |
| woobilicious | Okay fixed: https://github.com/LeventErkok/sbv/pull/772 | 06:56:25 |
 peddie | the hero we don't deserve! nice one! | 07:09:40 |
| woobilicious | yeah was easy find :D | 07:09:51 |
| woobilicious | I also like feeling productive instead of wasting time on the actual code I was gonna write lol | 07:10:19 |
|  catsarecute joined the room. | 19:05:45 |
 alexfmpe | https://github.com/cdepillabout/nix-haskell-updates-status is nearly a month outdated, is that expected? | 22:27:45 |
|  -> @n:rab.lol left the room. | 22:43:10 |
 maralorn | Nope, that is a known problem caused by an eval error. | 22:51:54 |
| woobilicious | The failing tests on sbv go deeper, than just the fix I made, we should probably just disable tests | 22:58:36 |
| woobilicious | Is there a logic to the configuration-common.nix file order? | 23:09:56 |
| woobilicious | I'll add the changes and open a PR against the haskell-updates branch. | 23:17:32 |
| alexfmpe | roughly grouping related things lots of conflict-avoidance by not adding stuff at the end I guess | 23:21:23 |
| alexfmpe | I do wonder if it shouldn't just be alphabetized and when we apply the same fix to several things, float it to a let at the start | 23:22:20 |
| woobilicious | Oh I think I found the "general" section | 23:23:20 |
| alexfmpe | we have one? | 23:23:28 |
| alexfmpe | I remember the very end being some // { amazonka packages stuff here } and maybe another section like that | 23:24:06 |
| alexfmpe | in other news, I was trying to understand why pkgsMusl doesn't hit the external interpreter for template haskell
nix-repl> pkgsMusl.stdenv.buildPlatform == pkgsMusl.stdenv.hostPlatform
true
nix-repl> pkgsMusl.stdenv.buildPlatform.libc
"musl"
| 23:24:18 |
| alexfmpe | didn't expect it to also change libc on the buildPlatform | 23:24:58 |
| woobilicious | yeah around line 1000 lol, there's a section that's not grouped by anything specifically | 23:25:10 |
| woobilicious | huh was it a bad idea to pull from haskell-updates? it's building git from source when running ./maintainers/scripts/haskell/update-hackage.sh | 23:31:36 |
| woobilicious | Or am I supposed to ignore the instructions in HACKING.md? | 23:34:12 |
| alexfmpe | haskell-updates started branching from staging as of last year or so | 23:41:47 |
| alexfmpe | so if you pull at a bad time, you can eat nasty rebuilds | 23:42:12 |
| alexfmpe | e.g. after staging was merged into it but before hydra CI cached that | 23:42:31 |
| woobilicious | I guess I can just checkout master and the cherry-pick the patch? or maybe just let the scripts be called by the next merge? | 23:43:41 |
| alexfmpe | that said, haskell-updates is mostly for bumping LTS and dealing with the fallout | 23:43:46 |
| woobilicious | I think I'm meant to call ./maintainers/scripts/haskell/regenerate-hackage-packages.sh instead shrug | 23:44:02 |
