public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: Cygwin svn vs. TortoiseSVN?
Date: Wed, 18 Mar 2015 23:46:00 -0000	[thread overview]
Message-ID: <550A08BA.8090602@tiscali.co.uk> (raw)
In-Reply-To: <B04B152D-806D-4DFD-8BC2-792E35C7C900@Denis-Excoffier.org>

On 18/03/15 20:57, Denis Excoffier wrote:
> On 2015-03-18 19:45, David Stacey wrote:
>> I have a PC with both Cygwin and TortoiseSVN. When I try to commit through Cygwin svn, I get the following (slightly redacted):
>>
>> Committed revision nnnnn.
>> svn: E200000: Commit succeeded, but other errors follow:
>> svn: E155009: Error bumping revisions post-commit (details follow):
>> svn: E155009: Failed to run the WC DB work queue associated with '/cygdrive/D/xxx/yyy', work item 528 (file-commit aaa/bbb.c)
>> svn: E000013: Can't open file '/cygdrive/D/xxx/yyy/.svn/tmp/svn-sckggY': Permission denied
> Just in case: mount the appropriate part of your D disk with the 'noacl' option, ie add something like
> D:/Wherever/Is/Your/SVNRepository /svnR ntfs cygexec,noacl
> at the end of your /etc/fstab,
> and use
> file:///svnR
> for your repo.

Thank you for your reply. It's a good thought about ACLs - my immediate 
thought was that this must be a locking problem, so I never considered ACLs.

My repository is on a server, accessed over https. The errors are coming 
from the svn client updating the working copy. This working copy is on 
the 'D' drive, so I'll try mounting '/cygdrive/d' as 'noacl' and see if 
that helps.

Dave.


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

  reply	other threads:[~2015-03-18 23:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-18 20:58 David Stacey
2015-03-18 22:49 ` Denis Excoffier
2015-03-18 23:46   ` David Stacey [this message]
2015-03-19 20:03   ` David Stacey
2015-03-19  8:34 ` Eric Pement
2015-03-19 10:05   ` Jan Nijtmans
2015-03-19 17:38   ` David Stacey
2015-03-19 10:31 ` Csaba Raduly
2015-03-19 13:18   ` Jan Nijtmans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=550A08BA.8090602@tiscali.co.uk \
    --to=drstacey@tiscali.co.uk \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).