| 29 Apr 2025 |
 Vladimír Čunát | They might start fixing failures on staging-next 😆 | 16:47:21 |
| 30 Apr 2025 |
|  @fossdd:matrix.org left the room. | 18:30:16 |
 leona | I'll publish a - hopefully good - announcement explaining the situation we're in, and start the ZHF from there. Otherwise time is too limited.. | 20:45:14 |
 Morgan (@numinit) | One of the bits of retrospective from 24.11 said that we should start scaling up our builders pretty soon:
https://discourse.nixos.org/t/nixos-24-11-retrospective/57085 | 20:54:40 |
| leona | To my knowledge thats not really possible / helpful because of the limitations of the hydra scheduler | 20:55:32 |
| Morgan (@numinit) | I have no horse in this race, but was just the notetaker and that reminded me 😀 | 20:55:41 |
| leona | (infra, correct me if i'm wrong) | 20:55:46 |
 Grimmauld (any/all) | current bottleneck is the staging-next of this cycle, which needs K's haskell patches and some darwin love? | 20:57:53 |
| leona | by the default procedure ZHF would start after this cycle's staging-next is merged. I'm not sure what it really needs, but at least it needs 2-3 more days time, if not more. ZHF can also start before, but then we get breaking changes in the ZHF after it started, so not ideal but acceptable | 21:00:01 |
 hexa | no scaling possible right now | 21:01:04 |
 Tristan Ross | In reply to @leona:leona.is
I'll publish a - hopefully good - announcement explaining the situation we're in, and start the ZHF from there. Otherwise time is too limited.. Cool, I'll try to help out with my 128 core system. Will be looking for the ZHF fixes label. | 21:34:50 |
| 1 May 2025 |
|  @bjsowa:matrix.org joined the room. | 00:04:56 |
| Morgan (@numinit) | Yeah I'll toss stuff at it for x86_64 on an EPYC, down to help stabilize | 06:02:25 |
| Morgan (@numinit) | Have both an EPYC 2 and EPYC 4 to toss at ZHF PRs this time :D | 06:03:37 |
| hexa | Darwin capacity is what hydra is missing | 12:56:48 |
| hexa | We have sufficient Linux capability | 12:57:07 |
| leona | ZHF started: https://github.com/NixOS/nixpkgs/issues/403336 | 15:11:58 |
| leona | let's actually mention this in #dev:nixos.org too, then i got almost every place i think :D | 15:12:34 |
 raf | I've created https://github.com/NixOS/nixpkgs/pull/403348 (in response to the discourse post)
This gets the obvious typos out of the way, but I'll revise the documentation in full again to clarify word where/if necessary. Also taking a look at the nixpkgs document now. | 16:16:50 |
|  Rosario Pulella changed their display name from Rosario Pulella to Rosuavio. | 20:09:35 |
| 3 May 2025 |
|  @rottenfishbone:matrix.org joined the room. | 21:01:37 |
| @rottenfishbone:matrix.org left the room. | 21:02:24 |
| 5 May 2025 |
| Grimmauld (any/all) | https://github.com/NixOS/nixpkgs/pull/402260#issuecomment-2833434789
https://github.com/NixOS/nixpkgs/pull/404303#pullrequestreview-2814080230
So uh - dropping ~10 years unmaintained leaf packages during freeze, yay or nay? | 08:15:48 |
 Alyssa Ross | In the past we haven't considered package removals to be breaking changes as I remember | 08:42:52 |
| leona | leaf package removals are okay | 08:43:21 |
| leona | espacially when they were already broken before | 08:43:44 |
| Alyssa Ross | It's not going to have unintended breaking consequences, which is the reason for the freeze. | 08:43:50 |
| Grimmauld (any/all) | Alright, thanks for the clarification 👍️ | 08:46:55 |
|  misuzu joined the room. | 12:14:09 |
|  @federicodschonborn:matrix.org changed their display name from This legally distinct plastic brick is licensed under the terms of the he/him or they/them pronouns, at your choice to This LEGO© Worm™ is licensed under the terms of the he/him or they/them pronouns, at your choice. | 20:48:46 |
