X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=CU fJxI2JPaOmQ74WVRfiAONvg0W99LRphxpxPcxtn5rXXBCBkFyaugq902GviNl+OX 26NuM2VVISGW/J9yeGSQG9ivpXLRINka2IZPuJ30b7wWAFYvHv677qgArgmYf9bt KSBc95MVu3nOiJ7Jj2zPdLU+eTp+nQnKjK9qF3D+A= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=/MkVvSpr BR/sfCRDsxyjoRc/s8I=; b=OKX2ihlVeDe0ybu5SLKkK7Qk7ge7zHnH5zFzu+xH J7KPS4X7RDaYqL2027pgZRE8ckI70Ew7fvqjOBaJvkDjyLFi9Bpz3p2vrJXXxRyd 418RBzCpSc5PgHnUG+6e7LLD/qh3EacjN6+dKocrUpOvMA+bOX/ud0aI9/EQg76S t4k= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=3.0 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,KAM_FROM_URIBL_PCCC,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 X-HELO: mail-la0-f49.google.com MIME-Version: 1.0 X-Received: by 10.152.115.169 with SMTP id jp9mr68204000lab.121.1426755469241; Thu, 19 Mar 2015 01:57:49 -0700 (PDT) In-Reply-To: References: <5509C7DB DOT 4040708 AT tiscali DOT co DOT uk> Date: Thu, 19 Mar 2015 09:57:49 +0100 Message-ID: Subject: Re: Cygwin svn vs. TortoiseSVN? From: Jan Nijtmans To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes 2015-03-19 5:01 GMT+01:00 Eric Pement : > 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