| 1 Dec 2025 |
 Fabián Heredia | As an informal poll I feel like the gcc15 change is ready for staging.
Would anyone oppose at the moment or is there something that should be addressed before merging into staging? (More fixes can be sent before and during the staging-next cycle) | 21:16:01 |
 Grimmauld (any/all) | my reaction was the same, and it might make sense to just skip that... | 21:51:10 |
| 2 Dec 2025 |
| Fabián Heredia | Would appreciate reviews or merge: https://github.com/NixOS/nixpkgs/pull/440456 | 17:57:26 |
| 4 Dec 2025 |
 vcunat | staging-next-25.05 merged | 08:26:54 |
| vcunat | Maybe several hours ago would've been better, but I wasn't paying attention and only glanced at status and regression now. | 08:27:51 |
|  isabel changed their profile picture. | 16:41:55 |
|  Yifei Sun changed their profile picture. | 20:41:53 |
| 5 Dec 2025 |
 hexa | yanked rust-cbindgen 0.29.1 into release-25.01 (1001-2500) for 146 | 12:58:44 |
| hexa | * yanked rust-cbindgen 0.29.1 into release-25.01 (1001-2500) for Firefox 146 | 12:58:49 |
| hexa | * yanked rust-cbindgen 0.29.1 into release-25.05 (1001-2500) for Firefox 146 | 12:58:53 |
| hexa | seeing as we'll likely not get another staging-25.05 and firefox 146 is due in 4 days | 12:59:07 |
| hexa | * yanked rust-cbindgen 0.29.1 into release-25.05 (1550 rebuilds on each Linux) for Firefox 146 | 13:00:06 |
| hexa | * seeing as we'll likely not get another staging-25.05 and firefox 146 is due in 3 days | 13:00:29 |
| vcunat | I'm not sure what to build next. I thought maybe 25.11, but after looking at the open pull requests, I don't feel like deciding anything or working on this, at least not today. | 13:52:55 |
 leona | I would prefer 25.11 as we will get the python venv fix on darwin. Multiple people already complained about that | 13:55:58 |
| leona | and unstable will probably hell | 13:56:15 |
 Randy Eckenrode | It will also get the clang-tools fix. | 15:38:30 |
| 6 Dec 2025 |
| vcunat | New staging-next-25.05: https://github.com/NixOS/nixpkgs/pull/468267 | 00:06:33 |
| hexa | off by 6 months, sorry | 00:06:48 |
| hexa | * off by 6 months, sorryo say | 00:06:50 |
| hexa | * off by 6 months, sorry to say | 00:06:51 |
| vcunat | I ended up at least starting it without reviewing the open pull requests (except those marked as security) | 00:06:53 |
| vcunat | * New staging-next-25.11: https://github.com/NixOS/nixpkgs/pull/468267 | 00:07:05 |
| vcunat | Corrected now. | 00:07:24 |
| vcunat | I hope I didn't forget any other place. I was just manually replacing 25.05 to 25.11 in the whole text. | 00:07:46 |
| vcunat | I suppose we'll still get a go update in there within a day or two. | 00:08:42 |
 mdaniels5757 | Already in (unless there's going to be another): 25.11-next contains https://github.com/NixOS/nixpkgs/pull/467315 | 02:09:37 |
 whispers (it/fae) | hi! i just opened a pr with an update to libgit2 (https://github.com/NixOS/nixpkgs/pull/468449), and am unsure if this needs to be targeted at master, staging, or staging-nixos. CONTRIBUTING.md says <500 rebuilds is fine for master, but CI also gave it 10.rebuild-nixos-tests. does that mean I should retarget to staging? | 15:34:31 |
| whispers (it/fae) | * hi! i just opened a pr with an update to libgit2 (https://github.com/NixOS/nixpkgs/pull/468449), and am unsure if this needs to be targeted at master, staging, or staging-nixos. CONTRIBUTING.md says <500 rebuilds is fine for master, but CI also gave it 10.rebuild-nixos-tests. does that mean I should retarget to staging? (this may also be the wrong matrix room, unsure where to ask) | 15:35:06 |
 K900 | staging-nixos | 15:36:10 |
