You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Vianney <vi...@conversagent.com> on 2004/06/25 22:57:04 UTC
wcprops files getting out of date.
Hello,
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
svn:
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
svn:wc:ra_dav:version-url
V 77
/svn/demo/!svn/ver/113/trunk/CorpInfo/Articles/General/CatBackground.ddl
END
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.
Thanks!
Re: wcprops files getting out of date.
Posted by Ben Collins-Sussman <su...@collab.net>.
[keeping this on the dev list]
On Mon, 2004-06-28 at 13:47, Vianney wrote:
> As you can see below, this isn't the case, as the repository is not at the
> virtual root of Apache, and the file is not at the root of the repository:
>
> in CatBackground.ddl.svn-work:
>
> "/svn/demo/!svn/ver/113/trunk/CorpInfo/Articles/General/CatBackground.ddl"
>
> in httpd.conf:
> <Location /svn>
> DAV svn
> SVNParentPath /home/svn
> </Location>
>
> I havent found yet the sequence of events that reproduce this consistently
> from a fresh check out, but the problem has been creeping back pretty often
> and once it's there it won't go away with just a wcprops cleanup. Any ideas?
No, but I'm dying to figure out how to reproduce it. Whatever is
happening to your system is *incredibly* rare.
Here's what would be useful: 'svn up' your working copy, edit a file,
then use ethereal to trace an 'svn commit'. I'd like to see the exact
message being sent back by the server.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: wcprops files getting out of date.
Posted by Ben Collins-Sussman <su...@collab.net>.
On Fri, 2004-06-25 at 17:57, Vianney wrote:
> It appears that this 'cache' file, once created, is never updated
> unless I commit changes outside and update my working copy.
The file's cache should be updated whenever you commit a change to the
file. It also gets updated when 'svn up' decides to update the file.
Is this bug, perhaps, issue 1851?
http://subversion.tigris.org/issues/show_bug.cgi?id=1851
This bug is only known to happen when the repository is located at
apache virtual location "/", though. Is that how you have it set up?
If you can reproduce it in some other way, then we need to dig deeper
and possibly file a new bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org