services.mysql when used with mysql84 or percona-server now only allow socket-peer authentication for the super-user by default and try to adjust existing deployments.
Users can opt-out from this behavior by setting services.mysql.secureSuperUserByDefault = false;
More information can be found in the security advisory: `services.mysql` is configured with insecure authentication by default when used with `mysql` or `percona-server` · Advisory · NixOS/nixpkgs · GitHub
2 Likes
rhendric
Split this topic
September 19, 2026, 10:16pm
145
swiftPackages.swift is now a Swift toolchain. It is no longer wrapped. This is a breaking change , but it’s likely not one that most packages will notice.
NIX_SWIFTFLAGS_COMPILE is no longer supported (as a consequence of the above). If you need to pass flags to swiftc, add them per your package’s build system.
The Swift stdlib is now available as swiftPackages.stdlib. The stubs and modules have been removed from the Darwin SDKs. If you rely on the Swift modules from the SDK, you must get them from the stdlib package or the swift toolchain package.
Note: An additional breaking change is planned for the 6.4.0 update that will move the stubs from the top-level lib folder in swiftPackages.stdlib^dev to lib/swift/macosx. This is a correction of the new Swift packaging to better align it with upstream Swift toolchains.
staging ← reckenrode:swift-6.2-update
opened 03:42AM - 30 Aug 26 UTC
This has been a long time coming. I seem to have a knack for volunteering to do … big rewrites (the Darwin stdenv, the SDK, and now Swift). 😅
I apologize this took so long. As I [discussed](https://bsky.app/profile/winter.bsky.social/post/3mnd7luaotk2h) on Bluesky, it was a cycle of burnout and long cycles. However, it’s ready, and the foundation is set to make Swift easier to use in Nixpkgs and easier to update and maintain.
I want to thank everyone who joined https://matrix.to/#/%23nixpkgs-swift:matrix.org as well as here and on Discourse who tested, reviewed, and/or provided feedback (@jen20, @booxter, and others). I also want to thank and @lucasly-ba in particular for demonstrating that it is possible to build Swift from an usptream toolchain using a sysroot even if that turned out not to have the right set of trade-offs for building Swift in Nixpkgs.
## And now for the changes themselves …
This PR is a rewrite of the Swift packaging and an update of Swift to Swift 6.2.4. It replaces the single `compiler` derivation that builds LLVM and Swift together with several that build everything separately. The Swift LLVM fork leverages the LLVM packaging already done in Nixpkgs. The Swift bootstrap is now implemented in Nix. The stdlib has been split out into its own package. It should interact with Nixpkgs tooling much better than before.
For the most part, it is compatible with the old Swift packaging except as noted in the packaging changes listed below.
https://www.swift.org/blog/announcing-swift-6/
https://www.swift.org/blog/swift-6.1-released/
https://www.swift.org/blog/swift-6.2-released/
**Note:** This PR has a large number of changes because I wanted to land each part of the rewrite as it is needed, but I also did not want to break eval or existing builds. Until 0c7f9f2589960bd52ffcf4a1186c4fb907e50167, the default Swift is 5.10.1. I confirmed every commit evals using the following `jj run` invocation. It took a while, but it confirmed no evaluation errors. I confirmed that new packages built by doing `jj new <change-id>` and then manually `nix build`ing them.
$ jj run --jobs 4 --clean --root --ignore-changes -r staging@upstream..swift-6.2-update -- nix-build ci -A eval.baseline --no-out-link --arg evalSystems '["aarch64-darwin" "aarch64-linux" "x86_64-linux"]' --system x86_64-linux
## Changes to packaging
- `swiftPackages.swift` is now a Swift toolchain. It is no longer wrapped. This is a **breaking change**, but it’s likely not one that most packages will notice.
- `swiftPackages.swift` now has (more) tests. Yay, tests!
- Packages for `Dispatch`, `Foundation`, and `XCTest` have been moved to their upstream names. The old names are available as aliases. Cleanup was done to prevent warnings (and eval failures in CI) in Nixpkgs.
- The Swift stdlib is now available as `swiftPackages.stdlib`. The stubs and modules have been removed from the Darwin SDKs. To build Swift applications, you must use the stdlib package, which is part of the toolchain.
- It is no longer necessary to use a custom `stdenv` when building Swift packages. This was a common footgun. The default `stdenv` will just work because Swift finds and uses `clang` in the toolchain.
- Swift is bootstrapped in Nix. This is because (as noted in the commit messages) the bootstrap build doesn’t work on Darwin, but it also prepares for using the Swift 6.2 compiler to bootstrap subsequent versions of Swift.
- A `fetchSwiftPMDeps` FOD has been added to make packaging Swift dependencies a lot easier. In most cases, you don’t have to do anything. Just add it to your package, and the dependencies will be made available.
Other than `age-plugin-se`, which used a custom vendoring method, I did not convert any packages outside of the Swift package set to use `fetchSwiftPMDeps`. `swiftpm2nix` is still supported and works. It was updated to use the same vendoring method as `fetchSwiftPMDeps`. Maintainers who would prefer to use `fetchSwiftPMDeps` can update their packages accordingly once this is merged.
## Limitations
- Cross-compilation is not implemented. It’s also not currently implemented, so this is not a regression.
- Some Darwin frameworks require macro dylibs shipped with Xcode. These are not available. Notable users are AppleIntelligence, Swift Data, and SwiftUI in the 27.0 SDK (not available yet in Nixpkgs, but it will be soon).
- I have included a patch to build libdispatch on Musl, but Swift assumes that Musl is static, which is not true in Nixpkgs. Work will be required to support Musl as a non-static platform.
## Future directions
- Once this is open, I plan to start working on the Swift 6.3.2 update (or Swift 6.4 if the release is out by then). It will leverage the Swift 6.2 compiler to bootstrap the new release.
- Packages that are independent of the compiler have update scripts. The toolchain does not have an updater. I will be adding it as part of the Swift 6.3.2 update.
- Cross-compilation needs to be implemented, which I want to use to support the WASM and Android SDKs.
- Determine whether https://github.com/NixOS/nixpkgs/issues/243681, https://github.com/NixOS/nixpkgs/issues/242779, and https://github.com/NixOS/nixpkgs/issues/331943 are still issues.
## Fixes/closes
- Fixes https://github.com/NixOS/nixpkgs/issues/311565
- Closes https://github.com/NixOS/nixpkgs/issues/343210
- Fixes https://github.com/NixOS/nixpkgs/issues/346866
- Fixes https://github.com/NixOS/nixpkgs/issues/379859
## Things done
- Built on platform:
- [x] x86_64-linux
- [ ] aarch64-linux
- [x] aarch64-darwin
- Tested, as applicable:
- [ ] [NixOS tests] in [nixos/tests].
- [x] [Package tests] at `passthru.tests`.
- [ ] Tests in [lib/tests] or [pkgs/test] for functions and "core" functionality.
- [ ] Ran `nixpkgs-review` on this PR. See [nixpkgs-review usage].
- [x] Tested basic functionality of all binary files, usually in `./result/bin/`.
- Nixpkgs Release Notes
- [x] Package update: when the change is major or breaking.
- NixOS Release Notes
- [ ] Module addition: when adding a new NixOS module.
- [ ] Module update: when the change is significant.
- [x] Fits [CONTRIBUTING.md], [pkgs/README.md], [maintainers/README.md] and other READMEs.
- [x] Follows the [automation/AI policy].
[NixOS tests]: https://nixos.org/manual/nixos/unstable/index.html#sec-nixos-tests
[Package tests]: https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#package-tests
[nixpkgs-review usage]: https://github.com/Mic92/nixpkgs-review#usage
[CONTRIBUTING.md]: https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md
[automation/AI policy]: https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#automationai-policy
[lib/tests]: https://github.com/NixOS/nixpkgs/blob/master/lib/tests
[maintainers/README.md]: https://github.com/NixOS/nixpkgs/blob/master/maintainers/README.md
[nixos/tests]: https://github.com/NixOS/nixpkgs/blob/master/nixos/tests
[pkgs/README.md]: https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md
[pkgs/test]: https://github.com/NixOS/nixpkgs/blob/master/pkgs/test
10 Likes
Ma27
October 4, 2026, 9:08am
147
When using Grafana with declarativePlugins, make sure to add grafanaPlugins.prometheus, grafanaPlugins.loki, grafanaPlugins.tempo as needed.
These weree previously builtin, but are now apps that are installed on startup. The location they’re installed to doesn’t have an effect when using declarativePlugins though.
See grafana: 13.1.6 -> 13.2.3 by Ma27 · Pull Request #569875 · NixOS/nixpkgs · GitHub
7 Likes
Massive breaking change that was snuck in with no release note or mitigation instructions: Reapply "nixos/wrappers: enforce target executable is ELF" by GrimmTheShrimp · Pull Request #570085 · NixOS/nixpkgs · GitHub
The title is self-explanatory, but to explain it more thoroughly, text-based programs/scripts can no longer be used in security.wrappers.*.source; instead it must be a binary (ELF).
For programs that end up being scripts due to makeWrapper, you can switch it out for makeBinaryWrapper and it should work immediately. However, if the program itself is a script, unfortunately you will need to rewrite the program into a compiled language (or find a suitable replacement).
11 Likes
A ZHF fix did a downgrade of libdb in perlPackages.BerkeleyDB for 26.05, which caused an unreported/unprotected on-disk format downgrade. In my case it caused postgrey to restart loop and queue mail because it could no longer open the, now too-new, database file.
opened 04:40PM - 23 Oct 26 UTC
0.kind: bug
### Nixpkgs version
- Stable (26.05)
### Describe the bug
ec077bf10c0e ("perl… Packages.BerkeleyDB: fix build by pinning to db4", #517349, part of ZHF #516381) switched `perlPackages.BerkeleyDB` from `pkgs.db` (5.3) to `pkgs.db4` (4.8) on **all** platforms. This shipped in 26.05.
The Hydra failure it fixed was aarch64-darwin only (https://hydra.nixos.org/build/327065767):
```
# : BDB2029 TAS: mutex initialize: No such file or directory
t/btree.t ...... Dubious, test returned 255
```
On x86_64-linux, BerkeleyDB 0.65 built against `pkgs.db` (db 5.3.28, perl 5.42.3, current release-26.05) passes the full test suite (`Files=35, Tests=1871 ... Result: PASS`).
Because db4 can't open environments written by db 5.3, the pin is effectively an on-disk format downgrade for existing Linux users, with no release note. After upgrading 25.11 → 26.05, `services.postgrey` crash-loops:
```
postgrey[359262]: ERROR: can't create DB environment: No such file or directory (dbdir: /var/postgrey uid/gid: 258,258)
systemd[1]: postgrey.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
```
With postgrey down, postfix's `check_policy_service unix:postgrey/socket` defers all inbound mail. Anything else that uses `perlPackages.BerkeleyDB` with persistent data is presumably affected the same way.
### Workaround
```nix
nixpkgs.overlays = [ (final: prev: {
postgrey = prev.postgrey.override {
perlPackages = prev.perlPackages // {
BerkeleyDB = prev.perlPackages.BerkeleyDB.overrideAttrs {
preConfigure = ''
echo "LIB = ${final.db.out}/lib" > config.in
echo "INCLUDE = ${final.db.dev}/include" >> config.in
'';
};
};
};
}) ];
```
### Steps to reproduce
1. Run `services.postgrey` on 25.11 so `/var/postgrey` gets populated (db 5.3).
2. Upgrade to 26.05.
3. `postgrey.service` fails as above. With an empty `/var/postgrey` it starts fine.
### Minimal reproducer
```nix
```
### Expected behaviour
Existing database files written in 25.11 should load on 26.05.
### Screenshots
_No response_
### Relevant log output
```console
Oct 23 10:07:02 liver systemd[1]: Starting Postfix Greylisting Service...
Oct 23 10:07:02 liver systemd[1]: Started Postfix Greylisting Service.
Oct 23 10:07:02 liver postgrey[359262]: Attempt to call undefined import method with arguments ("1.05") via package "IO::Multiplex" (Perhaps you forgot to load the package?) at
/nix/store/aglv1w2xs11hxysxqbkq293di22q8cya-perl5.42.3-Net-Server-2.014/lib/perl5/site_perl/5.42.3/Net/Server/Multiplex.pm line 26.
Oct 23 10:07:02 liver postgrey[359262]: Possible precedence problem between ! and string eq at
/nix/store/6vncjqmhdy5xx7qj9vabw0p9241dyjz5-perl5.42.3-BerkeleyDB-0.65/lib/perl5/site_perl/5.42.3/x86_64-linux-thread-multi/BerkeleyDB.pm line 829.
Oct 23 10:07:02 liver postgrey[359262]: Possible precedence problem between ! and string eq at
/nix/store/6vncjqmhdy5xx7qj9vabw0p9241dyjz5-perl5.42.3-BerkeleyDB-0.65/lib/perl5/site_perl/5.42.3/x86_64-linux-thread-multi/BerkeleyDB.pm line 997.
Oct 23 10:07:02 liver postgrey[359262]: 2026/10/23-10:07:02 postgrey (type Net::Server::Multiplex) starting! pid(359262)
Oct 23 10:07:02 liver postgrey[359262]: Binding to UNIX socket file "/var/lib/postfix/queue/postgrey/socket"
Oct 23 10:07:02 liver postgrey[359262]: Setting gid to "258 258"
Oct 23 10:07:02 liver postgrey[359262]: Setting uid to "258"
Oct 23 10:07:02 liver postgrey[359262]: ERROR: can't create DB environment: No such file or directory (dbdir: /var/postgrey uid/gid: 258,258)
```
### Additional context
_No response_
### System metadata
- system: `"x86_64-linux"`
- host os: `Linux 6.18.57, NixOS, 26.05 (Yarara), 26.05.20261020.cd4ea8d`
- multi-user?: `yes`
- sandbox: `yes`
- version: `nix-env (Nix) 2.34.9`
- nixpkgs: `/nix/store/x605rbj3d9bjxd3zdnqy0iphq7g6ly50-source`
### Notify maintainers
@iamanaws (author of #517349)
---
**Note for maintainers:** Please tag this issue in your pull request description. (i.e. `Resolves #ISSUE`.)
### I assert that this issue is relevant for Nixpkgs
- [x] I assert that this is a bug and not a support request.
- [x] I assert that this is not a [duplicate of an existing issue](https://github.com/NixOS/nixpkgs/issues?q=is%3Aissue+label%3A%220.kind%3A+bug%22+-label%3A%226.topic%3A+darwin%22+-label%3A%226.topic%3A+nixos%22).
- [x] I assert that I have read the [NixOS Code of Conduct](https://github.com/NixOS/.github/blob/master/CODE_OF_CONDUCT.md) and agree to abide by it.
- [x] I assert that I have read the [automation/AI policy](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#automationai-policy) and that this issue report complies with it.
### Is this issue important to you?
Add a :+1: [reaction] to [issues you find important].
[reaction]: https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/
[issues you find important]: https://github.com/NixOS/nixpkgs/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc
2 Likes
PR to add the restriction to release notes and module docs:
master ← trespaul:wrappers-elfs
opened 05:35PM - 23 Oct 26 UTC
#570085 requires wrappers to be ELFs (elves?) — it was pointed out (https://gith… ub.com/NixOS/nixpkgs/pull/567913#issuecomment-5880313062, https://github.com/NixOS/nixpkgs/pull/570085#issuecomment-6332105370, [@waffle8946 in the Discourse breaking changes topic](https://discourse.nixos.org/t/breaking-changes-announcement-for-unstable/17574/149)) that this is a breaking change which needs a release note.
I also added this to the module documentation so the restriction is surfaced in the reference docs when users are configuring a system.
## Things done
- [X] Fits [CONTRIBUTING.md], [pkgs/README.md], [maintainers/README.md] and other READMEs.
- [X] Follows the [automation/AI policy].
- Built on platform:
- [ ] x86_64-linux
- [ ] aarch64-linux
- [ ] aarch64-darwin
- Tested, as applicable:
- [ ] Basic functionality of all binary files, usually in `./result/bin/`.
- [ ] Ran `nixpkgs-review` on this PR. See [nixpkgs-review usage].
- [ ] [Package tests] at `passthru.tests`.
- [ ] [NixOS tests] in [nixos/tests].
- [ ] Tests in [lib/tests] or [pkgs/test] for functions and "core" functionality.
- Nixpkgs Release Notes
- [ ] Package update: when the change is major or breaking.
- NixOS Release Notes
- [ ] Module addition: when adding a new NixOS module.
- [X] Module update: when the change is significant.
[Package tests]: https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#package-tests
[NixOS tests]: https://nixos.org/manual/nixos/unstable/index.html#sec-nixos-tests
[nixpkgs-review usage]: https://github.com/Mic92/nixpkgs-review#usage
[CONTRIBUTING.md]: https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md
[automation/AI policy]: https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#automationai-policy
[lib/tests]: https://github.com/NixOS/nixpkgs/blob/master/lib/tests
[maintainers/README.md]: https://github.com/NixOS/nixpkgs/blob/master/maintainers/README.md
[nixos/tests]: https://github.com/NixOS/nixpkgs/blob/master/nixos/tests
[pkgs/README.md]: https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md
[pkgs/test]: https://github.com/NixOS/nixpkgs/blob/master/pkgs/test
3 Likes
Swift has been updated to Swift 6.4.0. SwiftPM now defaults to the Swift Build build system. This should be a mostly compatible change, but if your package depends on the layout of .build, you will have to update it to work with the new layout.
staging ← reckenrode:swift-6.4-update
opened 12:57PM - 14 Oct 26 UTC
Attempt number two. Previous attempt was https://github.com/NixOS/nixpkgs/pull/5… 73476. Trying to manage multiple base branches was causing a mess.
https://www.swift.org/blog/swift-6.4-released/
This PR is draft until I can sort out the C++ interop issue on Darwin. There were some dependent PRs (see the original), but they have been merged or included in this PR.
### Resolved issues
Fixes https://github.com/NixOS/nixpkgs/issues/242779
Fixes https://github.com/NixOS/nixpkgs/issues/331943
Fixes https://github.com/NixOS/nixpkgs/issues/570491
## Things done
- Built on platform:
- [x] x86_64-linux
- [ ] aarch64-linux
- [x] aarch64-darwin
- Tested, as applicable:
- [ ] [NixOS tests] in [nixos/tests].
- [ ] [Package tests] at `passthru.tests`.
- [ ] Tests in [lib/tests] or [pkgs/test] for functions and "core" functionality.
- [ ] Ran `nixpkgs-review` on this PR. See [nixpkgs-review usage].
- [x] Tested basic functionality of all binary files, usually in `./result/bin/`.
- Nixpkgs Release Notes
- [ ] Package update: when the change is major or breaking.
- NixOS Release Notes
- [ ] Module addition: when adding a new NixOS module.
- [ ] Module update: when the change is significant.
- [x] Fits [CONTRIBUTING.md], [pkgs/README.md], [maintainers/README.md] and other READMEs.
- [x] Follows the [automation/AI policy].
[NixOS tests]: https://nixos.org/manual/nixos/unstable/index.html#sec-nixos-tests
[Package tests]: https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#package-tests
[nixpkgs-review usage]: https://github.com/Mic92/nixpkgs-review#usage
[CONTRIBUTING.md]: https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md
[automation/AI policy]: https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#automationai-policy
[lib/tests]: https://github.com/NixOS/nixpkgs/blob/master/lib/tests
[maintainers/README.md]: https://github.com/NixOS/nixpkgs/blob/master/maintainers/README.md
[nixos/tests]: https://github.com/NixOS/nixpkgs/blob/master/nixos/tests
[pkgs/README.md]: https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md
[pkgs/test]: https://github.com/NixOS/nixpkgs/blob/master/pkgs/test
## Automation Disclosure
The previous was flagged by github-ci, but I did not use LLM assistance to prepare this PR nor did I use it to prepare any other of my PRs. I assume it was flagged due to the above-mentioned mess I made of the previous one.
10 Likes