On Nov 1, 2006, at 18:47, Colleen Dick wrote:
> I have several team members. We are elaborating a web application.
> Each developer has their own private deployment and we
> all commit to the repository from our remote machines just fine.
> Recently I needed to do several emergency tweaks on the
> working copy that is the live online copy. I would like to commit
> these tweaks to the repository (which by the way lives on the same
> physical machine as the live online deployment) When I try to commit
> I get
> svn: Commit failed (details follow):
> svn: Can't create directory
> '/back2/svn/tixrus/db/transactions/674-1.txn': Permission denied
>
> svn is owned by the svn user and so is the directory tixrus
> I guess when people commit remotely they go in as that.
> Should I become the svn user whenever I commit to the repository that
> is on the same box? I can do that. I don't want to chown anything
> because I'm afraid I'll lock all my developers out.
How are you accessing the repository? Via the file:/// protocol? If
so, I encourage you to investigate setting up an svnserve process and
using only the svn:// protocol to access the repository. You will
avoid permissions problems like this (because only a single user --
the user under which svnserve runs -- will need to access the files)
and you will increase security by ensuring that only this user is
able to access the repository. See the book at http://svnbook.org/
for instructions on setting up svnserve.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Nov 2 02:25:43 2006