| 18 Apr 2026 |
 ccicnce113424 | Actually, the window doesn't close until 2026-04-27 07:00 UTC, so we've still got a few days, not "tomorrow". That said, I think this PR is ready to merge right now. | 09:03:52 |
| 20 Apr 2026 |
 Edward Tjörnhammar | You risk breaking HPC deployments with these changes | 09:05:45 |
| Edward Tjörnhammar | * You risk breaking HPC deployments with these changes, rushing them without further confirmations is reckless | 09:07:42 |
| Edward Tjörnhammar | * You risk breaking HPC deployments with these changes, rushing them without further confirmations is reckless | 09:08:01 |
| ccicnce113424 | @[Edward Tjörnhammar] I'm not rushing anything. I didn't touch the HPC-specific logic, and the PR is literally open for review. I've already replied to all your concerns in the PR comments. If you genuinely believe HPC is broken by these changes, please quote the exact lines of code on GitHub that cause the issue. Let's keep the discussion technical and factual. | 09:40:13 |
| ccicnce113424 | https://github.com/NixOS/nixpkgs/pull/498612#issuecomment-4279399845 | 09:43:58 |
| ccicnce113424 | * @[Edward Tjörnhammar] I'm NOT rushing anything. I didn't touch the HPC-specific logic, and the PR is literally open for review. I've already replied to all your concerns in the PR comments. If you genuinely believe HPC is broken by these changes, please quote the exact lines of code on GitHub that cause the issue. Let's keep the discussion technical and factual. | 09:58:20 |
| Edward Tjörnhammar | In reply to @ccicnce113424:matrix.org
@[Edward Tjörnhammar] I'm NOT rushing anything. I didn't touch the HPC-specific logic, and the PR is literally open for review. I've already replied to all your concerns in the PR comments. If you genuinely believe HPC is broken by these changes, please quote the exact lines of code on GitHub that cause the issue. Let's keep the discussion technical and factual. That would be great, I said you risk breaking HPC deployments not that it was a fact, the concerns in my review are my technical and factual concerns. That you adressed my concerns were my main priority since you seemed to want to get this in within the merge window. I will take another look tonight. | 10:38:07 |
|  Moraxyc joined the room. | 12:36:07 |
|  caniko changed their profile picture. | 14:19:45 |
| 21 Apr 2026 |
 Gaétan Lepage | Hi Samuel Ainsworth!
I'm having yet another hash mismatch on xla:
error: hash mismatch in fixed-output derivation '/nix/store/r97i94lw0gyqi8x1z7w0f65v8p8hwlyr-xla-0-unstable-2026-02-21-deps.tar.drv':
specified: sha256-QTUqcP5t91Z4s+esxxFz2tGJAJplWXWZuYPqcC7ld+E=
got: sha256-go2EUhzSI2LcvYTjkrj3nbbwiLSusuj2Ijh6rlcarqE=
| 20:51:35 |
| 22 Apr 2026 |
 Samuel Ainsworth | Hmm interesting could you send me your deps file again and I can debug? | 00:06:40 |
| Gaétan Lepage | Sure:
https://mega.nz/file/PpZDzZqT#oGHHBpawgcbkqtk49FlVv1tL3Nvd4-FhEXZfulvxtfc | 07:11:35 |
| 23 Apr 2026 |
|  @little_dude:matrix.org left the room. | 09:36:06 |
| Gaétan Lepage | connor (burnt/out) (UTC-8), do you know if libnvvm is a CUDA>=13.0 thing? Or should it also be packaged for 12.9. | 16:18:41 |
| Gaétan Lepage | * connor (burnt/out) (UTC-8), do you know if libnvvm is a CUDA>=13.0 thing? Or should it also be packaged for 12.9? | 16:18:49 |
| Gaétan Lepage | * connor (burnt/out) (UTC-8), do you know if libnvvm is a CUDA>=13.0 thing? Or should it also be packaged for 12.9?
It should be... But only the 13.x redist manifests mention it... | 16:21:09 |
| Gaétan Lepage | * connor (burnt/out) (UTC-8), do you know if libnvvm is a CUDA>=13.0 thing? Or should it also be packaged for 12.9?
It should be... But only the 13.x redist manifests mention it...
EDIT: It's under cudaPackages.cuda_nvcc/nvvm for 12.x 🫠 | 16:27:19 |
 connor (burnt/out) (UTC-8) | Oh my god | 16:28:44 |
| connor (burnt/out) (UTC-8) | Oh wait yeah it was bundled with NVCC then was split out into its own library phew | 16:29:05 |
| connor (burnt/out) (UTC-8) | IIRC I symlink it into NVCC to avoid breaking consumers? | 16:29:22 |
| Gaétan Lepage | As you say. phew. | 16:31:54 |
| Gaétan Lepage | Raw fun: https://github.com/NixOS/nixpkgs/pull/512828 | 16:32:17 |
 SomeoneSerge (matrix works sometimes) | I'd rather change the definition of libnvvm to extract itself from nvcc in cuda<13 and declare that the current interface. | 16:55:27 |
| connor (burnt/out) (UTC-8) | The latent concern I have is around packages assuming relative path access to work :( | 18:04:25 |
| SomeoneSerge (matrix works sometimes) | Depending on fu... motivation, this is not necessarily a lost battle;) | 18:44:14 |
| Gaétan Lepage | connor (burnt/out) (UTC-8), I'd like to get this one in if you have a minute: https://github.com/NixOS/nixpkgs/pull/512796 | 20:49:46 |
| 24 Apr 2026 |
|  amarshall joined the room. | 05:39:52 |
 mdietrich | Hi all, this might be a stupid question but why do I have to build some packages still locally when on nixos-unstable with nixpkgs.config.cudaSupport = true; even though I've configured the binary cache in my substituters? Is this just because cuda packages have complicated versions and change very often that not all packages are built and cached on the cachix or am I doing something wrong?
This actually hinders me from updating right now because python3.13-torch-2.11.0 for python3.13-whisper-20250625 and python3.12-torch-2.11.0 for aider-chat-playwright-browser-help-bedrock-0.86.1 are eating my RAM and swap alive.
| 10:25:30 |
| mdietrich | Oh, and I'm sorry if this is the wrong place, I just remembered that there is a forum, duh. | 10:26:21 |
