!lheuhImcToQZYTQTuI:nixos.org

Nix on macOS

1168 Members
“There are still many issues with the Darwin platform but most of it is quite usable.” — http://yves.gnu-darwin.org191 Servers

Load older messages


SenderMessageTime
17 Feb 2026
@reckenrode:matrix.orgRandy EckenrodemacOS 26.4 is warning about Rosetta 2 use.00:42:26
@hexa:lossy.networkhexacool, let me accidentally update the build farm past that00:44:12
@hexa:lossy.networkhexa cool, let me accidentally update the build farm past that 00:44:16
@hexa:lossy.networkhexa26.05 is the final release with x86_64-darwin support, correct?00:44:42
@ihar.hrachyshka:matrix.orgIhar Hrachyshka

when users launch an app that uses Rosetta 2, there will be a popup letting them know that the app will no longer work when support for Rosetta 2 ends.

what will happen on headless? (do we ever run .apps during builds?)

01:06:42
@reckenrode:matrix.orgRandy EckenrodeThat’s the current plan. I’d like to remove support sooner rather than later in the cycle if possible.02:05:11
@sarahec:matrix.orgSarah ClarkUPDATE: I patched out the offending pragmas on Darwin04:40:12
@logn:zirco.devLogN changed their display name from Logan Devine to LogN.04:46:53
@spore:mozilla.orgSporeRedacted or Malformed Event05:46:02
@theutz:matrix.orgtheutz changed their profile picture.17:16:50
@theutz:matrix.orgtheutz changed their profile picture.17:17:37
@hexa:lossy.networkhexa to be fair, we can immediately remove x86_64-darwin builds on unstable after the release 23:25:34
@hexa:lossy.networkhexa* we can immediately remove x86_64-darwin builds on unstable after the release23:25:40
@hexa:lossy.networkhexawe could really use the capacity for aarch64-darwin23:25:49
@reckenrode:matrix.orgRandy EckenrodeI’d like to do the actual removal shortly in that timeframe as well.23:30:11
@reckenrode:matrix.orgRandy EckenrodeI think @emily has suggested we could keep it around if someone wants to do something with it, but I’d rather delete it so people can stop worrying about it.23:30:45
@reckenrode:matrix.orgRandy Eckenrode * I think emily has suggested we could keep it around if someone wants to do something with it, but I’d rather delete it so people can stop worrying about it. 23:31:00
@emilazy:matrix.orgemilyI remember us being on opposite sides of that 😅23:31:01
@reckenrode:matrix.orgRandy EckenrodeGlad I remembered correctly. 😂23:31:19
@emilazy:matrix.orgemily 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
@emilazy:matrix.orgemilyand I somewhat doubt anyone does want that23:31:32
@emilazy:matrix.orgemilyI would like to get an eval warning out for 26.05 though23:31:41
@emilazy:matrix.orgemilyjust so much to do :(23:31:45
@reckenrode:matrix.orgRandy EckenrodeThey can do that in their own fork like the LTS folks are doing AFAIK.23:32:22
@emilazy:matrix.orgemily 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:lossy.networkhexaso after 26.05 is branched we stop building into it?23:39:32
@emilazy:matrix.orgemilyit'll need to be built for 26.05 stable but yes23:39:45
@hexa:lossy.networkhexayes, and for 25.11 until EOL23:39:53
@hexa:lossy.networkhexabut not unstable, not staging-next23:39:59
@emilazy:matrix.orgemilyright23:40:05

There are no newer messages yet.


Back to Room ListRoom Version: 6