On 2/20/2017 1:40 PM, Carlos Adean wrote:
On the specific issue: I'm not getting completely what problem you
are
facing. Are you expecting that SVN sets the group for .svn/wc.db
according to some group you set up by itself so it's readably/usable
by
other users than the one who did the repository checkout?
Regards,
Stefan
So, I have set umask 002 and it works for all files except on .svn/wc.db -
maybe I'm wrong and this is not a SVN problem.
Again, I know this is unusual situation but is how we need to work.
Can you be a bit more specific what exactly you mean by "That's the file
that causes the problem[...]"? Do you get an SVN error when you perform
some operation from different accounts on the working copy (in that
case, please state the exact error message)? Alternatively: Are you
suggesting that after performing an SVN operation the permissions of
.svn/wc.db are changed (to what they were before the call)?
Also understand that wc.db is an SQLite database. While that should in
principle work with multiple users accessing the same database, the fact
that you are running a very old version of SVN suggests that you might
also use a very ancient version of SQLite (down to SQLite 3.8.1). It's
possible that this is causing some trouble in your case due to bugs
which have long been fixed in SQLite [1].
Last but not least, I certainly urge you to ensure that all the users
accessing the working copy use a decent version of SVN (preferably
1.9.5) and do not share the same working copy under SVN versions which
are too far apart from one another (for instance a client using SVN
1.8.0 and another one using SVN 1.9.5).
While this is supported by SVN (unless the working copy format changes),
the fact of using different SQLite versions and other dependencies
increases the risk for you to run into bugs/issues nobody else would
expect to run into (which then increases the workload to troubleshoot
such problems).
[1] https://www.sqlite.org/changes.html
--
Regards,
Stefan Hett
