nixos-server/pkgs/by-name/st, branch grocy-newnixos-config for vhack.eu servers https://vhack.euhttp://git.foss-syndicate.org/vhack.eu/nixos-server/atom?h=grocy-new2025-06-07T16:53:41+00:00pkgs/stalwart-mail-patched/update.sh: Avoid building the output2025-06-07T16:53:41+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-06-07T16:53:41+00:00urn:sha1:9c463d488d77b1434a9dca55038c1c9bad7cef09
We already have the nixos tests, that will fail, if this does not build.
pkgs/stalwart-mail-patched: Actually apply overrides2025-06-07T16:53:04+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-06-07T16:53:04+00:00urn:sha1:c042172d221fe43887ad1fcacd7689941d9f7903
The previous code silently dropped the overrides.
pkgs/stalwart-mail-patched/spamfilter: Provide infrastructure to update it2025-06-07T14:59:02+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-06-07T14:58:28+00:00urn:sha1:395d39c80c4281840755e54eec65bcf157eae509
Otherwise, this package will never be updated.
pkgs/stalwart-mail-patched: Use different native-ca-roots patch2025-06-07T14:50:57+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-06-07T14:50:57+00:00urn:sha1:f4388ee36cb7ce7af8d4a28aae7023ce65da953b
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.
pkgs/stalwart-mail: Update to nixos 25.052025-06-06T19:37:46+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-06-06T19:37:46+00:00urn:sha1:fccc098fa6d5636a6dad9a393414d7a1dfbac8ec
Now the stalwart-mail package is by default free. As such, we could drop
the respective patches.
pkgs/stalwart-mail-free: Update package hash, as it changed2025-04-23T08:06:09+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-04-22T20:26:54+00:00urn:sha1:10284fd90a2b8b8f44aa51f9224b9be626f6e5a1
This has to do with the underlying stalwart-mail update.
pkgs/stalwart-mail-free: Avoid running `stalwart-mail`'s tests2025-03-09T12:44:36+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-03-04T19:26:43+00:00urn:sha1:4ba09352dd1e04d6997ec1176fad908ba71f48a7pkgs/stalwart-mail-free: Update `cargoHash`2025-03-09T12:44:35+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-03-04T19:26:33+00:00urn:sha1:b0472a2a91d5204ca3aa25f43bc6a16bf5877a25pkgs/stalwart-mail-free: Also patch to use the platform CA store2025-03-09T12:44:23+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-03-04T18:21:22+00:00urn:sha1:80fab76532b5b159cf0c9c910387b1c09907be30
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.
modules/stalwart-mail: Move the package to the `pkgs` subtree2025-03-09T12:44:18+00:00Benedikt Peetzbenedikt.peetz@b-peetz.de2025-02-23T17:37:06+00:00urn:sha1:337afb96cb35fe525c851531fb04fd13989acbe5