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

Re: TortoiseSVN stale all-wcprops cache

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-09-28 23:22:23 CEST

Chris 'Xenon' Hanson wrote:
> I just built a new SVN repository for my small R&D company. We
> previously used CVS and WinCVS for nearly 8 years without any major
> problems.
>
> Versions in play:
> WinXP Pro
> TortoiseSVN-1.4.5.10425
> subversion1.3.2-3ubuntu (Ubuntu 6.06 LTS)
> Apache2 2.0.55-4ubuntu
>
> I'm experiencing the stale all-wcprops problem mentioned in these
> various pages:
> http://svn.haxx.se/users/archive-2006-05/0178.shtml
> http://chxo.com/be2/20070412_svn_wont_commit_dammit.html
> http://www.voidspace.org.uk/python/weblog/arch_d7_2007_05_19.shtml#e721
> http://readlist.com/lists/subversion.tigris.org/users/3/16001.html
> http://www.nabble.com/Subversion-update-problems-t4128464.html
>
> Many of the posts cite TortoiseSVN as a common factor, but not all.
>
> I've employed the deletion of .svn/all-wcprops as a workaround, and it

Never, ever mess around inside the .svn folders! I repeat: NEVER, EVER
mess around inside the .svn folder!

But since you already did:
delete your working copy and get a fresh checkout.

> helped. I'm wondering if there is some way to troubleshoot this? I'm
> using https/DAV for the transport. It has happened a couple of times
> with only three developers working on the project, and I'm getting
> ragged on by the other guys for having switched to something unreliable. :(
>
> We also have the AnkhSVN plugin for Visual C++ installed in VC++2005.
> We've used both. For the moment, we're avoiding Tortoise to see if we
> can pin down if the error is also present in Ankh.
>
> I found this issue:
> http://copilotconsulting.com/mail-archives/subversion.2005/msg06421.html

That was fixed years ago.

> But it seems to have already been fixed in 2005 and my repository
> doesn't have unicode chars in the URL.

Configure your virus scanner to not scan your working copies. And maybe
ditch the one you're currently using and get another one.

Even though you haven't told us what *your* exact problem is, my best
guess is that your virus scanner is interfering with the files during an
update, and that makes the update corrupted. Oh, and if you're using
ZoneAlarm: abandon all hope. Seriously: ZoneAlarm was the reason for
many, many, many complaints here because it sometimes even resets the
file timestamps without reason, locks files and messes around in the
whole system.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Sep 28 23:22:38 2007

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