Hi Bruno,
This problem should be covered in the readme-linux.txt file in the root directory of the SmartSVN bundle.
--
Best regards,
Thomas Singer
syntevo GmbH
https://www.syntevo.com
> *Research:*
>
> - SmartSVN extracts libsvnjavahl-1.so into
> ~/.config/smartsvn/14.5/svn-tmp/ at startup.
> - The bundled JavaHL is linked against SQLite 3.40, but the system
> SQLite on RHEL 9.3 is 3.34.
> - SmartSVN loads this .so via an absolute path, bypassing
> LD_LIBRARY_PATH, so users cannot easily override or disable it.
> - The GUI no longer offers an SVNKit/JavaHL selection, so users are
> forced into JavaHL even if it fails.
>
>
>
> *Impact:*SmartSVN starts normally, but all JavaHL-based operations (e.g.,
> opening a WC, checkout) fail on systems with older SQLite, making the
> client unusable for repository work.
>
>
> *Suggested actions:*
>
> - Provide a GUI option to force SVNKit as the backend.
> - Respect an environment variable (e.g., SMARTSVN_JAVAHL_DISABLE) to
> disable JavaHL.
> - Bundle JavaHL with a matching SQLite, or statically link SQLite to
> avoid system dependency issues.
>
>
>
> *Temporary workaround:*Use a wrapper script that deletes libsvnjavahl-1.so
> immediately after extraction so SmartSVN falls back to SVNKit. This works
> but is fragile since the svn-tmp folder is regenerated each launch.
>
> Thank you for reviewing this issue.
>
> Best regards,
> --
> Bruno Antunes
>
> --
> You received this message because you are subscribed to the Google Groups
> "SmartSVN" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
>
smartsvn+u...@googlegroups.com.
> To view this discussion visit
>
https://groups.google.com/d/msgid/smartsvn/CAA%3DPnK-YK2hCRAiRkMEpjFW78cv1rpw-VDx_9Z0%3Dnrv3%3DgspXg%40mail.gmail.com.
>