Hi Ian! On 1/22/07, Ian Dexter R. Marquez <[EMAIL PROTECTED]> wrote:
Thanks, Dean.
No problem. :)
svn: Can't check path '/home/user/.subversion': Permission denied So http_user is looking for a config path? I copied a working config directory to /tmp: cp -r /home/user/.subversion /tmp/config chown -R httpd_user:httpd_user /tmp/config $ sudo -u httpd_user /usr/bin/svn update /path/to/webapps/rootdir --config-dir /tmp/config And it worked! I also tested the post-commit hook to automatically update the working directory based on the last commit, and that, too, worked. Hay... But that should have worked without a config dir, right? Please correct me if I'm wrong. (I did try it without explicitly pointing to the config dir, and the subsequent commits worked. *Sigh* some more.)
Actually it does need a client configuration directory for the user running the svn binary -- this is because that's where the svn binary caches data (like passwords, repository details, usernames, client specific flags/configurations, etc.). What happened here is that the configuration information had been saved in the configuration of the working copy. This is why usually the first time a user runs svn checkout, the client specific flags are put in ~/.subversion and the working copy will refer/defer to the configuration which you used to check out the code. If you used a different directory for the configuration, then the working copy will refer to that directory in succeeding updates. HTH! -- Dean Michael C. Berris http://cplusplus-soup.blogspot.com/ mikhailberis AT gmail DOT com +63 928 7291459 _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
