aboutsummaryrefslogtreecommitdiffstats
path: root/pkgs/by-name/st (unfollow)
Commit message (Collapse)Author
2025-06-07pkgs/stalwart-mail-patched/update.sh: Avoid building the outputBenedikt Peetz
We already have the nixos tests, that will fail, if this does not build.
2025-06-07pkgs/stalwart-mail-patched: Actually apply overridesBenedikt Peetz
The previous code silently dropped the overrides.
2025-06-07pkgs/stalwart-mail-patched/spamfilter: Provide infrastructure to update itBenedikt Peetz
Otherwise, this package will never be updated.
2025-06-07pkgs/stalwart-mail-patched: Use different native-ca-roots patchBenedikt Peetz
My patch was no longer working, as it was written against an older version of stalwart. This patch is now sourced directly from a GitHub pr, that was closed at the 21st of may. Upstream says, that they will support that in a future version, but I am honestly just waiting for the rug pull at this point. They are no longer accepting PRs, focusing more and more on new features, whilst the actual software is still very difficult to debug. But, with all this said, their current source code is available under the AGPL, so even if they rug pull (which might be difficult, due to fact, that their CLA is from the FSFE), a base for forking still persists.
2025-06-06pkgs/stalwart-mail: Update to nixos 25.05Benedikt Peetz
Now the stalwart-mail package is by default free. As such, we could drop the respective patches.
2025-04-23pkgs/stalwart-mail-free: Update package hash, as it changedBenedikt Peetz
This has to do with the underlying stalwart-mail update.
2025-03-09pkgs/stalwart-mail-free: Avoid running `stalwart-mail`'s testsBenedikt Peetz
2025-03-09pkgs/stalwart-mail-free: Update `cargoHash`Benedikt Peetz
2025-03-09pkgs/stalwart-mail-free: Also patch to use the platform CA storeBenedikt Peetz
This is needed for the test. The general changes are caused by the requirement to update the `chargoHash`, which currently only works with this counter intuitive attribute overriding.
2025-03-09modules/stalwart-mail: Move the package to the `pkgs` subtreeBenedikt Peetz