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.