| 1 Jan 2026 |
|  matthewcroughan changed their display name from matthewcroughan @ 39c3 (DECT 94667 or 97340 or 67192) to matthewcroughan. | 20:04:02 |
| 5 Jan 2026 |
 Ari Lotter | is there a more general python/ml Nix chat anywhere? trying to get some stuff that isn't technically cuda-related going | 21:24:26 |
 Gaétan Lepage | Just ask it here. There is no other "python+ML" official room I'm aware of.
The closest would be the official Python room, but you would end up pinging even more people. | 21:27:55 |
| Ari Lotter | yeah fair enough.
trying to depend on the python module outlines, it seems not to build because it has a hard requirement of outlines-core==0.2.11, but the version of -core in nixpkgs is 0.2.13. seems like latest outlines release still does depend on 0.2.11. wondering if it makes more sense to PR to.. revert the core update? because it seems like outlines must have been "broken" since https://github.com/NixOS/nixpkgs/commit/a5370c8752db2465791097660563b3b2441b56ac
either that or something changed about the pythonRuntimeDepsCheck - the error i get is that f"{package_name}{requirement.specifier} not satisfied by version {package.version}"
| 21:46:53 |
|  Kevin Mittman (jetlagged/UTC+8) changed their display name from Kevin Mittman (EOY sleep) to Kevin Mittman (UTC-8). | 22:03:14 |
| Ari Lotter | * yeah fair enough.
trying to depend on the python module outlines, it seems not to build because it has a hard requirement of outlines-core==0.2.11, but the version of -core in nixpkgs is 0.2.13. seems like latest outlines release still does depend on 0.2.11. wondering if it makes more sense to PR to.. revert the core update? because it seems like outlines must have been "broken" since https://github.com/NixOS/nixpkgs/commit/a5370c8752db2465791097660563b3b2441b56ac
either that or something changed about the pythonRuntimeDepsCheck - the error i get is that f"{package_name}{requirement.specifier} not satisfied by version {package.version}": outlines-core==0.2.11 not satisfied by version 0.2.13
| 22:39:27 |
| 6 Jan 2026 |
| Gaétan Lepage | Yes, I already fixed it in https://github.com/NixOS/nixpkgs/pull/476381.
You can track it here: https://nixpkgs-tracker.ocfox.me/?pr=476381 | 11:39:15 |
 apyh | everyone is so fast lol thank you | 15:04:29 |
| 8 Jan 2026 |
| Gaétan Lepage | RE onnxruntime-dependent segfaults when cudaSupport is enabled.
Apparently, this does not only happen in onnxscript, but also in rapidocr-onnxruntime. | 10:12:03 |
| Gaétan Lepage | Addressed in https://github.com/NixOS/nixpkgs/pull/478028. | 10:46:28 |
| Gaétan Lepage | connor (burnt/out) (UTC-8) what is your plan for updating the default cudaPackages alias?
Bumping to 12.9 or directly to 13? | 11:02:00 |
| Gaétan Lepage | I ask this because evaluating nixpkgs with cudaSupport = true is currently broken because of python3Packages.paddlepaddle which doesn't have sources for Cuda 12.8. | 12:39:45 |
| Gaétan Lepage | And this broke our cuda-packages-unstable hydra jobset :/ | 12:40:29 |
|  wilhelmines joined the room. | 16:58:46 |
 connor (he/him) | Is that backport-able? | 17:19:30 |
| connor (he/him) | I’d be okay bumping to the latest CUDA once we get OpenCV bumped to the latest release (4.13 came out recently and includes fixes to build with CUDA 13), assuming nothing super important breaks | 17:20:53 |
| connor (he/him) | One of the longer discussions I keep pushing back is deciding on whether or not we want to do release gating, and if so, which packages should be considered blockers. | 17:21:32 |
 SomeoneSerge (back on matrix) | Yes we should, at the least on pytorch | 19:52:18 |
| SomeoneSerge (back on matrix) | Eval error like that is a bug. if you have the time, append "or null" to the attribute look up | 19:56:31 |
| 10 Jan 2026 |
| connor (he/him) | okay well this absolutely sucked and took way too long: https://github.com/NixOS/nixpkgs/pull/478619 | 03:26:56 |
