!UNVBThoJtlIiVwiDjU:nixos.org

Staging

365 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/116 Servers

Load older messages


SenderMessageTime
14 Apr 2026
@vcunat:matrix.orgVladimír Čunát* For security issues I'd say you could even go directly to master with such rebuild amount.16:28:30
@klea:catgirl.cloudklea (she/her) Ack, will do a PR. 16:28:38
@klea:catgirl.cloudklea (she/her) Done. https://github.com/NixOS/nixpkgs/pull/510019 16:36:20
@tfc:matrix.orgtfc joined the room.17:31:58
@tfc:matrix.orgtfchello! quick question: we merged this test driver change to staging (https://github.com/NixOS/nixpkgs/pull/509654), although it should have gone to staging-nixos. now there are some other pull requests that depend on this and should also go to staging-nixos, so it's a bit annoying that i chose the wrong branch for the first one. what to do with this ideally? revert in staging and re-open PR based on staging-nixos? 17:33:34
@k900:0upti.meK900No need to revert17:41:02
@tfc:matrix.orgtfci don't completely understand the staging dynamics across the different branches. shall we then base the upcoming PRs on staging then, too?18:42:04
@k900:0upti.meK900No18:55:05
@k900:0upti.meK900Just merge to staging-nixos18:55:09
@tfc:matrix.orgtfcBut new prs will not see the change that we have now in staging, or am i wrong? The next prs depend on that19:30:45
@rvdp:infosec.exchangeRamses 🇵🇸You can duplicate the commit in staging-nixos, and git will figure that out later when staging-nixos gets merged into master and then into staging19:33:15
@emilazy:matrix.orgemilygit cherry-pick -x like it's a backport19:34:09
@rvdp:infosec.exchangeRamses 🇵🇸It should just skip it19:33:57
@tfc:matrix.orgtfcPerfect, thank you for the explanation19:56:34
15 Apr 2026
@vcunat:matrix.orgVladimír Čunát

🤔 I didn't think xorgserver would be such a large rebuild.

Rebuild: linux 18610, darwin 22

05:40:25
@vcunat:matrix.orgVladimír Čunát *

🤔 I didn't think xorg-server would be such a large rebuild.

Rebuild: linux 18610, darwin 22

05:51:29
@vcunat:matrix.orgVladimír Čunát Ah right, without xvfb it 06:07:54
@vcunat:matrix.orgVladimír Čunát *

Ah right, without xvfb it's just

Rebuild: linux 231, darwin 4

06:07:59
@vcunat:matrix.orgVladimír ČunátContext: https://github.com/NixOS/nixpkgs/pull/51018406:08:48
16 Apr 2026
@johnrtitor:matrix.orgAinz Ooal Gown

https://github.com/NixOS/nixpkgs/pull/510522

@vcunat:matrix.org could you try running the passthru tests, it seems to hang on me on the nix community builder

15:58:36
@vcunat:matrix.orgVladimír ČunátNot now. In 14 hours perhaps.16:59:36
17 Apr 2026
@pyrox:pyrox.devdish [Fox/It/She] changed their profile picture.16:58:37
@khaneliman:matrix.orgAustin Horstmanshould https://github.com/NixOS/nixpkgs/pull/510964 target staging or staging-next... sorry. out of the loop on staging cycles.19:22:05
@k900:0upti.meK900staging-next19:39:37
18 Apr 2026
@k900:0upti.meK900Has anyone looked at the db failure on darwin?11:12:57
@k900:0upti.meK900https://hydra.nixos.org/build/32589812511:12:58
@k900:0upti.meK900It's blocking like 3k things11:13:17
@hexa:lossy.networkhexa6e1fd3207889796664a0a58771c0137a5420eb66 fixed that11:17:38
@k900:0upti.meK900Oof11:19:39
28 Jun 2021
@grahamc:nixos.org@grahamc:nixos.org set the history visibility to "world_readable".15:07:04

Show newer messages


Back to Room ListRoom Version: 6