!UNVBThoJtlIiVwiDjU:nixos.org

Staging

395 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/127 Servers

Load older messages


SenderMessageTime
21 Jun 2026
@emilazy:matrix.orgemilyesp since most everything that isn't already done can be done mid-cycle13:42:15
22 Jun 2026
@grimmauld:m.grimmauld.deGrimmauld (any/all)Will anyone scream if i just merge the gstreamer things? Those being: https://github.com/NixOS/nixpkgs/pull/514056 https://github.com/NixOS/nixpkgs/pull/459808 I am not quite familiar enough with gstreamer to properly review this, but as it stands it isn't maintained at all and we are accumulating security issues. I would prefer just merging an update that at least on the surface looks reasonable and figure out the breakages later if there end up being problems.12:07:22
@k900:0upti.meK900https://github.com/NixOS/nixpkgs/pull/534242/changes can we get this into this cycle12:46:02
@vcunat:matrix.orgVladimír Čunát I'd like to have the following staging-next done like this:
https://github.com/NixOS/nixpkgs/pull/534248
12:59:14
@vcunat:matrix.orgVladimír Čunát(i.e. a quick one, utilizing staging-next-26.05 binaries)12:59:35
@vcunat:matrix.orgVladimír ČunátI think we have about a day before we need to decide/start. Hydra is now a bit recovering after queue-runner changes.13:00:34
@k900:0upti.meK900I want to see a full staging run with the new queue runner13:00:48
@k900:0upti.meK900For science13:00:50
@vcunat:matrix.orgVladimír ČunátI was more concerned about security fixes waiting since May 8th.13:03:55
@vcunat:matrix.orgVladimír Čunát(those which were able to merge directly due to too many rebuilds)13:04:31
@vcunat:matrix.orgVladimír Čunát* (those which were unable to merge directly due to too many rebuilds)13:04:37
@qyliss:fairydust.spaceAlyssa Rosshow quick do you think it would be?13:37:49
@vcunat:matrix.orgVladimír ČunátThe new queue-runner situation is a bit of wild card here.13:39:47
@hexa:lossy.networkhexathe time to integrate changes from staging into release has come down quite a bit13:40:19
@hexa:lossy.networkhexafrom days to hours13:40:23
@vcunat:matrix.orgVladimír ČunátBut assuming the old speed, I expect ~4 days instead of two weeks.13:40:23
@vcunat:matrix.orgVladimír ČunátYes, the merge lag.13:40:43
@vcunat:matrix.orgVladimír ČunátThough the lag to catch up with NixOS tests seems to remain, at least to some extent.13:40:55
@vcunat:matrix.orgVladimír Čunát(or whatever is slowing it down at this very moment)13:41:06
@hexa:lossy.networkhexaif we only schedule 4 steps in 30s that is bad for big closures with many small files13:41:21
@vcunat:matrix.orgVladimír Čunát* (or whatever is slowing it down at this very moment, e.g. on nixos-26.05)13:41:23
@hexa:lossy.networkhexaRedacted or Malformed Event13:41:29
@vcunat:matrix.orgVladimír Čunát* (or whatever is slowing it down at this very moment, e.g. on https://hydra.nixos.org/jobset/nixos/release-26.05 )13:41:52
@vcunat:matrix.orgVladimír ČunátStill, "Steps completed per minute" metric shows much higher than with the old queue-runner.13:42:53
@vcunat:matrix.orgVladimír ČunátSo even this phase is probably significantly faster than it used to be.13:43:28
@qyliss:fairydust.spaceAlyssa Rosshave we still not disabled the non-blocker NixOS tests?13:44:10
@grimmauld:m.grimmauld.deGrimmauld (any/all)also don't forget we recently killed half the nixos tests13:44:16
@vcunat:matrix.orgVladimír ČunátWe haven't. I've had too many other higher-priority tasks so far.13:44:44
@grimmauld:m.grimmauld.deGrimmauld (any/all)I meant killing the all-drivers tests (https://github.com/NixOS/nixpkgs/pull/532396)13:45:42
@vcunat:matrix.orgVladimír ČunátYes, I know, but I don't expect it helped dramatically with building all those etc and disk-image derivations.13:46:32

Show newer messages


Back to Room ListRoom Version: 6