| 13 Nov 2025 |
 K900 | OK yeah that's just gone from 2.0 | 11:39:02 |
| K900 | According to the changelog | 11:39:07 |
| K900 | I am out lol | 11:39:09 |
 vcunat | https://github.com/HDFGroup/hdf5/blob/develop/release_docs/CHANGELOG.md#%EF%B8%8F-breaking-changes | 11:42:46 |
| vcunat | * https://github.com/HDFGroup/hdf5/blob/hdf5_2_0_0/release_docs/CHANGELOG.md#%EF%B8%8F-breaking-changes | 11:43:43 |
 leona | I think most of the PRs to staging are merged now and trunk-combined will also be ready soon. So we can probably start tomorrow morning (CET side of the planet) with staging-next? | 23:16:29 |
 ivy | but cachix | 23:26:19 |
| leona | that might block trunk, but we don't have the time to wait for that to be fixed | 23:27:29 |
| leona | and also tbh if nobody of them cares so long for fixing it, I think about removing it as a blocker | 23:27:55 |
| leona | if we don't start staging-next within the next day, we probably won't have another cycle (I would need to talk with jopejoe1 about it), but we're already quite late right now. | 23:28:53 |
| 14 Nov 2025 |
 Fabián Heredia | Just as a consideration before staging-next begins this seems security related (out of bounds read is the only fix): https://github.com/NixOS/nixpkgs/pull/461446 | 05:27:52 |
 jopejoe1 (4094@39c3) | Yeah don't think we will be able to get another one in if don't start it today | 07:35:46 |
| vcunat | Yes, staging-next in a few moments. No use blocking that because of the cachix situation. | 08:22:49 |
| vcunat | https://github.com/NixOS/nixpkgs/pull/461523 | 09:49:27 |
| leona | thank you | 09:50:21 |
| vcunat | I'd hope we can merge it around 25th - 26th. | 09:52:04 |
| vcunat | e.g. the last spacing was 12 days. | 09:52:27 |
| ivy | but still no cachix fix? | 09:52:53 |
| vcunat | I'm not aware of any. | 09:53:38 |
| leona | yes, we probably need to move the branch-off a bit. | 09:54:18 |
| vcunat | People relevant to cachix had been pinged over GitHub mentions and Matrix. I saw also Robert's emoji-reaction on that. I'd hope that a fix won't need any huge rebuild. | 09:57:53 |
|  Daniel joined the room. | 14:27:38 |
 Wolfgang Walther | Periodic merges are right now failing constantly. This seems to be related to Nixpkgs' repo size on GitHub. The Nixpkgs core team is in touch with GitHub to look into that. | 18:25:15 |
 dish [Fox/It/She] | congratulations to the nixpkgs community for finding yet another github limitation | 18:30:33 |
| dish [Fox/It/She] | * congratulations to the nixpkgs community for finding yet another github issue related to the size of the repo lol | 18:30:41 |
| vcunat | I've been seeing lots of unicorns in the past few days, too. | 18:38:10 |
| Wolfgang Walther | yeah me too. We're unsure whether Nixpkgs maybe caused https://www.githubstatus.com/incidents/1jw8ltnr1qrj :D | 18:40:16 |
 hexa | maybe get your head checked | 18:53:15 |
 Gaétan Lepage | Should protobuf: 33.0 -> 33.1 target staging or staging-next? | 23:38:16 |
| 15 Nov 2025 |
| vcunat |
Rebuild: linux 4523, darwin 2011
Rebuild-wise that would be OK for either branch at this point. But note that staging won't reach 25.11 whereas this staging-next will. That also implies restrictions on breaking changes.
| 06:29:17 |
