Chris 'Xenon' Hanson wrote:
> Stefan Küng wrote:
>>> 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.
> What would have been the "proper" way to fix this so I can sort it out
> if/when it next happens?
Update the working copy, run cleanup. If that doesn't work, zip up the
corrupted folder and send it to the subversion dev list for analysis.
>> Configure your virus scanner to not scan your working copies. And
>> maybe ditch the one you're currently using and get another one.
> This machine is not virus-scanning, and does not run ZoneAlarm, or
> anything other than the WinXPsp2 firewall.
>> Even though you haven't told us what *your* exact problem is
> The problem seems to be that after a check-in of a file by user A, a
> subsequent attempt to check-in a new change to that file by user A
> fails, claiming that the file is not up to date. No other user has
> checked in anything to the same file in the interim. The working copy
> directory _has_ been svn updated.
Do you have some commit hook scripts running on the server which might
not work properly? For example, if a post-commit hook script fails (or
takes too long because it isn't started as a new process/thread), then
the commit succeeds but the working copy isn't updated to reflect the
> I don't know what other circumstantial data you might need, I posted
> everything that seemed relevant.
You posted a lot of links to users describing problems with commits, but
every one of them was due to different problems. So I couldn't know what
your problem was. Now that I know: this shouldn't happen, and doesn't
happen to most people (we would get flooded here on the list if that
problem would occur often). So there must be something different on your
Do you maybe also use the cygwin client? That one corrupts working
copies which are used by other svn clients because it simulates Linux,
which handles working copies differently than windows svn clients.
Also check your hook scripts on the server.
Run chkdsk on your harddrive. It may be a bad sector which keeps messing
with the data (happens more often than you might think).
Do you get any errors when you commit?
Do you often change properties on folders? Because to commit those, you
usually must first run an update.
That's all I can think of right now. Maybe you can think of something on
your computer/server setup that's not very common?
It's midnight here, so I won't answer your next mails until tomorrow.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Sep 28 23:57:11 2007