| 29 Jun 2026 |
 Ben Sparks | on which platform? | 14:47:19 |
 K900 | All of them, presumably | 14:47:36 |
| K900 | It complains about dependency versions and if you relax those it fails a bunch of tests and locks up a bunch of other tests | 14:48:05 |
| K900 | This is, unfortunately, very normal Paperless behavior | 14:48:18 |
| Ben Sparks | ah alright. I only asked as there was some issue bumping nltk recently (https://github.com/NixOS/nixpkgs/pull/534599) where paperless got borked, but from your description, it sounds like it's a paperless problem | 14:48:50 |
| K900 | I did not get to that error at least | 14:49:28 |
| K900 | It locks up before that | 14:49:32 |
| K900 | I think | 14:49:33 |
| K900 | I'm gonna try to downgrade DRF | 14:50:40 |
| K900 | That's what usually blows it up | 14:50:44 |
| K900 | Nope wasn't it | 14:55:14 |
| K900 | Bisect time I guess | 14:55:17 |
|  orekushii joined the room. | 15:19:05 |
| orekushii | Hey everyone! I'm unfamiliar with the staging workflows, and was looking to update qsv to 21.1.0, which requires Rust 1.96.0. I found https://github.com/NixOS/nixpkgs/pull/525279 (rust: 1.95.0 -> 1.96.0), which was merged to staging a month ago. What are the next steps to land Rust 1.96 in master? How to monitor progress? I would appreciate any hints :) | 15:21:06 |
 whispers [& it/fae] | it is in the current staging-next cycle, and will reach master as soon as that does: https://github.com/NixOS/nixpkgs/pull/535855 | 15:22:35 |
 Myria | So, at most 2 weeks, the usual length of a cycle. We're already 2-3 days in. | 15:23:20 |
| whispers [& it/fae] | if you want to merge the update into Nixpkgs now, iirc it's fine to merge into staging-next if you want, though it won't can't reach master any faster than that staging-next merge does. | 15:23:57 |
| whispers [& it/fae] | * if you want to merge the update into Nixpkgs now, iirc it's fine to merge into staging-next if you want, though it won't/can't reach master any faster than that staging-next merge does. | 15:24:05 |
 Grimmauld (any/all) | Why does so much shit want latest rust all the time anyways? Like surely you can go back some versions for most boring applications.... | 15:26:16 |
| orekushii | Thank you for the responses! | 15:28:47 |
| orekushii | It's no problem, I'll revisit it once the merge lands | 15:29:08 |
| Ben Sparks | anything after 1.80 is fair game (1.82 promoted aarch64-darwin to tier 1, for example). maybe 1.85 for edition 2024 | 15:30:51 |
| Ben Sparks | * anything after 1.80 is fair game (1.82 promoted aarch64-darwin to tier 1, for example). maybe 1.85 for edition 2024 (but non-bleeding edge would be ncie) | 15:32:21 |
 Lach | In reply to @brightone:matrix.org
Hey everyone! I'm unfamiliar with the staging workflows, and was looking to update qsv to 21.1.0, which requires Rust 1.96.0. I found https://github.com/NixOS/nixpkgs/pull/525279 (rust: 1.95.0 -> 1.96.0), which was merged to staging a month ago. What are the next steps to land Rust 1.96 in master? How to monitor progress? I would appreciate any hints :) https://nixpk.gs/pr-tracker.html is good for that | 15:40:08 |
 emily | the new features are nice and since the compatibility guarantees are strong it's cheap to update | 15:42:20 |
| emily | and distros like Debian stable ship versions so old that it's miserable to support, so either you make yourself very sad or you just roll with rustup | 15:42:47 |
| emily | I think it's a good thing largely and it's up to distros to meet the challenge of keeping up | 15:43:07 |
| emily | and yes, it's fine to base on/merge into staging-next | 15:43:23 |
| emily | the basic stuff gets cached pretty quickly so you should be able to do your PR pretty normally on top of it after the first few days of a cycle | 15:43:38 |
| K900 | OK fucking hell do I have to bisect paperless | 16:44:54 |
