Subversion client svn fails with openssl3.1

[MichaelJFischer]

Subversion client no longer works with repositories configurated to use sasl authentication.

> svn update
Updating '.':
svn: E170013: Unable to connect to a repository at URL 'svn://...'
svn: E170001: SASL authentication error: SASL(-1): generic failure: internal error: failed to init cipher 'rc4'

A fix is to rebuild openssl3 as suggested by ryandesign (Ryan Schmidt) in comment7 to ticket #67149:

sudo port upgrade --enforce-variants openssl3 +legacy

After the rebuild, svn works normally. The build script for svn should be changed to reflect that it needs the +legacy variant of openssl3.

[ryandesign (Ryan Carsten Schmidt)]

A port "can't" depend on a variant of another port (see #126). It can use the active_variants 1.1 portgroup, but that requires manual intervention from the user, and prevents the buildbot from automatically creating binary archives of the port.

Have you reported this problem to the developers of Subversion? If not, please do, and put the URL of the report here.

[MichaelJFischer]

Correspondence with subversion developer

[MichaelJFischer]

I reported the problem to the subversion developers. I received a very helpful reply from Daniel Sahlberg. I responded to his questions and have attached a copy of my response to this ticket. My conclusion is that this is not a subversion problem but one of attempting to build the subversion client against an incompatible library (openssl3). I believe that the MacPorts recipe for building subversion should be changed to require the cyrus-sasl2 library instead. I don't know enough about how MacPorts works to do it myself, but I'd be happy to test any proposed changes.