subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Adean <carlosad...@linea.gov.br>
Subject Re: .svn/wc.db as group writable
Date Wed, 22 Feb 2017 16:13:52 GMT
Hello,


----- Mensagem original -----
> De: "Stefan Hett" <stefan@egosoft.com>
> Para: users@subversion.apache.org
> Enviadas: Segunda-feira, 20 de fevereiro de 2017 12:03:36
> Assunto: Re: .svn/wc.db as group writable
> 
> 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)?
> 

The default umask is 002 for all users and all of them are in the same group 'appgroup', which
is the group that owns the repositories. The repositories are remote and one specific user
creates local copies/clones. This user checks out a repository in a given directory (e.g.
/home/appuser/software/trunk) using his own account. If a different user tries to svn update
the same local copy of the repository, he gets errors of the type:

svn: E155004: Working copy '/home/appuser/software/trunk' locked
svn: E200031: sqlite: attempt to write a readonly database
svn: E200031: sqlite: attempt to write a readonly database
svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)

my doubt is: if the umask is 002 why are the permissions for the group read-only on that file
after checkout? 

> > > 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
> 

OK as soon as possible I'm going to update the version as you're suggesting.


Thank you!

--
Carlos

--
Carlos

Mime
View raw message