Subversion is toast on my current system complaining about gdbm despite having just executed:
resulting in:
Any clues on how to get subversion to point to libgdbm.so.4 instead of libgdbm.so.3? Subversion error below:
sudo portmaster -r gdbm
resulting in:
Code:
===>>> The following actions were performed:
Re-installation of gdbm-1.9.1
Re-installation of apr-ipv6-devrandom-gdbm-db42-1.4.5.1.3.12_1
Re-installation of apache-2.2.22_5
Re-installation of ap22-mod_macro-1.1.11
Re-installation of ap22-mod_python-3.3.1_3
Re-installation of subversion-1.7.3
Any clues on how to get subversion to point to libgdbm.so.4 instead of libgdbm.so.3? Subversion error below:
Code:
/libexec/ld-elf.so.1: Shared object "libgdbm.so.3" not found, required by "svnserve"
svn: E210002: Commit failed (details follow):
svn: E210002: Unable to connect to a repository at URL 'svn+ssh://svn.example.com/usr/local/example/svn/example/trunk'
svn: E210002: To better debug SSH connection problems, remove the -q option from 'ssh' in the [tunnels] section of your Subversion configuration file.
svn: E210002: Network connection closed unexpectedly
svn: E210002: Your commit message was left in a temporary file:
svn: E210002: '/usr/local/example/svn-commit.7.tmp'