| 17 Feb 2026 |
 emily | I remember us being on opposite sides of that 😅 | 23:31:01 |
 Randy Eckenrode | Glad I remembered correctly. 😂 | 23:31:19 |
| emily | my position is that if someone wants to fund maintenance and infra then x86_64-darwin can stay until end of official support, otherwise yeet it | 23:31:27 |
| emily | and I somewhat doubt anyone does want that | 23:31:32 |
| emily | I would like to get an eval warning out for 26.05 though | 23:31:41 |
| emily | just so much to do :( | 23:31:45 |
| Randy Eckenrode | They can do that in their own fork like the LTS folks are doing AFAIK. | 23:32:22 |
| emily | if it resulted in a net overall effective increase in capacity and maintenance time for aarch64-darwin then it'd be fine to have it in-tree, but I doubt anyone has the funds for that, so it should just go | 23:36:13 |
 hexa | so after 26.05 is branched we stop building into it? | 23:39:32 |
| emily | it'll need to be built for 26.05 stable but yes | 23:39:45 |
| hexa | yes, and for 25.11 until EOL | 23:39:53 |
| hexa | but not unstable, not staging-next | 23:39:59 |
| emily | right | 23:40:05 |
| 18 Feb 2026 |
|  -> @n:rab.lol changed their display name from niko ⚡️ to -> @n:rab.lol. | 23:28:26 |
| 19 Feb 2026 |
| emily | FWIW: https://github.com/NixOS/nixpkgs/pull/492100 | 14:11:30 |
| emily | still need to do some work to get CI passing, and then I'll put up the draft PR for 26.11 that does the actual drop. (I also have, like, hundreds of treewide commits cleaning things up and fixing update scripts for the fallout of that, but they'll need cleaning up to be ready to send out even in draft form.) | 14:12:03 |
| Randy Eckenrode | The message suggests we will be keeping the platform definition but not building it. When do we get to delete it completely? | 14:28:49 |
| Randy Eckenrode | * | 14:29:04 |
| emily | does it imply that? I didn't intend to. I delete it in my commits that I'm going to push out | 14:30:29 |
| emily | you can --argstr system whatever you want to Nixpkgs, it just won't manage to bootstrap for most possible choices | 14:30:58 |
| emily | (do you mean the release notes? that's mostly from the copy I wrote for last release) | 14:37:45 |
| Randy Eckenrode | Yeah, the release notes. I can see someone interpreting, “we will no longer build packages for x86_64-darwin or guarantee that it can build at all,” that they can try anyway and fix what breaks on their own. | 14:40:10 |
| Randy Eckenrode | * Yeah, the release notes. I can see someone interpreting, “we will no longer build packages for x86_64-darwin or guarantee that it can build at all,” as they can try anyway and fix what breaks on their own. | 14:40:24 |
| emily | they can in their own tree :) | 14:45:55 |
| emily | I can look at adjusting the wording once I actually have things evaluating. | 14:46:21 |
| emily | you know you have a great patch stack going when squashing things into the first commits of it with Jujutsu is noticeably slow | 15:58:45 |
| emily | because it has to rebase the hundred commits after it | 15:58:54 |
| emily | Randy Eckenrode: do we have a plan for Wine, btw? I believe you said that x86 emulation on AArch64 didn't work on macOS upstream currently? | 16:01:06 |
| Randy Eckenrode | No plan at the moment. | 16:02:23 |
| Randy Eckenrode | It would be good to get Wine building on aarch64, so Linux users can use it with Fex, but Fex doesn’t work on Darwin AFAIK. | 16:03:01 |
