| 2 Nov 2025 |
 leona | fyi We thought a bit about the release schedule and adapted it to reality, it will probably be something like that. I propose that we'll see how the staging-next cycle that starts in the next 2 days looks like and then decide if a second one still fits | 17:28:29 |
| leona | 
Download image.png | 17:28:32 |
| leona | i think a second cycle will be quite tight, we could decide tho to branch-off a few days (like 2-3) earlier and then already start a staging-next-25.11 cycle | 17:29:41 |
 Vladimír Čunát | I'll start staging-next within a few hours maybe. | 17:31:27 |
| Vladimír Čunát | I wonder if it's worth considering to start "encouraging ZHF fixes" against the staging-next branch in a few days already, before it gets to master. | 17:41:20 |
| Vladimír Čunát | (I don't recall if the workflow instructions would have to get adapted significantly.) | 17:41:57 |
| Vladimír Čunát | There's not too much time before the end of the month. | 17:42:21 |
| Vladimír Čunát | Though two full staging-next cycles might realistically fit. | 17:42:49 |
| Vladimír Čunát | (if we don't get stuck on something) | 17:43:02 |
| Vladimír Čunát | * Though two full staging-next cycles might realistically fit under 4 weeks. | 17:43:23 |
|  @dawnofmidnight:catgirl.cloud changed their display name from whispers to whispers (it/fae). | 17:58:06 |
| Vladimír Čunát | Oh, I didn't realize that ZHF was already announced several minutes before that comment 🤦 | 19:10:30 |
| Vladimír Čunát | Also note that the planned GNOME upgrade is not in the just-starting staging-next. And it's a huge rebuild.
https://github.com/NixOS/nixpkgs/pull/440720#issuecomment-3478235753 | 20:07:54 |
| leona | ack | 20:08:21 |
| Vladimír Čunát | New staging-next:
https://github.com/NixOS/nixpkgs/pull/457894 | 20:08:27 |
 Grimmauld (any/all) | wait is that the one with the glib upgrade? That'll be fun | 20:13:14 |
| Grimmauld (any/all) | also eval error because gradle? Thats not good... | 20:16:03 |
 Wolfgang Walther | I'm currently looking at that Eval error. Seems to be because wrapGradle forces evaluation of more than it should, so accessing meta is not possible without triggering the insecure error immediately. | 20:23:38 |
| Wolfgang Walther | I suspect it's that lib.makeOverridable call... | 20:23:50 |
| Wolfgang Walther | This is only a problem for GHA eval, I think, not for hydra. | 20:25:16 |
| Wolfgang Walther | Actually it's this: // lib.optionalAttrs (this-gradle-unwrapped == gradle-unwrapped) {. I think I remember who proposed it... I know that line... | 20:28:01 |
 K900 | Rust 1.91? | 20:38:52 |
| K900 | CC @Alyssa Ross | 20:38:58 |
| Wolfgang Walther | Proposed a fix in https://github.com/NixOS/nixpkgs/pull/457900 | 20:50:45 |
 Alyssa Ross | Rust will happen when it happens I think | 21:48:50 |
| Alyssa Ross | I need https://github.com/NixOS/nixpkgs/pull/457908 this cycle if somebody would mind reviewing so we can beat Hydra to Valgrind | 21:50:10 |
| Alyssa Ross | oh eval is broken on staging-next or master, lovely | 21:53:20 |
| Alyssa Ross |
error: Package ‘gradle-7.6.6’ in /home/runner/work/nixpkgs/nixpkgs/nixpkgs/trusted/pkgs/development/tools/build-managers/gradle/default.nix:295 is marked as insecure, refusing to evaluate.
| 21:53:31 |
| Alyssa Ross | well, I need to go to bed | 21:53:44 |
| Grimmauld (any/all) | was just fixed | 21:54:11 |
