| 12 May 2026 |
 vcunat | But generally you can put your mass-rebuild commits atop some master commit and select staging as the merge target. | 07:31:05 |
| vcunat | Of course there's a risk of conflicts, but usually it's not high. And it minimizes the amount of rebuilds done locally. | 07:31:34 |
 emily | @k900:0upti.me do you feel like cross-building some Qt stuff for https://github.com/NixOS/nixpkgs/pull/518539 | 12:40:08 |
| emily | (does Qt exercise Meson anywhere?) | 12:40:17 |
 K900 | Not directly | 12:41:10 |
| K900 | Qt cross is already a fuck | 12:41:16 |
| K900 | It's probably fine to make it more fuck | 12:41:35 |
| emily | it's more about not knowing whether CMake/Meson cross actually work at all after this yet | 12:46:48 |
| emily | (though they ought to) | 12:46:51 |
| K900 | Cmake cross never works, it usually just happens to kinda do the right thing by complete accident | 12:48:13 |
| emily | ok but the PR is literally moving around stuff we have to make CMake cross work :P | 13:28:21 |
 emily | I can fix this tomorrow or the day after tomorrow | 19:58:42 |
| 13 May 2026 |
| emily | vcunat: just checking on this? not sure when the first 26.11 cycle is due | 16:38:32 |
 leona | at least not in the next 7-10 days ^^ | 16:42:24 |
| leona | * at least not in the next 7 days ^^ | 16:42:38 |
| vcunat | The current staging won't reach 26.05, so I guess you can already merge changes in there? | 16:47:58 |
| emily | but it's already building for x86_64-darwin, right? | 16:48:12 |
| emily | so makes sense to do it next cycle instead | 16:48:15 |
| vcunat | staging only builds stdenvs | 16:48:31 |
| vcunat | I can stop that immediately easily. | 16:48:42 |
| emily | hmmm | 16:49:06 |
| emily | next cycle would be easier for me timing-wise | 16:49:09 |
| emily | because right now the PRs I have would break update scripts etc. and I'll need to take a day or so to tidy stuff up | 16:49:22 |
| vcunat | I don't really know what will the next staging-next* be, as we will have 3 different candidates. | 16:49:40 |
| vcunat | * I don't really know what the next staging-next* will be, as we will have 3 different candidates. | 16:49:52 |
 hexa | we should probably go for stagingn-25.11 next | 16:50:34 |
| vcunat | Channel-update scripts only come to play after merging staging-next to master. | 16:50:38 |
| hexa | Redacted or Malformed Event | 16:50:38 |
| emily | right. well, I wanted to get the drop in early in the release cycle to avoid wasting a bunch of compute, but just need a couple days to rebase and finish the necessary clean-ups | 16:50:48 |
| vcunat | But that's too late, as we have all binaries at that point. | 16:50:49 |
