Colin Bendell wrote:
> About 90% of the time that I commit using to our svn repository I am
> prompted with the error that the file is probably out of date. The file
> is up to date and the only solution is to delete the wcprops files.
Did you update the file first before deleting the wcprops file?
> This problem is not localized to any particular workstation or
> environment as we have encountered this with a variety of OS
> installations and configurations and different projects within the
> repository. There is not a developer in our dept that has not
> experienced this problem (~50 developers)! As a hack we have a bunch of
> scripts that go and blow away all the wcprops files when we encounter this.
Such a brute force attack doesn't really help here. You're corrupting
your working copy.
> Our SVN repository has over 90,000 commits and most of our projects make
> heavy use of externals (on the same repository). This problem, however,
> is not limited to commits that span across externals and happens if it
> is a single file commit or a multiple file commit.
> As far as we can tell there is no pattern to this problem. We’ve even
> experienced this on a fresh checkout, modification, update, and commit.
What kind of modifications did you do? If you used the "ignore" command
from TSVN, then you *must* first update the working copy before
committing. Because that command modifies the svn:ignore property, and
properties set on folders require an update before any commit.
Or, if you use "update to revision", then a commit will also fail with
that error (guess why).
> Can anyone shed some light to why we have this problem? (Yes, I have
> read the FAQ on this issue which does not apply. And yes, I have read
> the newsgroups – no one appears to have a valid solution other than
> brute force deletion of the wcprops files.)
I found this:
which is a very recent thread. Maybe it's related to your problem.
But please, please: *never* mess around inside the .svn folders. If you
do, then all sorts of errors can come up and nobody will help you out
until you do a fresh checkout and you can reproduce the error *without*
having messed around inside the .svn folders.
When you say "on a variety of OS installations", do you mean Windows
exclusively or other OS like Linux too? If the latter, please report
this on the Subversion mailing list (which would even be a better idea
if you're only using Windows - because the error comes from the
Subversion library and not from TSVN directly).
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Jun 20 18:57:25 2006