!UNVBThoJtlIiVwiDjU:nixos.org

Staging

400 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/128 Servers

Load older messages


SenderMessageTime
29 Jun 2026
@sempiternal-aurora:matrix.orgMyriaCan someone look at https://github.com/NixOS/nixpkgs/pulls/536669 ? Just some gnat stuff I haven't had the time to properly investigate and fix on darwin14:04:31
@hexa:lossy.networkhexapull, not pulls14:06:30
@sempiternal-aurora:matrix.orgMyria * 14:07:06
@sempiternal-aurora:matrix.orgMyriaThank you, once again writing out links by hand gives bad results14:07:27
@sempiternal-aurora:matrix.orgMyriaI think some of the scipy tests you added were formatted weirdly? CI is complaining on my pr about it.14:10:47
@k900:0upti.meK900Checking14:12:57
@k900:0upti.meK900Ugh yes14:13:28
@k900:0upti.meK900Annoying14:13:43
@k900:0upti.meK900Pushed a fix, sorry14:13:46
@k900:0upti.meK900Oh great14:46:05
@k900:0upti.meK900paperless is fucked14:46:07
@benjaminsparks:chat.alugha.appBen Sparkson which platform?14:47:19
@k900:0upti.meK900All of them, presumably14:47:36
@k900:0upti.meK900It complains about dependency versions and if you relax those it fails a bunch of tests and locks up a bunch of other tests14:48:05
@k900:0upti.meK900This is, unfortunately, very normal Paperless behavior14:48:18
@benjaminsparks:chat.alugha.appBen Sparksah 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 problem14:48:50
@k900:0upti.meK900I did not get to that error at least14:49:28
@k900:0upti.meK900It locks up before that14:49:32
@k900:0upti.meK900I think14:49:33
@k900:0upti.meK900I'm gonna try to downgrade DRF14:50:40
@k900:0upti.meK900That's what usually blows it up14:50:44
@k900:0upti.meK900Nope wasn't it14:55:14
@k900:0upti.meK900Bisect time I guess14:55:17
@brightone:matrix.orgorekushii joined the room.15:19:05
@brightone:matrix.orgorekushii 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:catgirl.cloudwhispers [& 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/53585515:22:35
@sempiternal-aurora:matrix.orgMyriaSo, at most 2 weeks, the usual length of a cycle. We're already 2-3 days in.15:23:20
@whispers:catgirl.cloudwhispers [& 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:catgirl.cloudwhispers [& 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:m.grimmauld.deGrimmauld (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

Show newer messages


Back to Room ListRoom Version: 6