All geek questions in one place

Licensing for Supernatural Subversions

I am trying to configure SVN on a CentOS 5 system so that several people can use the repository.

  • I created a repository on /var/svnrepository.
  • I added the user and group subversion, making recursively the owner of the repository.
  • I set recursion permissions to 775.
  • I guaranteed that all users of the system are in a group subversion.

The problem I am facing is that when I commit, SVN seems to create a file called db/current, and it has my username and group. So say my username jimbo...

-rwxrwxr-x 1 jimbo      jimbo         11 Dec  2 01:09 current

Then after that no one can check anything. They are denied permission.

A similar problem occurs with the file db/format.

Can not open file /var/svnrepository/contactdb/trunk/format: Permission denied

Has anyone else seen this? Know the solution?

Access to the repository is via ssh.

Strange, I already installed SVN on Linux and did not have this problem. This time I do not know what I am doing differently.

+3
source share
2 answers

Note that usually setGID is set in the Subversions repository directory and their child directories:

drwxr-sr-x svnowner svnusers 4096 2008-11-01 .

by chmod 775 you canceled this setGID bit and this is why there were problems:

SetGID means: if you create a file, svnusers (in my example) will be installed for the group , and not your main group.

I bet you don't have a SetGID set, do you?

However, it is better to change the GID of the folders:

chmod g+s <REPO>/dir

, .

+3

svnserve file:/// URI? Subversion . svnserve -d .

.

+2

Source: https://habr.com/ru/post/1724450/

More articles:


All Articles