| 18 Jan 2026 |
 Randy Eckenrode | https://github.com/NixOS/nixpkgs/pull/481408 fixes it on staging-next. | 20:30:17 |
 Vladimír Čunát | Why not tag it as backport-release-25.11 directly? | 20:34:53 |
|  isabel changed their profile picture. | 20:43:58 |
 Arian | Heya I'm super confused
https://github.com/NixOS/nixpkgs/pull/475079 was opened on 29.12.2025 and merged on 10.01.2026
https://github.com/NixOS/nixpkgs/pull/474788 was merged on 28.12.2025
the 258.3 bump still didn't land on 25.11
Did I miss the window by a few seconds? | 22:05:22 |
| Arian | At this rate , given that the next staging-next-25.11 iteration will take at least a week; it means it'll take ~5 weeks from merge to landing in a channel. That feels long. What could I have done differently to speed this up? Should I have proactively asked to include it in the previous staging-next cycle manually? | 22:15:48 |
| Arian | * At this rate , given that the next staging-next-25.11 iteration will take at least a week; it means it'll take ~5 weeks from merge to landing in a channel. That feels way too long. What could I have done differently to speed this up? Should I have proactively asked to include it in the previous staging-next cycle manually? | 22:15:58 |
 hexa | make sure we have more people fixing darwin problems | 22:26:52 |
| hexa | and prune nixpkgs | 22:26:59 |
