Nix on macOS | 1174 Members | |
| “There are still many issues with the Darwin platform but most of it is quite usable.” — http://yves.gnu-darwin.org | 191 Servers |
| Sender | Message | Time |
|---|---|---|
| 2 Dec 2025 | ||
| you can work around it by manually creating the bundle | 01:13:14 | |
| not sure I follow, it is capped at some amount per backup or in total | 01:14:35 | |
| it's capped bc time machine uses bad settings to create the bundle | 01:14:58 | |
| so in total per machine | 01:15:17 | |
| oh ok | 01:15:38 | |
| well you shouldn't be having 16tb in a workstation regardless lol | 01:15:51 | |
| 1st world problems | 01:15:55 | |
| though yours is showing up as a time machine destination and not a normal SMB share, so i think you'd avoid this issue | 01:16:08 | |
| im not sure how you accomplished that, i tried some things and couldn't figure it out | 01:16:35 | |
| oh wait nvm, that's not the time machine icon | 01:16:49 | |
| the tahoe ones all look so similar... | 01:17:00 | |
| hmm I just did the avahi thing | 01:20:33 | |
| Swift Build requires the 15.x SDK because of course it does. 😞 | 01:33:16 | |
| 01:39:39 | |
*
| 01:39:49 | |
Great. The 15.5 SDK has the TaskLocal change. | 01:39:59 | |
| how is it defined in the 14.x SDK? | 01:52:07 | |
| https://github.com/swiftlang/swift/pull/70902#pullrequestreview-1833189110 | 01:53:17 | |
| fwiw, it looks like it was an issue for Android too. | 01:53:23 | |
| and it's now conditional https://github.com/swiftlang/swift/commit/8d67a3723146c417a1986febfb207d1fe962a0d8 | 01:54:11 | |
| perhaps a later version of the SDK will pick that up? | 01:54:19 | |
(maybe not, if the .swiftinterface is after that) | 01:55:46 | |
| It’s a property wrapper. They changed it to a macro in Swift 6.0. | 01:56:07 | |
| https://github.com/swiftlang/swift/blame/36a3c6e61101419f4557781da79f291445cdfa1b/stdlib/public/Concurrency/TaskLocal.swift#L17-L30 | 01:58:03 | |
| I wonder if building against the version of the libraries in the Swift sources rather than using the SDK for the bootstrap would solve it – since the conditional is there in the source. alternatively –
I wonder what happens if you just make these emit a warning rather than an error. | 01:58:18 | |
| (ofc, not a good long-term solution to patch like that, but it's something that we could go to upstream about) | 01:58:37 | |
The guard isn’t in the swiftinterface. Either Apple strips it from their SDK build, or it doesn’t get put in there. | 01:59:29 | |
yeah, I guess the guards are processed before generating the .swiftinterface. so making the compiler not immediately die when it sees a macro definition, and avoiding the .swiftinterfaces in favour of the source code when bootstrapping, are the two options there. | 02:00:25 | |
| That works for Concurrency, but it doesn’t work for Foundation. | 02:00:34 | |
| well, they do have their FOSS Foundation, right? but yeah, making the macro definitions not immediately kill it seems like the easier thing to try. | 02:01:25 | |