| 25 Mar 2026 |
 Gaétan Lepage | For sure! The diff is fairly trivial. The bulk of the job will be the testing.
yorik.sar this is a good candidate for testing the new GitHub app on our infra. | 00:34:39 |
| Gaétan Lepage | FYI: The PR updating jax to 0.9.2 and the rest of the ecosystem with it (22 commits 🫠) has finally been merged! (after 2 months of efforts)
Changelogs:
https://github.com/NixOS/nixpkgs/pull/482118 | 00:37:22 |
| Gaétan Lepage | * FYI: The PR updating jax to 0.9.2 and the rest of the ecosystem with it (22 commits 🫠) has finally been merged! (after 2 months of efforts)
Changelogs:
https://github.com/NixOS/nixpkgs/pull/482118 | 00:37:29 |
| Gaétan Lepage | * FYI: The PR updating jax to 0.9.2 and the rest of the ecosystem with it (22 commits 🫠) has finally been merged! (after 2 months of efforts)
Please let me know if you notice any regression.
Changelogs:
https://github.com/NixOS/nixpkgs/pull/482118 | 00:39:56 |
| 26 Mar 2026 |
 SomeoneSerge (matrix works sometimes) | /me mumbles aside: shoulda patched it out years ago | 04:15:10 |
|  @meadow_weasel:matrix.org left the room. | 15:05:31 |
| 27 Mar 2026 |
| Gaétan Lepage | Do we agree that pytorch got their upper bounds wrong?
https://github.com/pytorch/pytorch/blob/v2.11.0/torch/utils/cpp_extension.py#L75
https://docs.nvidia.com/cuda/archive/12.9.1/cuda-installation-guide-linux/index.html#host-compiler-support-policy
GCC 14.x should be supported with cuda 12.9 | 14:46:42 |
| Gaétan Lepage | Also, it's unclear why this only blows up in torchvision and not in torch itself... | 14:48:33 |
| 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 |
| tpw_rules | i guess? it's my personal opinion and thought and i'd appreciate comment from the man himself | 03:39:28 |
| tpw_rules | i think i mixed my metaphors slightly. i don't intend to put words in his mouth | 03:40:00 |
| tpw_rules | there's also this: https://github.com/NixOS/nixpkgs/pull/185078 | 03:42:14 |
| tpw_rules | it's not really fair to characterize python general package updates as "breaking everything all over again" and the notice wouldn't have prevented it. it's just sort of life as being the center of a tangled web of dependencies | 03:43:13 |
