On Nov 5, 2009, at 15:27, Tyler wrote:
>>> I'm trying to update a working copy by having svn update executed
>>> during a post-commit script after the repo has been committed to by
>>> another wc. I have a script that executes svn update, but it only
>>> works when I run it directly in the command line. It gets an error
>>> and stops when the hook script is called automatically by svn. I'm
>>> executing "SVNPATH/svn update fullPathToWC" but I'm not sure why it
>>> only works from command line.
>>
>> It's probably filesystem permissions. The hook runs as the user the
>> server is running as and that user must have read/write access to the
>> wc path being updated and EVERYTHING within it. Check your
>> permissions.
>
> Is the user you're referring to the same as the svn author?
No: the user the server-side working copy is owned by, which should be
the user your Subversion repository is served by...
> Otherwise, I'm not really sure where to look to change file
> permissions. SVN is being run by Apache on a Win2k server.
...which will be the user your Apache server is running as. On Linux
this could be "nobody" or "www" or "apache"; I don't know what it will
be on a Windows server.
Another likely candidate is that you have not specified authentication
details, e.g. with the --username and --password options. When you run
the script yourself, it uses your cached credentials, but your Apache
web server probably has not been a Subversion client before and so
doesn't have any credentials cached.
More generally, you need to direct both the stdout and the stderr of
the svn command in the script to some useful place, like a log file,
so that you can find out exactly what's going on.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2415685
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-11-09 08:05:22 CET