| 12 Mar 2026 |
 K900 | I don't understand that build system and it scares me | 11:59:30 |
 emily | I don't have time to look at it right now but it should hopefully be a simple fix unless upstream did something wrong again | 11:59:59 |
| emily | the duplicate symbols are a bit weird | 12:00:41 |
| emily | my guess is that https://github.com/OpenMathLib/OpenBLAS/pull/5423 messed something up while fixing the issue we patch | 12:01:12 |
| emily | https://github.com/OpenMathLib/OpenBLAS/pull/5423/commits/55a10c748df2bdc5e4bf678457e446e23e9996fc | 12:04:04 |
| emily | wondering if we should be using the CMake build | 12:04:09 |
| emily | https://github.com/OpenMathLib/OpenBLAS/issues/5625 | 12:05:34 |
| emily | looks maybe related. | 12:06:01 |
| emily | I would try HEAD and try CMake I suppose. can't spend more time on it now though | 12:07:34 |
 Lun | https://github.com/NixOS/nixpkgs/pull/499299 | 16:26:27 |
| 13 Mar 2026 |
| K900 | We are badly behind on Darwin | 06:26:31 |
| K900 | So maybe we can eat the openblas rebuilds on Linux | 06:26:59 |
| K900 | 
Download image.png | 06:27:41 |
| K900 | Like it's bad bad | 06:27:44 |
 vcunat | There's still x86_64-darwin openblas | 06:36:57 |
| vcunat | It's time for some staging-nixos, as discussed in #security:nixos.org | 06:38:30 |
| K900 | Then I guess we have to revert the kernel bump | 06:41:13 |
| vcunat | Darwin builds tend to get stuck now on "sending inputs". (no idea why or what's changed) Maybe that's making things worse. | 06:47:32 |
 Alyssa Ross | Unclear to me what's going on with the kernels because nobody posted what the regression actually is | 07:49:23 |
| vcunat | Simply unblocking the other changes sounds reasonable to me. | 07:57:19 |
| Alyssa Ross | Yeah, I guess. Just a shame to revert the kernels when there could be no significant issue with them. | 07:57:57 |
| Alyssa Ross | Okay the kernels are confirmed fine. | 08:09:44 |
 Ramses 🇵🇸 | is there any docs on how to fix a merge conflict when merging master in -next? I don't immediately find anything by grepping in the repo. Is this just manual merge and push? | 11:29:41 |
| Ramses 🇵🇸 | * are there any docs on how to fix a merge conflict when merging master into -next? I don't immediately find anything by grepping in the repo. Is this just manual merge and push? | 11:30:03 |
| K900 | Yes | 11:31:08 |
| Ramses 🇵🇸 | ok, fix is trivial (go version difference), I'll push the merge then | 11:34:21 |
| K900 | @Ramses 🇵🇸 this is unnecessary, 1.26 is the default Go version on staging-next | 11:45:37 |
| K900 | https://github.com/NixOS/nixpkgs/pull/497493/changes/e190313e265fc4881b05c0f6076d4ab03a0eefa5..e2e702cb4e1e024359e2915862a2ffaa874a305e | 11:45:39 |
| Ramses 🇵🇸 | Yeah, but I noticed that it was explicitly pinned on master, and always have been, so figured that the maintainers have a reason for that | 11:46:19 |
| Ramses 🇵🇸 | * Yeah, but I noticed that it was explicitly pinned on master, and always has been, so figured that the maintainers have a reason for that | 11:46:32 |
