| 15 Dec 2025 |
 Fabián Heredia | * Re: short 25.11-analog staging-next for unstable
I think the only high >= severity security fix would be libpng and others would be delayed like glib which probably has more usage)
If that short staging-next cycle would be about a couple of days the next staging-next cycle would start around holidays (navidad + new year in my case) and I would rather do any pending gcc fixes before then to have less to think about during winter holidays xd | 19:58:47 |
| Fabián Heredia | * Re: short 25.11-analog staging-next for unstable
I think the only high >= severity security fix would be libpng (and others would be delayed like glib which probably has more usage)
If that short staging-next cycle would be about a couple of days the next staging-next cycle would start around holidays (navidad + new year in my case) and I would rather do any pending gcc fixes before then to have less to think about during winter holidays xd | 19:58:58 |
 Grimmauld (any/all) | i'll be doing more nix again starting next week | 20:34:16 |
| Grimmauld (any/all) | i can pick up some of the gcc fallout, but not all of course | 20:34:43 |
 ghpzin | Do we know that fallout better than results from last run of jobset ?
Unfortunately top 15 deps on last eval were 12631 out of 13188 failures, so it is hard to measure what is in there. | 20:52:04 |
| Fabián Heredia | it was a single shot to fix some of the most prominent fallout but doing other evals would be expensive and no show stoppers appeared on that attempt so now it would be more on the normal staging-next cycle side | 20:53:33 |
| ghpzin | Okay, just checking maybe there is some better list I am not aware of. | 20:54:28 |
| ghpzin | * Okay, just checking maybe there is some better list I am not aware of.
I will maybe try to build it in chunks on top of master with gcc15 and fixes, to see if something important in there is still broken. | 21:00:16 |
| ghpzin | * Okay, just checking maybe there is some better list I am not aware of.
I will try to build it in chunks on top of master with gcc15 and fixes, to see if something important in there is still broken. | 21:13:28 |
| Grimmauld (any/all) | someone should build bootstrap tools with gcc 15 | 21:18:09 |
| Grimmauld (any/all) | thats the one i am worried about most rn | 21:18:16 |
| Grimmauld (any/all) | everything else should be fixable during a staging cycle | 21:18:27 |
| Fabián Heredia | I can do that now if it is a concern, could you give me the attr? | 21:18:44 |
| Grimmauld (any/all) | sec | 21:18:55 |
 vcunat | Like this build? https://hydra.nixos.org/build/315259025 | 21:23:14 |
| Grimmauld (any/all) | nom build -f pkgs/stdenv/linux/make-bootstrap-tools.nix bootstrapTools.all | 21:23:44 |
| Grimmauld (any/all) | but i guess if test passed thats good enough? | 21:23:58 |
| vcunat | musl bootstrap was broken in that Hydra eval. | 21:24:14 |
| vcunat | * musl bootstrap was broken in that Hydra eval. | 21:24:47 |
| Grimmauld (any/all) | i hate the combination where you need both attr path and file path | 21:25:03 |
| ghpzin | musl is known, needs updating. | 21:25:10 |
| Grimmauld (any/all) | never can remember those | 21:25:12 |
| Fabián Heredia | x2 | 21:25:59 |
| vcunat | If you know a Hydra job, it's easy. | 21:26:02 |
| ghpzin | * musl is known, need updating. | 21:26:06 |
| Grimmauld (any/all) | hydra isn't any easier to search than my shell history | 21:26:29 |
| ghpzin | * musl is known, need bootsrap update. | 21:26:31 |
| Fabián Heredia | searched nom and hadn't used it before. As a double check is it https://github.com/maralorn/nix-output-monitor? (Looks really nice :3) | 21:27:33 |
| vcunat | Yes, that's the thing. | 21:28:11 |
| Grimmauld (any/all) | nix would do the same thing, but i like pretty output | 21:28:29 |
