| 29 Jan 2026 |
|  Gilles Poncelet joined the room. | 22:07:17 |
| 30 Jan 2026 |
 connor (he/him) | Can someone review/merge https://github.com/NixOS/nixpkgs/pull/485211? | 02:20:04 |
| connor (he/him) | 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 (he/him) | Oh god is it up to date | 16:32:45 |
| connor (he/him) | Those manifests should come directly from NVIDIA (but they need a new line added to comply with the Nixpkgs formatter) | 16:33:13 |
| 1 Feb 2026 |
|  Fernando Rodrigues changed their display name from SigmaSquadron to Fernando Rodrigues. | 10:43:22 |
 Gaétan Lepage | OpenCV 4.13.0 bump has just been merged! | 22:56:18 |
| 3 Feb 2026 |
 Kevin Mittman (UTC-8) | Hi Bryan Honof I can help answer questions about the JSON manifestsconnor (burnt/out) (UTC-8) You could have mentioned that, happy to add a newline at the end | 21:41:47 |
| connor (he/him) | Gaétan Lepage: PR for fixes related to CUDA 13 breakages: https://github.com/NixOS/nixpkgs/pull/485208 | 22:06:42 |
| 4 Feb 2026 |
|  Yorusaka Miyabi joined the room. | 01:48:31 |
|  Benjamin Isbarn joined the room. | 09:10:02 |
| Benjamin Isbarn | Hi, I'm trying to run an application that uses OpenCV with cuda support built with nix on a NVIDIA® Jetson™ Orin™ Nano 8GB. This fails essentially with the following message:
Internal Error: OpenCV(4.11.0) /build/source/modules/dnn/src/cuda4dnn/init.hpp:55: error: (-217:Gpu API call) CUDA driver version is insufficient for CUDA runtime version in function 'getDevice'\n (code: GpuApiCallError, -217)
I did the old /run/opengl-driver/lib trick which worked flawlessly on another device which was a PC running a 3050. But this doesn't seem to work on the Jetson (I do see that the libcuda i symlinked in /run/opengl-driver/lib get's loaded when running it within strace). I tried to use the same cuda version thats on the Jetson (i.e.g cat /usr/local/cuda/version.json gave me "version" : "11.4.19" so I went with cuda_11_4 in nix.
Any help would highly be appreciated :) | 11:39:09 |
| 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.org
i'm mildly peeved about a recent merging of something i maintain where i'm pretty sure the merger does not own the expensive hardware required to properly test the package. i don't think it broke anything but i was given precisely 45 minutes to see the notification before somebody merged it ugh, 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 |
| Winter (she/her) | oh yes i did | 03:35:49 |
| Winter (she/her) | but that's not what the topic of this PR/the notice is, though? | 03:36:11 |
| Winter (she/her) | this wouldn't help that | 03:36:14 |
