Now, if you check the APR-utils libraries in use, they point to versions 0.6.2 and 0.6.0 respectively, which are different from the version in your system. Note INSTALLDIR is a placeholder to your installation directory. $ ldd INSTALLDIR/subversion/bin/.svn.bin | grep -i apr For the Bitnami binaries, you get, once you have loaded the Bitnami environment used by the final binaries with the first command below:.Which points the apr libraries to versions 0.6.5 and 0.6.1 respectively: $ ls -lart /lib/x86_64-linux-gnu/libaprutil-1.so.0 /lib/x86_64-linux-gnu/libapr-1.so.0 I post here my results for more information 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 launched an AWS Ubuntu Eoan 19.10 (AMI ID: ami-08861fc83ad3ad16a) and manually installed subversion on it. And the same for our SVN binaries at installdir/subversion/bin/svn. 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. Please note this will require further configuration on your SVN server so your repositories can be remotely accessible. 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.Īs 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. 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. 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. Because of that, Apache is giving errors of undefined symbols. 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. Please find below a longer explanation of your issue and one alternative solution you can try. 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 /usr/bin/svn. Hi glad it worked for you including the SVN component. Note the three slashes at the beginning of the path after file: at /repositories/my-repo, you will need to configure set it in Redmine with file:///repositories/my-repo. If the repository is in the same server, i.e. I’m linking below our guide for configuring SVN repositories in Redmine just in case it is of help for you Can you try uninstalling the stack and installing it again but selecting both components? After that, try to configure a SVN repo again. This can be related to using the libsvn_subr-1.so.1 library from the system instead of using the one bundled in the Bitnami installation. Can you tell us which changes did you perform on your server to configure your SVN binary in Redmine? I can’t see any change in the bnsupport bundle.Īlso, according to the Apache error log, it looks like Redmine is having some issues trying to properly detect and use the SVN binary App 20449 output: svn: symbol lookup error: /lib/x86_64-linux-gnu/libsvn_subr-1.so.1: undefined symbol: apr_crypto_block_cleanup
0 kommentar(er)
