Hello,

I'm testing out this functionality for a site I'm working on. I'm running LAMP stack (Apache 2.2.3, PHP 5.2.9), where the repository is accessed through https, users are authenticated (passed through auth-pam kerberos). The repository is operating fine, can access it through the web and shell. The repository is located on the same server as the drupal installation (using 6.13) and subversion 1.6.2.

When trying to "fetch" using the VCS Repositories section, I input the url either through https://server/pathtorepo/repo (credentials have been entered in the authentication section of the form), or through file:///pathtorepo/repo; then I receive this error "sh: svn: command not found". Is there something wrong with my syntax? Any steps you would suggest to help me get to the bottom of why I can't retreive the commit info?

Going to try to look into your code to see if I'm missing something... (but I'm a bit of a newbie in php).

Any help you might have to offer would be welcome.

Thanks in advance
Brandon

Comments

jpetso’s picture

jpetso commented

It seems the "svn" binary is not in your $PATH - or rather, in the $PATH of the webserver. Try to log in as your webserver user (www-data?) with "su $username" (or "sudo su $username", depending on your distro - you might also need to supply a login shell or temporarily change the existing one in /etc/passwd) and run any SVN command from that login shell. Then have a look how you can fix it for that environment. If you managed to add it to the $PATH of your webserver user, the Drupal side of things should (hopefully) be fine.

bschakola’s picture

bschakola commented

Thanks, doing some server maintenance this morning (Centos, btw). Also updating subversion to the latest (1.6.4). I was poking around this morning and it appears from the looks of it, it's a path problem. Thanks for the help (even though it was more of a server config problem than your module).

jpetso’s picture

jpetso commented
Status: Active » Fixed

I take this as a "ok, you can close the issue".

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.