| 23 Dec 2025 |
 Randy Eckenrode | $ nix build -f . swiftPackages.swift-format
$ result/bin/swift-format --version
6.2.3
| 03:37:31 |
| Randy Eckenrode | That’s with the hook vendoring the packages from nixpkgs and propagating swift-corelibs-xctest automatically from swift. | 03:37:56 |
| Randy Eckenrode | {
lib,
fetchFromGitHub,
mkSwiftPackage,
swift-argument-parser,
swift-markdown,
swift-syntax,
stdenv,
swift_release,
}:
mkSwiftPackage (finalAttrs: {
pname = "swift-format";
version = swift_release;
src = fetchFromGitHub {
owner = "swiftlang";
repo = "swift-format";
tag = "swift-${finalAttrs.version}-RELEASE";
hash = "sha256-DhTtGU2B9BIyN6PyLBlg7kIs3cVyRl6Pa9G0txzta0g=";
};
postPatch =
# Fix the deployment target or compiling code using XCTest fails.
lib.optionalString stdenv.hostPlatform.isDarwin ''
substituteInPlace Package.swift \
--replace-fail '.macOS("13.0")' ".macOS(\"$MACOSX_DEPLOYMENT_TARGET\")"
'';
buildInputs = [
swift-argument-parser
swift-markdown
swift-syntax
];
})
| 03:39:01 |
 Katalin 🔪 | cool! | 03:39:21 |
| Randy Eckenrode | swift package edit lets me handle vendoring in a better way than what we were doing before. | 03:39:52 |
| Randy Eckenrode | The inputs are just source packages. With traits, I don’t think we can reliably pre-compile dependencies. | 03:40:12 |
| Randy Eckenrode | (Even if we could fool SwiftPM into using them.) | 03:40:20 |
| Randy Eckenrode | Next is splitting out Swift Syntax from the compiler, so it looks like a normal package and works with SwiftPM’s special support for providing pre-built Swift Syntax binaries. | 03:41:21 |
| Katalin 🔪 | I'll have to test this with Meson at some point too | 03:42:35 |
| Katalin 🔪 | but I assume it'll just work | 03:43:00 |
| Randy Eckenrode | mkSwiftPackage is a helper that sets up packages to be consumable as inputs. | 03:43:48 |
| Randy Eckenrode | It’s not currently available outside of the Swift package set. | 03:44:13 |
| Randy Eckenrode | * mkSwiftPackage is a helper that sets up package sources to be consumable as inputs. | 03:44:31 |
| Katalin 🔪 | ah no, I mean your new swift changes in general. this one is swiftpm-specific (or at least, it won't work as-is with Meson subprojects) | 03:46:01 |
| Randy Eckenrode | Swift is still unwrapped. Meson may need help finding things. | 03:46:25 |
 K900 | @emilazy:matrix.org have you tested uncursed xorg yet | 08:22:44 |
| K900 | I kinda want to merge it before people start touching it again | 08:23:14 |
 WeetHet | Is python just broken on unstable or am I missing something | 11:39:18 |
| WeetHet | ❯ nix-shell -I nixpkgs=channel:nixpkgs-unstable -p "python3.withPackages (ps: [ ps.numpy ])"
this derivation will be built:
/nix/store/fsnqmdg1k6cvsvkb24h9bjcx1i3w80ci-python3-3.13.9-env.drv
building '/nix/store/fsnqmdg1k6cvsvkb24h9bjcx1i3w80ci-python3-3.13.9-env.drv'...
created 219 symlinks in user environment
[nix-shell:~]$ python
Python 3.13.9 (main, Oct 14 2025, 13:52:31) [Clang 21.1.2 ] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import numpy
Traceback (most recent call last):
File "<python-input-0>", line 1, in <module>
import numpy
ModuleNotFoundError: No module named 'numpy'
>>>
| 11:39:21 |
| K900 | I believe this is fixed on master | 11:49:59 |
 leona | this will be fixed with the next staging-next | 12:41:29 |
| leona | so yes, it's broken currently | 12:41:43 |
| leona | it's fixed on 25.11 | 12:41:55 |
 kdn | How do I make the external USB drives accessible to linux-builder? I'm getting permissions denied | 13:49:42 |
 emily | oh, I was waiting for the patches to be updated | 14:09:06 |
| K900 | Oh I was hoping you would do it | 14:14:02 |
| K900 | I do not understand or trust those patches | 14:14:10 |
| emily | well I showed that they were from an old release of XQuartz and that there is a newer branch of XQuartz that contains different patches but at least one of them was already upstreamed to Xorg | 14:16:15 |
| emily | and at least one of the patches we have currently is a hacky-looking revert that XQuartz hasn't shipped for years | 14:16:37 |
| emily | I don't really have the time but it should be pretty mechanical to check how many commits from the newest XQuartz tag haven't actually made it to an Xorg release since | 14:17:00 |
