| 1 Apr 2026 |
 SomeoneSerge (matrix works sometimes) | Yet to check the link, but generally Kiskae is the driver guru | 15:53:44 |
|  penguin joined the room. | 21:57:36 |
| 2 Apr 2026 |
 connor (he/him) | you ever see something that you just know is going to cause you immense pain in 3-6mo? | 18:41:10 |
| connor (he/him) | https://github.com/NixOS/nixpkgs/pull/505958
- I need to support onnx-tensorrt
- It's an absolute pain in the ass to package and make work over all the CUDA versions I have to support (cough cuda-legacy cough)
- It's not packaged in-tree (I packaged a (then new!) copy here https://github.com/ConnorBaker/cuda-packages/blob/7604ebdb8e9484c633710b408e50816e95ebfac9/pkgs/by-name/on/onnx-tensorrt/package.nix)
- I don't understand why ONNX_ML being set to 1 broke onnx-tensorrt or even know if it's still a problem
| 18:43:19 |
 ccicnce113424 | In reply to @ccicnce113424:matrix.org
ping NVIDIA transitioned to zstd compression starting with version 530.30.02 three years ago, yet the build dependencies were never updated to reflect this. Consequently, driver extraction has been relying on the bsdtar fallback for three years—an oversight that has gone completely unnoticed until now. | 19:28:44 |
| 3 Apr 2026 |
| SomeoneSerge (matrix works sometimes) | Yes, daily. | 01:43:30 |
|  julm joined the room. | 02:36:25 |
| connor (he/him) | Okay I started packaging cuda_tileiras and cuda-tile | 14:56:35 |
| connor (he/him) | Does... does tileiras use dlopen with relative paths to find libnvvm.so 😱 | 15:08:03 |
| connor (he/him) | Also, can someone explain https://developer.download.nvidia.com/compute/cuda/redist/cuda_compat_orin/ to me? If I had to hazard a guess, it would be that it would allow using CUDA 13.1/13.2 on a Jetson based on JetPack 7 (since support for Orin is added in JetPack 7.2, but that hasn't been released yet as far as I can tell, though it is talked about in the CUDA 13.2 blog post: https://developer.nvidia.com/blog/cuda-13-2-introduces-enhanced-cuda-tile-support-and-new-python-features/#embedded_devices). Is that correct? Or does it allow forward compat across major versions and can be used with JetPack 6, similar to how cuda_compat for Orins on JetPack 5 allows support for up to CUDA 12.2 despite shipping with CUDA 11.4. | 15:19:07 |
| connor (he/him) | Unrelated, but I'm getting errors with the nix-required-mounts hook, maybe I'm just on a bad commit:
$ /nix/store/kgcbq3ablba98myqn8j4sq7yla6nzs3m-nix-required-mounts-0.0.1/bin/nix-required-mounts /nix/store/5i5w8byychlxjbrjnvfl4rwbi9wqr66d-nix-shell-env.drv
Traceback (most recent call last):
File "/nix/store/kgcbq3ablba98myqn8j4sq7yla6nzs3m-nix-required-mounts-0.0.1/bin/.nix-required-mounts-wrapped", line 9, in <module>
sys.exit(entrypoint())
~~~~~~~~~~^^
File "/nix/store/kgcbq3ablba98myqn8j4sq7yla6nzs3m-nix-required-mounts-0.0.1/lib/python3.13/site-packages/nix_required_mounts.py", line 142, in entrypoint
[canon_drv_path] = parsed_drv.keys()
^^^^^^^^^^^^^^^^
ValueError: too many values to unpack (expected 1)
Using commit https://github.com/NixOS/nixpkgs/commits/8110df5ad7abf5d4c0f6fb0f8f978390e77f9685 of Nixpkgs. I remember something about JSON derivation format change but I can't remember for the life of me if we already fixed that. Previous commit was https://github.com/NixOS/nixpkgs/commits/a6531044f6d0bef691ea18d4d4ce44d0daa6e816.
| 15:49:56 |
 Gaétan Lepage | Interesting, I'm facing another error:
error:
… while setting up the build environment
error: getting attributes of path '/nix/store/02wkfkv635277dyq176lw5dcqpxlpsl0-kmod-31/sbin/bin': No such file or directory
| 15:56:06 |
| 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 |
| Winter (she/her) | ~~is that what you're saying and i'm just lagging behind~~ | 03:36:27 |
| tpw_rules | no it wouldn't, but it reads to me like that's the underlying problem and this is a manifestation which can be controlled more easily. not to put thoughts in people's head | 03:37:07 |
| Winter (she/her) | right
(what do you mean by that last sentence, you don't want to influence anyone's opinion on the matter by saying that?) | 03:38:29 |
