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

.svn directory inconsistency

From: Sally Gurney <rillaith_at_gmail.com>
Date: 2006-06-30 12:53:34 CEST


I'm having a periodic problem with TortoiseSVN, where the contents of
the .svn directory are out of sync with each other.

3 of us are using the software, and noone of the others have had the
same issue. I haven't been able to identify any obvious differences
between my environment / settings and theirs - we're all using
standard build work-issue WinXP Pro boxes, and I am using the latest
version of the software ( I'm the one working on these
files most; one of the others doesn't touch my areas, and the other
only works on a small subset at any one time. I haven't identified
what I am doing that is causing the problem, but I have found an
inconsistency within the .svn files.

Each morning, and several times through the day, I do an SVN Update.
Sometimes, I will try to commit a file that I get the "out of date"
error message for, so I revert the file (or delete the local copy) and
do another Update, and a Cleanup, before immediately redoing the
change and trying to commit again, with the same error. If I delete
the directory containing that file (and the .svn folder), run another
update, and try again, the file is committed with no error message.

Yesterday, I went through the .svn files and recorded all the contents
pertaining to the file that was erroring. I then deleted the directory
containing the file (and .svn folder) and ran SVN Update. I checked
the same files within .svn to record any differences. I came across 2
places where the data was different:

.svn/entries - the text-time and the prop-time changed.
.svn/wcprops/filename.svn-work - the revision number in the subversion
path changed. The original one was on revision 812, and the new one
was revision 871 (which matches the entries file)

So, it seems that the SVN update isn't correctly updating all the .svn
data in my working copy, and that I have to cause the SVN data to be
recreated to force the update to make it consistent.

I first had this error about 6 weeks ago, when I had to delete all my
SVN directories and pull a complete fresh copy of the SVN data from
the repository. I had the same error again last week, when I ended up
doing the same thing. I've had the same issue 4 times this week. I've
been using SVN in the same manner and with the same frequency for
about 3 months now.

I've not found any reference to a similar problem or how to fix it on
the site, buglist or recent mailing list messages. The FAQ refers to
the error emssage and explains how it happens, but the slution given
there (to run SVN update) is not correcting my issue due to the
inconsistency in the SVN data.

Has anyone else seen this before, or even better, know how to prevent
it or fix it without deleting my working copies?

Many thanks for your patience and your help,


PS Should any other debug information or similar be useful, please do
let me know.

Sally Gurney, sally@tupia.net
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Fri Jun 30 12:53:42 2006

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.