Quantcast
Channel: BitNami Answers - latest questions
Viewing all articles
Browse latest Browse all 2052

Subversion integration stops working after upgrading to 2.3.2 from 2.0.1.stable

$
0
0

Hi,

I had Redmine v2.0.1.stable running and working fully on OSX 10.8.4 using the Bitnami Stack. It was setup to link to an external SVN repository.

After upgrading to the v2.3.2 stack the SVN integration now fails. I've done some digging to try and track down the issue without great success: - I first tried the standard recommendations (disabling plugins, manually setting the full path to the SVN binary) - I added debug commands to the subversion_adapter.rb to log the commands being issued and the reponses - The SVN command being run was correct but no output was generated - I hardcoding the command (into scm_version_from_command_line) but without success - As a test I added temporarily made it run a few other different executables (eg. which, uuconv) - The other executables ran without issue and the output was retrieved - I've verified the file permissions, owner and group are consistent for SVN with the commands that did run - I tried switching to run subversion from other paths but without success - I tried upgrading from subversion 1.7.2 to 1.8.0 - I checked the code changes to the SCM side of redmine and nothing stood out as being an issue

I'm at a loss as to what the issue might be. Any help would be greatly appreciated.


Viewing all articles
Browse latest Browse all 2052

Trending Articles