Wow... I missed that section of the SVN book when I was searching. It
actually turned out to be a combination of the umask part of the script,
and ensuring that the primary group of the users involved was set to the
From: Andy Levy [mailto:andy.levy_at_gmail.com]
Sent: Tuesday, April 14, 2009 12:29 PM
To: Ben Kyrlach
Subject: Re: svnserve changes ownership of files in FSFS repo...
On Tue, Apr 14, 2009 at 12:06, Ben Kyrlach <bkyrlach_at_hobsons-us.com>
> Here's my setup...
> Multiple users connect to SVN using SVN+SSH with a common key.
> The *nix machine hosting svnserve is using the authorized_keys file in
> users $HOME/.ssh to launch svnserve when connecting with said key.
> Whenever a user makes a commit to the single FSFS repository there,
> myrepository/db/current file has its ownership changed to the user.
So, if I
> commit, the files ownership changes to bkyrlach.bkyrlach. Because the
> repository disallows any access at the "other" level, it essentially
> prevents any other users from committing to the repository. I've tried
> sudo and or su in the authorized_keys file to run svnserve as root,
> I do this I get an error stating that I need a TTY in order to perform
> Are my permissions set wrong perhaps? I had it set up so that
> myrepository under was owned by root.developers, and all of the people
> svn access were in the developers group. Or is there a way to make
> not change ownership of that file?
You need to change the umask being set for those users. See the box at
the bottom of
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-04-14 20:12:24 CEST