 | NixOS CUDA | 289 Members |
| CUDA packages maintenance and support in nixpkgs | https://github.com/orgs/NixOS/projects/27/ | https://nixos.org/manual/nixpkgs/unstable/#cuda | 57 Servers |
| NixOS CUDA | 289 Members |
| CUDA packages maintenance and support in nixpkgs | https://github.com/orgs/NixOS/projects/27/ | https://nixos.org/manual/nixpkgs/unstable/#cuda | 57 Servers |
| Sender | Message | Time |
|---|---|---|
| 26 Jan 2026 | ||
 connor (burnt/out) (UTC-8) | Just reviewed, looks good. You might need to update the PR description to change python3Packages.cuda-bindings: init at 13.1.1 though | 23:40:28 |
 Gaétan Lepage | Thanks! | 23:46:49 |
| 29 Jan 2026 | ||
 @oh_yeah:matrix.org left the room. | 00:14:51 | |
| Gaétan Lepage | Hello everyone! I want to share some news regarding the progress yorik.sar and I made on the infra. Some were already communicated, but it doesn't work to summarize everything.
We're trying our best to move things forward as fast as possible. Unfortunately, time and compute resources are limited, so it's never fast enough 😅 Have a nice day! | 09:26:20 |
| Gaétan Lepage | * Hello everyone! I want to share some news regarding the progress yorik.sar, connor (burnt/out) (UTC-8), SomeoneSerge (back on matrix) and I made recently. Some were already communicated, but it doesn't work to summarize everything.
We're trying our best to move things forward as fast as possible. Unfortunately, time and compute resources are limited, so it's never fast enough 😅 Have a nice day! | 09:26:59 |
| Gaétan Lepage | * Hello everyone! I want to share some news regarding the progress yorik.sar, connor (burnt/out) (UTC-8), SomeoneSerge (back on matrix) and I made recently. Some were already communicated, but it doesn't work to summarize everything.
We're trying our best to move things forward as fast as possible. Unfortunately, time and compute resources are limited, so it's never fast enough 😅 Have a nice day! | 09:27:55 |
 hexa | nixos-25.11 should be fairly cheap on rebuilds | 14:12:03 |
| hexa | the opencv 4.13.0 blocks openvino updates | 14:12:22 |
| hexa | * the opencv 4.13.0 update blocks openvino updates | 14:12:27 |
| hexa | * the opencv 4.13.0 update is required to update openvino too | 14:12:44 |
 Gilles Poncelet joined the room. | 22:07:17 | |
| 30 Jan 2026 | ||
| connor (burnt/out) (UTC-8) | Can someone review/merge https://github.com/NixOS/nixpkgs/pull/485211? | 02:20:04 |
| connor (burnt/out) (UTC-8) | Also coming up: https://github.com/NixOS/nixpkgs/pull/485208 | 03:10:33 |
 matthewcroughan @fosdem changed their display name from matthewcroughan to matthewcroughan @fosdem. | 13:50:24 | |
| 31 Jan 2026 | ||
 Bryan Honof | Hey hey, live from FOSDEM here. Is there an easy way to generate those manifest JSON files? Or is that a fully manual process? | 16:26:02 |
| Bryan Honof | Nevermind, should've read the READEME. :) | 16:26:59 |
| connor (burnt/out) (UTC-8) | Oh god is it up to date | 16:32:45 |
| connor (burnt/out) (UTC-8) | Those manifests should come directly from NVIDIA (but they need a new line added to comply with the Nixpkgs formatter) | 16:33:13 |
| 4 Aug 2022 | ||
 Winter (she/her) joined the room. | 03:26:42 | |
| Winter (she/her) | (hi, just came here to read + respond to this.) | 03:28:52 |
 tpw_rules | 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 |
| Winter (she/her) | 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 |
| tpw_rules | no, i haven't yet, but i probably will | 03:31:03 |
| Winter (she/her) | 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 |
| tpw_rules | 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 |
| Winter (she/her) | (it was also simple enough that it was fine and the maintainer said it looked good after) | 03:32:15 |
| tpw_rules | * 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 |
| tpw_rules | 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 |
| Winter (she/her) | the frustration that i see is that people are touching packages that he maintains, am i missing further context here? | 03:35:09 |
| tpw_rules | did you ever see this? https://discourse.nixos.org/t/nixpkgss-current-development-workflow-is-not-sustainable/18741 | 03:35:43 |