| 7 Nov 2025 |
 hexa | this is staging-next | 16:20:12 |
 Sandro | 🤔 | 16:28:25 |
 Yureka (she/her) | I was suggesting just removing darwin from the conditional though | 18:01:47 |
 Lun | Is there going to be another staging cycle before branch off? | 18:12:40 |
| hexa | yes | 18:17:07 |
 Alyssa Ross | ah okay | 18:45:22 |
| Alyssa Ross | I can do that | 18:45:29 |
| 8 Nov 2025 |
 aloisw | The nix-drv-index numbers are not as trustworthy as the ones obtained by actual eval, since they don't take into account intermediate derivations that aren't accessible themselves. | 06:44:51 |
 Marcus | given the current release cycle, is https://github.com/NixOS/nixpkgs/pull/459886 ok to merge to staging? | 23:23:04 |
 K900 | The release notes look OK | 23:24:23 |
| K900 | But maybe hold off until branch-off anyway | 23:24:31 |
| K900 | Just to be safe | 23:24:34 |
| 9 Nov 2025 |
 samasaur | https://github.com/NixOS/nixpkgs/pull/459987 should fix swift on staging-next | 07:32:42 |
|  tom joined the room. | 08:07:31 |
| K900 | 
Download image.png | 10:14:06 |
| K900 | Can github please fucking not | 10:14:12 |
| K900 | @Wolfgang Walther there's no way to tell it to just stop checking those on automated merges, is there? | 10:15:23 |
| K900 | OK fuck this I give up | 10:17:45 |
| K900 | I retried it like five times | 10:17:53 |
 @wolfgangwalther:matrix.org | I doubt it. For example checking the rule "creation" times out. I'd say that "whether a new branch is created or not" should be independent from basically everything else. No matter how many commits are merged. Thus, I assume this is just github being github - and short of disabling all branch protection, I don't think we can do much.
Even if it worked, I'd not feel comfortable to add the nixpkgs-ci bot account, which does the periodic merges, as a bypasser to all rules. But that's a big if anyway. | 10:22:20 |
| @wolfgangwalther:matrix.org | This is something that should be brought up with GitHub. | 10:29:35 |
