> From: Arne Handt [mailto:arne@espresto.com]
> Sent: Friday, March 07, 2003 12:43 PM
[...]
> The problem occured when someone else (than me, the repository owner) tried
> to commit files to the repository for the first time. BTW, we're using the
> filesystem client only, so no Apache etc. involved. I guess there's
> something wrong with my Subversion installation, but I can't figure what it
> could be (I'm not the one who did the install).
> Well, as I mentioned before, there have been some other problems: I did
> some commits and when my colleagues tried to update their working copies
> the client aborted and I had to run a recovery. After the recovery, the
> access permissions of some files in the db folder were reset so I had to do
> a chmod...after that, the update succeeded.
>
> Are these two problems interrelated? Does anyone have a clue what the root
> problem may be? BTW, I'm using subversion 0.17.1 on a machine with Debian
> Linux version 2.4.19. I'd be really thankful for any useful information!
This is the classic permissions issue.
Create a group for your committers (e.g. svncommitters). Add all users
you want to be able to access the repos to the group, then:
$ chgrp -R svncommitters ${REPOS}
$ chmod -R g+w ${REPOS}
$ find ${REPOS} -type d | xargs chmod g+s
To be sure no none committers mess things up:
$ chmod -R o= ${REPOS}
That should do the trick.
Sander
PS. If you are also running apache, make sure you add the apache user
to the same group...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Mar 7 12:53:49 2003