| 13 May 2026 |
 vcunat | And doing that... you can pull it out of the big jobset as well in the same way. | 16:54:26 |
 hexa | doing it on staging will make it trickle through the branches organically | 16:54:35 |
 emily | I already have a PR for that | 16:54:40 |
| emily | my open PRs PRs cover the general release files, CI, etc. | 16:54:47 |
| hexa | diff --git a/pkgs/top-level/release-supported-systems.json b/pkgs/top-level/release-supported-systems.json
index 44c18f1abf0e..c8dd96072651 100644
--- a/pkgs/top-level/release-supported-systems.json
+++ b/pkgs/top-level/release-supported-systems.json
@@ -2,5 +2,4 @@
"aarch64-linux",
"aarch64-darwin",
"x86_64-linux",
- "x86_64-darwin"
]
| 16:54:56 |
| hexa | I want that in staging asap | 16:55:00 |
| emily | but I need to do channel scripts and fix more regressions/fallout from dropping it | 16:55:00 |
| hexa | if you have it | 16:55:04 |
| emily | I would really prefer to land it once it won't break everything | 16:55:19 |
| vcunat | Hmm, it's only easy for the small jobset which only pulls stdenvs, yeah. | 16:55:55 |
| hexa | and I would prefer wasting less compute cycles for when we have to support three releases | 16:55:58 |
| emily | I can get those changes ready on a few days' notice but I am just trying to manage my time. I do not want to land something that will break the world before I have the fixes pushed out | 16:56:03 |
| emily | like I said, I can have it ready for the upcoming -next | 16:56:18 |
| hexa | ok | 16:56:27 |
| emily | overriding it on Hydra for the staging jobset specifically for now seems like the right fix until then? | 16:56:32 |
| emily | nothing else will be wasting cycles on x86_64-darwin | 16:56:48 |
| hexa | https://hydra.nixos.org/jobset/nixpkgs/staging#tabs-configuration done | 16:57:40 |
| vcunat | I suppose. But you know... on nixpkgs side we deduplicated that list and then we override it on a remote place per-jobset... | 16:58:17 |
| vcunat | but that's of little practical significance anyway. | 16:58:48 |
| hexa | the per jobset thing is a stopgap for now | 16:58:51 |
| hexa | I think that's a fair compromise | 16:59:16 |
| vcunat | Yes, just easily forgotten. | 16:59:38 |
| vcunat | But the list is very static anyway. | 16:59:53 |
| hexa | doesn't matter for staging, does it? | 16:59:56 |
| emily | I can remind about the override if I'm reminded about the -next :) | 17:00:11 |
| emily | but yeah, this stuff changes very little | 17:00:21 |
| emily | as I discovered by how much needs fixing if you remove anything | 17:00:26 |
| emily | it will require a bit of a dance with nixpkgs-ci | 17:00:37 |
| emily | as you need to merge changes to make CI not block on the platform and then merge changes dropping it etc. | 17:00:50 |
| emily | there's like a 3-PR sequence that has to land in order | 17:01:02 |
