| 30 Sep 2025 |
 Grimmauld (any/all) | will poke those this evening | 13:34:35 |
| Grimmauld (any/all) | 
Download image.png | 13:34:56 |
| Grimmauld (any/all) | we should probably fix nixd | 13:35:14 |
| Grimmauld (any/all) | soqt is fixed and i'll poke py-slvs later, but indeed this is looking wonky. Especially considering it is just a few days to feature freeze... | 13:36:09 |
| Grimmauld (any/all) | * soqt is fixed and i'll poke py-slvs later, but indeed this is looking wonky. Especially considering it is just a few days to break freeze... | 13:36:19 |
 nim65s | vcunat: re https://github.com/casadi/casadi/issues/4225 : do you want to handle this directly in https://github.com/NixOS/nixpkgs/pull/444862, or should I open another PR for that ? (in the later case: on which branch ?) | 16:07:30 |
 Vladimír Čunát | Yes, PR targeting staging-next. | 16:15:25 |
| Vladimír Čunát | Or pushing directly there if you're sure. | 16:15:41 |
| nim65s | a PR is fine :) | 16:16:39 |
| 1 Oct 2025 |
|  lovesegfault changed their profile picture. | 22:36:10 |
| 2 Oct 2025 |
| Vladimír Čunát | staging-next: we have all binaries, but still at >9k build regressions even if I subtract newly-succeeding, and we still have those blockers. | 05:46:36 |
| Vladimír Čunát | The convenient moment to start the next iteration is Sunday, as Saturday is the last day of merging breaking changes to critical packages (e.g. glibc upgrade is pending). So I don't feel like rushing a staging-next merge right now. | 05:48:09 |
 Randy Eckenrode | My Darwin stuff still needs reviewed and merged …. | 11:06:18 |
| Randy Eckenrode | Is upping the minimum and SDK version in that first freeze? | 11:10:11 |
| 3 Oct 2025 |
| Grimmauld (any/all) | https://github.com/NixOS/nixpkgs/pull/444599
I am done with libxml2, the failing test in librsvg is NOT a security regression. And we should merge this before the next cycle so it gets into 25.11 | 08:57:35 |
| Grimmauld (any/all) | i did all the testing that is reasonable, but i'd still appreciate some more eyes on this. I don't expect it to break super hard, but you never know with libxml | 08:58:21 |
| Grimmauld (any/all) | (if noone wants to take a look, i'll send it some time tomorrow so it goes into the next cycle (before breaking changes freeze) | 08:59:32 |
| Vladimír Čunát | libxml2 wouldn't be affected by the tomorrow's deadline. But I do think it best to include it in the next staging-next. | 09:02:08 |
| Vladimír Čunát | 2025-10-18 applies to libxml2. | 09:02:36 |
| Grimmauld (any/all) | okay alright, makes sense | 09:03:17 |
| Grimmauld (any/all) | i lost track a little | 09:03:36 |
| Grimmauld (any/all) | actually are you sure? | 09:04:23 |
| Grimmauld (any/all) | libxml is quite far down, its even a dep into cmake and obviously docbook... How are critical packages defined? | 09:04:51 |
| Vladimír Čunát | Pretty narrow list:
https://nixos.github.io/release-wiki/Release-Critical-Packages.html | 09:05:09 |
| Grimmauld (any/all) | ah ty | 09:06:05 |
| Grimmauld (any/all) | then i guess its not cutting it as close as systemd 258 | 09:06:49 |
| Vladimír Čunát | I just went to remind them: https://github.com/NixOS/nixpkgs/pull/427968#issuecomment-3364889517 | 09:08:23 |
| Vladimír Čunát | There's also glibc open: https://github.com/NixOS/nixpkgs/pull/379542 | 09:08:59 |
| Grimmauld (any/all) | oh yeah no we are aware | 09:08:59 |
| Vladimír Čunát | And nothing else, I hope. | 09:09:04 |
