I'm glad it worked for you including the SVN component. The issue, as mentioned in the Apache error log, seems to be related to the APR-utils version included on your system and used by the subversion binary at
Please find below a longer explanation of your issue and one alternative solution you can try.
The APR-utils library installed on your system and used by the
/usr/bin/svn binary is different than the one that Apache is using. Because of that, Apache is giving errors of undefined symbols.
On the other hand, our subversion binary at
INSTALLDIR/subversion/bin/svn is using the same APR-utils library version than Apache because we build all the included components together to ensure they will work properly.
I think you can try to modify the APR-utils libraries on your system to match the libraries on our installation and in that case, you could continue using the
/usr/bin/svn binary, but note changing those libraries may break other components on your system and that we do not recommend you to do it. That's why we bring all the components in our installation, so they can be used out of the box and to ensure they won't break the host system.
As an alternative to having two different subversion servers in the same machine, you can continue using the Subversion component on the Bitnami installation and configuring Redmine to use an SVN repository in a remote machine. Please note this will require further configuration on your SVN server so your repositories can be remotely accessible.
The versions of the APR-utils dependencies used by
/usr/bin/svn are not compatible with the Apache binary, that was compiled against our own APR-utils versions. And the same for our SVN binaries at
I launched an AWS Ubuntu Eoan 19.10 (AMI ID:
ami-08861fc83ad3ad16a) and manually installed subversion on it. You can check the version of the APR-utils library being used by the system
svn binary running the command
ldd as shown below. I post here my results for more information
$ ldd /usr/bin/svn | grep -i "apr"
libapr-1.so.0 => /lib/x86_64-linux-gnu/libapr-1.so.0 (0x00007f60f2789000)
libaprutil-1.so.0 => /lib/x86_64-linux-gnu/libaprutil-1.so.0 (0x00007f60f2547000)
Which points the
apr libraries to versions
$ ls -lart /lib/x86_64-linux-gnu/libaprutil-1.so.0 /lib/x86_64-linux-gnu/libapr-1.so.0
lrwxrwxrwx 1 root root 17 Nov 19 2018 /lib/x86_64-linux-gnu/libapr-1.so.0 -> libapr-1.so.0.6.5
lrwxrwxrwx 1 root root 21 Aug 12 01:59 /lib/x86_64-linux-gnu/libaprutil-1.so.0 -> libaprutil-1.so.0.6.1
- For the Bitnami binaries, you get, once you have loaded the Bitnami environment used by the final binaries with the first command below:
# Load the binaries environment
$ source INSTALLDIR/scripts/setenv.sh
# Check libraries used by subversion
$ ldd INSTALLDIR/subversion/bin/.svn.bin | grep -i apr
libaprutil-1.so.0 => INSTALLDIR/common/lib/libaprutil-1.so.0 (0x00007fad5d892000)
libapr-1.so.0 => INSTALLDIR/common/lib/libapr-1.so.0 (0x00007fad5d12e000)
INSTALLDIR is a placeholder to your installation directory. Now, if you check the APR-utils libraries in use, they point to versions
0.6.0 respectively, which are different from the version in your system.
$ ls -lart INSTALLDIR/common/lib/libaprutil-1.so.0 INSTALLDIR/common/lib/libapr-1.so.0
lrwxrwxrwx 1 ubuntu ubuntu 17 Jan 10 12:30 INSTALLDIR/common/lib/libapr-1.so.0 -> libapr-1.so.0.6.2
lrwxrwxrwx 1 ubuntu ubuntu 21 Jan 10 12:29 INSTALLDIR/common/lib/libaprutil-1.so.0 -> libaprutil-1.so.0.6.0
If you also check the APR-utils library used by Apache, you will see it uses the same libraries version than our subversion binary.
$ ldd apache2/bin/httpd.bin | grep -i apr
libaprutil-1.so.0 => INSTALLDIR/common/lib/libaprutil-1.so.0 (0x00007f06e9a01000)
libapr-1.so.0 => INSTALLDIR/common/lib/libapr-1.so.0 (0x00007f06e929d000)
The different versions used by the Bitnami Apache binary and the subversion from the system causes the issues you are getting in the Apache error log file and that Redmine can't use the
Hope it helps,