Created attachment 265393 [details] stalwart 0.14.1 The attached patch updates mail/stalwart to version 0.14.1. https://github.com/stalwartlabs/stalwart/releases/tag/v0.14.0 https://github.com/stalwartlabs/stalwart/releases/tag/v0.14.1 As ring 0.16.20 is no longer needed can we now remove NOT_FOR_ARCHS*? That's what the OpenBSD folks did. My poudriere build is still running. Btw. is there a reason why there is no stalwart (0.13.4) package available yet?
Unfortunately, stalwart 0.14.0 and 0.14.1 do not build if S3=on.
stalwart 0.14.1 (S3=on) compiles with rust 1.90.0.
LGTM. I see that ring 0.16.20 has already disappeared from the list of crates. In theory, we should indeed be able to remove NOT_FOR_ARCHS. Also there is truly no stalwart-related build information showing up on FreshPorts or PortFallout, which is strange...
I noticed an ERROR in the pkg-message section: “WARNING: The FreshPorts parser failed. ucl_tool failed. Please report this.” The pkg-message you pushed (https://github.com/freebsd/freebsd-ports/blob/main/mail/stalwart/pkg-message) is missing an EOM at the end.
(In reply to Orville Q. Song from comment #4) Sorry, not you. It was Mark Felder (feld@FreeBSD.org ) who modified the pkg-message and eventually pushed this port into the ports tree. I misremembered that. I'll provide a patch to address this issue later.
There is a typo: -BACKEND_DESC= Database and storage backends +BACKENDS_DESC= Database and storage backends
Created attachment 265981 [details] mail/stalwart 0.14.1 with EOM fix
Created attachment 265982 [details] mail/stalwart 0.14.1 with EOM&NOT_FOR_ARCH&typo fix
(In reply to Orville Q. Song from comment #3) I think S3 should be removed from OPTIONS_DEFAULT and marked broken. https://github.com/durch/rust-s3/issues/440
(In reply to Herbert J. Skuhra from comment #9) This might be a viable solution, especially since no package has made it into pkg yet, so there is basically no need to consider upgrades for existing users. Unfortunately, I am currently at the hospital with my father and do not have time to run the relevant tests; I probably will not be free until at least next week. If you would be willing to adjust the S3 feature flags and write an upgrade notice from the current version to 0.14.1, I would greatly appreciate it. Or I can pick this up and continue the follow-up work once I have time.
Additionally, I saw in https://github.com/stalwartlabs/stalwart/discussions/2312 that someone added elastic to the feature flags, after which S3 was able to compile successfully. I have not tried this myself yet, but it may be another possible approach.
Created attachment 266628 [details] mail/stalwart 0.15.3 Hi all, here's a patch that brings it up to 0.15.3 which the release notes also mention that it will correctly migrate the database schemas from 0.13.4. It's unclear if they do migrate their "breaking" changes for 0.14.x; I haven't been able to get a clear answer on that. This includes the EOM fix, the typo, and the removal of the NOT_FOR_ARCHES I am not getting any build errors with the S3 option being left enabled. I'm currently running this version without any issues. I'd like to get a confirmation from another user that this is working for them as well, and a sign off from Orville.
I want to clarify my last comment: I mean that I'm not certain if the 0.14.3 update correctly handles the changes since 0.13.x, so going straight to 0.15.3 should be safer based on those release notes and the 0.15.1 tag notes https://github.com/stalwartlabs/stalwart/blob/main/UPGRADING/v0_15.md https://github.com/stalwartlabs/stalwart/releases/tag/v0.15.1
The patch looks great to me, will run a test build later.
*** Bug 292465 has been marked as a duplicate of this bug. ***
Hi Orville, just checking in again to see if you were able to test it.
Created attachment 267331 [details] stalwart 0.15.4 Stalwart 0.15.4 released (2026-01-19): https://github.com/stalwartlabs/stalwart/releases/tag/v0.15.4
Sorry for the wait, I'm now running the test build of 0.15.4. Since my father is still undergoing treatment and needs care, I'm unable to devote enough time in the near future to maintain this package. I would like to ask Herbert J. Skuhra or Mark Felder, or anyone else, whether you would be willing to take over the role of maintainer. Thank you.
Comment on attachment 267331 [details] stalwart 0.15.4 [patch] stalwart 0.15.4 Tested with no problem, good to merge.
(In reply to Herbert J. Skuhra from comment #17) Stalwart 0.15.4 doesn't build with Rust 1.93.0: https://github.com/stalwartlabs/stalwart/discussions/2757
Created attachment 268062 [details] stalwart 0.15.5 Stalwart 0.15.5 released: https://github.com/stalwartlabs/stalwart/releases/tag/v0.15.5
(In reply to Herbert J. Skuhra from comment #21) Btw. this version builds with Rust 1.93.x.
LGTM. Now running the build test.
There is a security advisory for the Stalwart version in ports: https://github.com/stalwartlabs/stalwart/security/advisories/GHSA-jm95-876q-c9gw
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=61feef1538971887a52e58e5eab2c1da0926c712 commit 61feef1538971887a52e58e5eab2c1da0926c712 Author: Mark Felder <feld@FreeBSD.org> AuthorDate: 2026-03-03 00:13:45 +0000 Commit: Mark Felder <feld@FreeBSD.org> CommitDate: 2026-03-03 00:14:39 +0000 mail/stalwart: Update to 0.15.5 PR: 290995 mail/stalwart/Makefile | 7 +- mail/stalwart/Makefile.crates | 597 ++++++++++---------- mail/stalwart/distinfo | 1200 ++++++++++++++++++++--------------------- mail/stalwart/pkg-message | 1 + 4 files changed, 873 insertions(+), 932 deletions(-)