| 10 May 2026 |
 hexa (UTC+1) | yeah, but cheap :D | 20:57:14 |
 Robbie Buxton | Last time I checked graviton was similar if not cheaper | 20:58:00 |
 neobrain | I'm guessing self-hosting has been considered but isn't an option? nvidia has a pretty generous marketing budget for free hardware | 21:01:09 |
 Gaétan Lepage | aarch64-linux support is definitely on our roadmap. For now, the critical blocker is getting access to relevant hardware. I'll give updates in this channel as soon as we get new opportunities in this regard. | 21:01:46 |
|  NixOS Moderation Botchanged room power levels. | 21:07:38 |
| 11 May 2026 |
| Gaétan Lepage | Looking for an approval on https://github.com/NixOS/nixpkgs/pull/517764 (cudaPackages.cudnn update).
connor (burnt/out) (UTC-8) maybe? | 15:52:02 |
 smudge (she/her) | Redacted or Malformed Event | 19:34:06 |
| smudge (she/her) | should the nixos wiki cuda page's cache section be corrected? it recommends the cache.nixos-cuda.org cache and doesn't mention others which lead me to assume it was the one for public use. is nix-community.cachix.org (per this announcement) the one that should be primarily recommended on the wiki? as well as information about using flox's nixpkgs repo and its cache? Or, if the nix-community.cachix.org isn't actually allowed to distribute should flox be the primary suggested cache?
also should the information for cache.nixos-cuda.org be retained, just with a proper disclaimer that it is for internal use only, or how would you like that to be handled? | 19:40:10 |
| smudge (she/her) | should the nixos wiki cuda page's cache section be corrected? it recommends the cache.nixos-cuda.org cache and doesn't mention others which lead me to assume it was the one for public use. is nix-community.cachix.org (per this announcement) the one that should be primarily recommended on the wiki? as well as information about using flox's nixpkgs repo and its cache? Or, if the nix-community.cachix.org isn't actually allowed to distribute should flox be the primary suggested way to access a cuda cache?
also should the information for cache.nixos-cuda.org be retained, just with a proper disclaimer that it is for internal use only, or how would you like that to be handled? | 19:44:22 |
| smudge (she/her) | should the nixos wiki cuda page's cache section be corrected? it recommends the cache.nixos-cuda.org cache and doesn't mention others which lead me to assume it was the one for public use. is nix-community.cachix.org (per this announcement) the one that should be primarily recommended on the wiki? as well as information about using flox's nixpkgs repo and its cache? Or, if the nix-community.cachix.org isn't technically allowed to distribute should flox be the primary suggested way to access a cuda cache?
also should the information for cache.nixos-cuda.org be retained, just with a proper disclaimer that it is for internal use only, or how would you like that to be handled? | 20:10:58 |
| smudge (she/her) | should the nixos wiki cuda page's cache section be corrected? it recommends the cache.nixos-cuda.org cache and doesn't mention others which lead me to assume it was the one for public use. is nix-community.cachix.org (per this announcement) the one that should be primarily recommended on the wiki? as well as information about using flox's nixpkgs repo and its cache? Or, if the nix-community.cachix.org isn't technically allowed to distribute should flox be the primary suggested way to access a cuda cache?
also should the information for cache.nixos-cuda.org be retained, just with a disclaimer that it is for internal use only? | 20:14:14 |
| 13 May 2026 |
| smudge (she/her) changed their display name from smudge to smudge (she/her). | 08:48:06 |
| 14 May 2026 |
|  weriomat joined the room. | 21:11:04 |
| 15 May 2026 |
|  Grayson Tinker changed their display name from graysontinker to Grayson Tinker. | 03:47:21 |
 ccicnce113424 | I'm currently working on improving the packaging of the NVIDIA driver. My plan, is to first split the namespace and driver extraction into two separate files without changing semantics with the assistance of LLM, and then switch from the current passthru pattern to using scope. The first step is now complete. Semantics should be unchanged. I'm not sure how to verify semantic equivalence (suggestions welcome!), but this PR works fine with my current NixOS configuration. As a side note, I also moved nvidia-modprobe into the nvidiaPackages namespace. Since these changes are mostly structural and don't alter semantics, could they be merged separately, with the scope migration and further work happening in a new PR? | 09:07:14 |
| ccicnce113424 | https://github.com/NixOS/nixpkgs/pull/519313 | 09:07:25 |
