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

wcprops files getting out of date.

From: Vianney <vianney_at_conversagent.com>
Date: 2004-06-26 00:57:04 CEST


I'm consistently getting the out-of-date error when I commit some of the files in my WC directory:

$./svn commit ../Projects/CorpInfo/Articles/General/CatBackground.ddl -m "pipo"
Sending Projects/CorpInfo/Articles/General/CatBackground.ddl
svn: Commit failed (details follow):
svn: Your file or directory 'CatBackground.ddl' is probably out-of-date
The version resource does not correspond to the resource within the transaction. Either the requested version resource is out of date (needs to be updated), or the requested version resource is newer than the transaction root (restart the commit).

Restarting the commit, or updating the working copy won't help. After some research, I've narrowed the apparent source of the problem to the svn-work files located in .svn/wcprops/ :

$ ll ../Projects/CorpInfo/Articles/General/.svn/wcprops/
-r--r--r-- 1 ab ab 118 Jun 25 12:40 CatBackground.ddl.svn-work

$ cat ../Projects/CorpInfo/Articles/General/.svn/wcprops/CatBackground.ddl.svn-work
K 25
V 77

It appears that this 'cache' file, once created, is never updated unless I commit changes outside and update my working copy. So after the first commit the version number of the checked in file and the version number appearing in the URL of the svn-work file, are out of sync. Deleting the file allows to work around the issue and force a commit, but not solve the problem. Another way to work around it is to change the 113 in the URL to the current version of the file, but that too is just temporary. Moreover, at that first commit (with no file in wcprops/), I may be commiting revision 118 and still get 113 in the newly created svn-work file.

So I'd like to know more about what the files in wcprops/ are supposed to be made of and when they're supposed to change; if such an issue has already been documented and/or addressed? And considering I never touched the metadata files until the problem showed up, what may have caused the corruption and what I should do to prevent it from happening again?

I'm using subversion v1.0.4, on Redhat 9.

Received on Sat Jun 26 00:58:59 2004

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

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