| 29 Dec 2024 |
 connor (burnt/out) (UTC-8) | In reply to @ss:someonex.net
Yes, which is why this is really is about working with the upstream and getting the changes through on their side, not on nixpkgs side Thoughts on what to do when upstream makes it clear they don’t care or don’t want to implement changes that make it easier (or feasible) to build with Nix? | 21:59:14 |
 SomeoneSerge (matrix works sometimes) | In case of pytorch, I think they are willing to accept stuff | 21:59:41 |
| SomeoneSerge (matrix works sometimes) | They just won't do it themselves | 21:59:53 |
 Gaétan Lepage | Also, I'm afraid we are severly under-staffed :/ | 22:00:12 |
| connor (burnt/out) (UTC-8) | I’ve had good experiences with them too; I meant more like NVIDIA and the ONNX ecosystem | 22:00:14 |
| Gaétan Lepage | Since the latest staging-next merge, everything is kind of broken... | 22:00:38 |
| Gaétan Lepage | Hopefully, we merged the triton-llvm fix and the jax/jaxlib switch to bin. | 22:00:54 |
| SomeoneSerge (matrix works sometimes) | Yeah right... like, pray that they lose the market? | 22:00:55 |
| Gaétan Lepage | But still | 22:00:57 |
| Gaétan Lepage | Also, we have python3.13 now which is very brittle | 22:01:12 |
