!UNVBThoJtlIiVwiDjU:nixos.org

Staging

393 Members
Staging merges | Running staging cycles: https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aopen+head%3Astaging-next+head%3Astaging-next-25.11 | Review Reports: https://malob.github.io/nix-review-tools-reports/125 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
29 Jun 2026
@benjaminsparks:chat.alugha.appBen Sparksanything after 1.80 is fair game (1.82 promoted aarch64-darwin to tier 1, for example). maybe 1.85 for edition 202415:30:51
@benjaminsparks:chat.alugha.appBen 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:delta.rocksLach
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
@emilazy:matrix.orgemilythe new features are nice and since the compatibility guarantees are strong it's cheap to update15:42:20
@emilazy:matrix.orgemily 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
@emilazy:matrix.orgemilyI think it's a good thing largely and it's up to distros to meet the challenge of keeping up15:43:07
@emilazy:matrix.orgemily and yes, it's fine to base on/merge into staging-next 15:43:23
@emilazy:matrix.orgemilythe 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 cycle15:43:38
@k900:0upti.meK900OK fucking hell do I have to bisect paperless16:44:54

Show newer messages


Back to Room ListRoom Version: 6