[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: ERROR can't move *.svn-work to *.svn-base: access is denied

From: Andy Levy <andy.levy_at_gmail.com>
Date: Wed, 17 Jun 2009 08:44:12 -0400

On Wed, Jun 17, 2009 at 03:04, Tobias Rapp<t.rapp_at_noa-audio.com> wrote:
> Simon Large wrote:
>> I believe the delete readonly=yes setting is a temporary workaround
>> for a bug in SAMBA. In later SAMBA versions it probably isn't needed.
> Does anybody know which samba version has this bug fixed? I had a look at the FAQ (http://tortoisesvn.tigris.org/faq.html#samba) but also no versions are mentioned there.
> In my case I have tried both workarounds mentioned in the FAQ without success. Sometimes in my case it helps to remove the read-only property recursively on the base folder of the working copy followed by a SVN clean-up. Most of the time this also doesn't work and I have to do an in-place export and a fresh checkout then.
>> The behaviour of the subversion library changed in 1.5. Something
>> along the lines of simplifying the code to use standard file access
>> APIs and less kludges.
> Another example of developers rating code beauty over user experience :-(

This isn't about "code beauty." Kludges are bad. Using standard APIs
is good. Overall, it's a net gain because things are now being done
properly, even if that means exposing bugs in other software. At the
end of the day, everyone benefits.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-17 14:44:25 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.