This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Cygwin svn vs. TortoiseSVN?
- From: Jan Nijtmans <jan dot nijtmans at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Thu, 19 Mar 2015 09:57:49 +0100
- Subject: Re: Cygwin svn vs. TortoiseSVN?
- Authentication-results: sourceware.org; auth=none
- References: <5509C7DB dot 4040708 at tiscali dot co dot uk> <CAB+hQJ6QVEKJs4=ZQHwZFLbW-jyxHQ40CGPANbne8TLj=78K5w at mail dot gmail dot com>
2015-03-19 5:01 GMT+01:00 Eric Pement <eric.pement@gmail.com>:
> The TortoiseSVN FAQ file, answering the question of whether one can
> use different SVN clients on the same working copy, says this is not
> recommended.
> The FAQ mentions Cygwin in particular:
I am aware of this FAQ entry, but with latest SQLite versions this
is not a problem any more, as cygwin SQLite uses the
same locking semantics as the sqlite client in TortoiseSVN does.
I am using TortoiseSVN in combination with the cygwin svn client
without any problem (but I understand the suspicion due to
past experience).
Another reason why I don't think the locking is the problem:
> svn: E000013: Can't open file '/cygdrive/D/xxx/yyy/.svn/tmp/svn-sckggY': Permission denied
The SQLite database file can be found in /cygdrive/D/xxx/yyy/.svn/wc.db',
so any file opened by SQLite can only be this file (or related .wal/.journal
file), or some temporary file named something like '/tmp/etilqs*'. The file,
'svn-sckggY' doesn't look like that, so it's opened by subversion, not by
SQLite. That's why the recent ACL-related changed in cygwin are
more likely causing the problem here.
Anyway, thanks for your report!
Regards,
Jan Nijtmans
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple