Staging | 349 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/ | 113 Servers |
| Sender | Message | Time |
|---|---|---|
| 22 Feb 2026 | ||
| * I have a PR (https://github.com/NixOS/nixpkgs/pull/492830) against staging-next. It fixes python314Packages.cmd2, which immediately fixes at least a couple of packages (on each OS), and removes one reason that about 50 other packages (also on each OS, even though they continue to fail). But it's 9k linux and 7k darwin rebuilds... Is it mergable at this point in the cycle? | 03:24:47 | |
| * I have a PR (https://github.com/NixOS/nixpkgs/pull/492830) against staging-next. It fixes python314Packages.cmd2, which immediately fixes at least a couple of packages (on each OS), and removes one reason that about 50 other packages fail (also on each OS). But it's 9k linux and 7k darwin rebuilds... Is it mergable at this point in the cycle? | 03:28:57 | |
| 19:48:19 | ||
| 22:54:26 | ||
| 23 Feb 2026 | ||
staging-next merged | 12:12:13 | |
| 12:12:17 | |
| Thanks for the numerous fixes 🙂 | 12:15:21 | |
| (you're certainly welcome to continue directly on master) | 12:15:44 | |
| Are we doing 25.11 after or another master | 12:48:59 | |
| 12:49:59 | |
| There's really not a lot on 25.11 | 12:50:04 | |
| A few more are open: https://github.com/NixOS/nixpkgs/pulls?q=base%3Astaging-25.11+is%3Aopen | 12:51:59 | |
| (including some security fixes) | 12:52:10 | |
| 24 Feb 2026 | ||
Uh, I forgot to add staging-nixos before that. Way too late now; we already have all tests built and nixos-unstable is activating. | 04:55:52 | |
Added 5 more lines. | 07:17:55 | |
| I think 25.11, as (up to) one month delay is long enough for security fixes as it is. | 07:18:34 | |
| * I think 25.11, as (up to) one month delay is long enough for security fixes already. | 07:18:51 | |
New staging-next-25.11:https://github.com/NixOS/nixpkgs/pull/493587 | 07:31:06 | |
| The first change in there was merged on Jan 25, so the delay will be more like 5 weeks. | 07:31:34 | |
| (though the first real security fix was merged about a week later) | 07:32:50 | |
| Redacted or Malformed Event | 07:45:13 | |
| Wonder if that's automatable. Feels like it should be... | 07:45:47 | |
| We can probably auto-merge staging-nixos into next? | 07:46:26 | |
| Like instead of going master -> next -> staging, we can go master -> staging-nixos -> next -> staging | 07:46:42 | |
| 13:02:48 | ||
| Oh yeah perfect | 14:48:50 | |
| we're several versions behind on no build failures across a bunch of heterogeneous nixos configs with lots of desktop software, and the systems I've tested run fine. I think it makes sense to move forward with this, as it's going to start blocking more and more updates (right now, for example, latest | 14:57:30 | |
| Sure, let's just get this in | 14:59:20 | |
| hey all, currently calibre is broken on unstable and master ( https://hydra.nixos.org/build/322102655 ), last success was at https://hydra.nixos.org/build/321911294 . error message states it cannot find qt6 qmake anymore. i tried to pinpoint the issue (or have rather have mr computer trying to build the package until it is successful) and it came up with the following solution https://p.krebsco.de/1x23192 however i have absolutely no idea if this is a good idea and i had no plan to touch qt6 buildhooks in first place. setting before i create a PR, could anybody have a quick look at the solution above? | 17:37:25 | |
| I believe we have a fix for that in the next staging | 17:37:43 | |