mariadb-10.6 @10.6.5_1: mariadb-10.6 cannot be built while openssl is active

[FaradayLight (Faraday Light)]

I do not know if this should be considered a bug or not given that there is a warning given with regards to how to address, but it results in an error. Therefore, for the record:

--->  Configuring mariadb-10.6
Error: mariadb-10.6 cannot be built while openssl is active.
Error: Please forcibly deactivate openssl, e.g. by running:
Error: 
Error:     sudo port -f deactivate openssl
Error: 
Error: Then try again. You can reactivate openssl again later.
Error: Failed to configure mariadb-10.6: openssl is active
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mariadb-10.6/mariadb-10.6/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
ERROR: Update of ports failed with exit code: 1
cicero@faraday ~ % vi /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_databases_mariadb-10.6/mariadb-10.6/main.log

[michaelld (Michael Dickens)]

I think that the broader issues is that MariaDB is not compatible with OpenSSL3, and will opportunistically link against any OpenSSL that it finds. Thus, we need to be specific in not providing opportunistic linking options, and that's what this deactivation requirement forces. Some day this hopefully won't be required, but until then, it's a feature, not a bug.

[FaradayLight (Faraday Light)]

OK, thanks.

[ryandesign (Ryan Carsten Schmidt)]

It is a bug. Whether we choose to fix it or not is the question.