NixOS CUDA | 281 Members | |
| CUDA packages maintenance and support in nixpkgs | https://github.com/orgs/NixOS/projects/27/ | https://nixos.org/manual/nixpkgs/unstable/#cuda | 59 Servers |
| Sender | Message | Time |
|---|---|---|
| 21 Nov 2025 | ||
| i'd love to hear a better one! | 20:17:37 | |
(btw, this programs.nix-required-mounts.presets.nvidia-gpu.enable stuff is super cool. seems to be 99% of the way there) | 20:18:35 | |
| also, i'd like to buy a beer for whoever wrote this error message:
| 20:19:44 | |
| Ah, SomeoneSerge (back on matrix), looks like I owe you a beer: https://github.com/nixos/nixpkgs/commit/3a0d777486191cbdd2ffc7e31f25156da94c4831 | 20:22:04 | |
| 22 Nov 2025 | ||
| I'm going to revisit https://github.com/NixOS/nixpkgs/pull/459416 today and do some final fixups; I'd really like if we could merge it soon SomeoneSerge (back on matrix) Gaétan Lepage given its absence is making my life more difficult | 14:07:58 | |
| I'm in a call with Serge. We'll have a look at it now. | 14:20:00 | |
| Let's have a look | 14:20:23 | |
| I'm still unconvinced by the approach... | 14:20:41 | |
| But since we're not actively benefitting form the stubs right now, maybe we at least merge it for now (without promises to keep) | 14:21:01 | |
| 23 Nov 2025 | ||
| We've had a peek with Gaetan yesterday and LOL turns out the messages aren't even defined in the stubs, but in downstream libraries like in cudart | 07:49:49 | |
| Recently firefox and thunderbird started being rebuilt with cudaSupport enabled because they depend on some other package that now has cuda support. For my laptop with 32GB of ram it takes ages to compile either of them and it eventually runs out of RAM when it's time to link the binary. It seems that they were added to release-cuda in https://github.com/NixOS/nixpkgs/pull/437809 so they should be cached by the nix-community cache. Yet even after waiting for the new commit to be cached nix still tries to build thunderbird and firefox. This seems to only be possible if hydra.nixos-cuda.org doesn't push to nix-community or if it signs things with a key I don't trust. Here is my configuration:
Does anyone know what I have to do to get build outputs from the cuda hydra? | 10:05:21 | |
| * Recently firefox and thunderbird started being rebuilt with cudaSupport enabled because they depend on some other package that now has cuda support. For my laptop with 32GB of ram it takes ages to compile either of them and it eventually runs out of RAM when it's time to link the binary. It seems that they were added to release-cuda in https://github.com/NixOS/nixpkgs/pull/437809 so they should be cached by the nix-community cache. Yet even after I waited for half a week for the new commit to be cached nix still tries to build thunderbird and firefox. This seems to only be possible if hydra.nixos-cuda.org doesn't push to nix-community or if it signs things with a key I don't trust. Here is my configuration:
Does anyone know what I have to do to get build outputs from the cuda hydra? | 10:07:38 | |
| * Recently firefox and thunderbird started being rebuilt with cudaSupport enabled because they depend on some other package that now has cuda support. For my laptop with 32GB of ram it takes ages to compile either of them and it eventually runs out of RAM when it's time to link the binary. It seems that they were added to release-cuda in https://github.com/NixOS/nixpkgs/pull/437809 so they should be cached by the nix-community cache. Yet even after I waited for half a week or more for the new commit to be cached nix still tries to build thunderbird and firefox. This seems to only be possible if hydra.nixos-cuda.org doesn't push to nix-community or if it signs things with a key I don't trust. Here is my configuration:
Does anyone know what I have to do to get build outputs from the cuda hydra? | 10:07:55 | |
| * Recently firefox and thunderbird started being rebuilt with cudaSupport enabled because they depend on some other package that now has cuda support. For my laptop with 32GB of ram it takes ages to compile either of them and it eventually runs out of RAM when it's time to link the binary even with --max-jobs 1. It seems that they were added to release-cuda in https://github.com/NixOS/nixpkgs/pull/437809 so they should be cached by the nix-community cache. Yet even after I waited for half a week or more for the new commit to be cached nix still tries to build thunderbird and firefox. This seems to only be possible if hydra.nixos-cuda.org doesn't push to nix-community or if it signs things with a key I don't trust. Here is my configuration:
Does anyone know what I have to do to get build outputs from the cuda hydra? | 10:16:54 | |
Indeed, it does not push to the nix-community Cachix instance.You can use our new cache instead. | 10:51:20 | |
| Thank you! | 10:54:45 | |
| * | 10:55:02 | |
connor (burnt/out) (UTC-8): {isDeclared{Array,Map},sortArray}.bash very nice | 11:57:04 | |
| 24 Nov 2025 | ||
| thanks, I remember it being an incredibly aggravating experience getting them upstreamed | 01:49:00 | |
| 4 Aug 2022 | ||
| 03:26:42 | ||
| (hi, just came here to read + respond to this.) | 03:28:52 | |
| hey. i had previously sympathzied with samuela and like i said before had some of the same frustrations. i just edited my github comment to add "[CUDA] packages are universally complicated, fragile to package, and critical to daily operations. Nix being able to manage them is unbelievably helpful to those of us who work with them regularly, even if support is downgraded to only having an expectation of function on stable branches." | 03:29:14 | |
In reply to @tpw_rules:matrix.orgugh, 45 minutes? that's... not great. not to air dirty laundry but did you do what samuela did in the wandb PR and at least say that that wasn't a great thing to do? (not sure how else to word that, you get what i mean) | 03:30:23 | |
| no, i haven't yet, but i probably will | 03:31:03 | |
| i admittedly did that with a PR once, i forget how long the maintainer was requested for but i merged it because multiple people reported it fixed the issue. the maintainer said "hey, don't do that" after and now i do think twice before merging. so it could help, is what i'm saying. | 03:31:50 | |
| i'm not sure what went wrong with the wandb PR anyway, i think it was just a boneheaded move on the maintainer's part | 03:32:10 | |
| (it was also simple enough that it was fine and the maintainer said it looked good after) | 03:32:15 | |
| * i'm not sure what went wrong with the wandb PR anyway, i think it was just a boneheaded move on the merger's part | 03:32:19 | |
| but i thought most of the frustration was around packages which don't really involve CUDA breaking the fragile CUDA packages, and i'm not sure how the warning helps in this case. it's not like nixpkgs-review prints out the comments. maybe i'm wrong. but it is a legitimate problem | 03:34:19 | |
| the frustration that i see is that people are touching packages that he maintains, am i missing further context here? | 03:35:09 | |