| 30 Oct 2025 |
 Fabián Heredia | I would say the time is always right. The policy is around other distros already using values as default and enabling hardware seems really reasonable.
Some time ago I made some effort to better compartamentalize the option by ISA so aarch64 specific stuff could be enabled on that platform easily. | 05:33:08 |
| Fabián Heredia | ah wait nvm, it was only power-management options | 05:38:16 |
| Fabián Heredia | https://github.com/NixOS/nixpkgs/pull/165547/commits/cc8456effe723a6489b6f89fdafa7e877245742d
Anyways, same idea, // optionalAttrs (platform)
| 05:38:42 |
| Fabián Heredia | I should also do a cleanup now that 5.4 was removed | 05:41:44 |
 j-k | I was in the middle of asking about the jobs here:
https://hydra.nixos.org/job/nixpkgs/trunk/unstable#tabs-constituents
But it looks like someone is going through and cancelling some of the old pending work | 10:27:46 |
| j-k | aggregate job 311452680 I believe in you 🙏 | 10:28:29 |
 Vladimír Čunát | If only trunk wouldn't commonly generate 10k rebuilt jobs daily (roughly). | 10:29:35 |
| Vladimír Čunát | Most of cancellations that you see are from
https://hydra.nixos.org/admin/clear-queue-non-current | 10:30:29 |
| j-k | does merge trains now help with that a bit? | 10:30:53 |
| j-k | * do merge trains now help with that a bit? | 10:30:58 |
| j-k | So it's this one I should be watching for staging -> master?
https://hydra.nixos.org/jobset/nixpkgs/staging | 10:31:05 |
| Vladimír Čunát | Merge queue is unrelated, I believe. | 10:31:15 |
| Vladimír Čunát | * Merge queue is unrelated, I believe. | 10:31:59 |
| Vladimír Čunát | What's your point? I'm honestly confused. | 10:33:02 |
| j-k | I'm just trying to identify/follow when go 1.25.3 will make it to master etc
https://github.com/NixOS/nixpkgs/blob/staging/pkgs/development/compilers/go/1.25.nix | 10:33:59 |
| Vladimír Čunát | That's like in two weeks hopefully. | 10:35:07 |
