[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Checkins from different users corrupting repository

From: Carl Youngblood <carl.youngblood_at_gmail.com>
Date: 2005-06-08 18:47:35 CEST

Hello, I'm having problems getting my file system permissions right
for checkins from different users. My svn repository is located in
/home/svn/svnroot. This directory is owned by user svn group svn.
Other system users have permission to use the repository. They belong
to group svn but their default group is something else. I have set
the g+s bit on the db subdir inside the svn repository so that when
users checkin their changes the file ownership stays as group svn and
doesn't get changed to the users' default group. However, the
permissions settings are getting changed. New .log files that get
added to the db subdir are getting added with 0644 permissions instead
of 0660 (what I want). This causes other users to get a corrupted
repository message when they try to update. To fix this in the past
I've had to run svnadmin recover and reset the file ownership and
permissions properly.

I'm checking in changes from Windows XP, OS X and Linux. I've noticed
that TortoiseSvn especially doesn't always seem to honor the settings
I give it (for example when I edit the subversion configuration file
manually and change the [auto-props] it seems to ignore these), so I'm
wondering if it might also be ignoring some important setting.

Anyway, I'm wondering if anyone has any advice for me that would help
me configure my system so that everything "just works". So far, svn
seems like it has been a lot harder to get working right than CVS.

Thanks,

Carl Youngblood

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jun 8 18:50:35 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.