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

Re: can't svn commit

From: Max Bowsher <maxb_at_ukf.net>
Date: 2004-07-09 12:29:20 CEST

Aaron Chan wrote:
> Hi,
> I hope this is not a subversion bug
> but when I make changes to any file
> I get the error below...
> Did I make some silly mistakes?
> What does "out-of-date" mean? My local copies are not up-to-date?
> Doesn't svn update bring me the lastest revision and save it in
> .svn/ ?
> The error message wasn't very helpful to me
> I had no problem with svn add or svn delete
> It looks like svn can't handle modified-files
> I am using subversion-1.0.5/ for client and server
> Let me know what else you will need to know
> Thanks
> Aaron
> ==============================================
> [aaron@doer]$ svn update
> At revision 9.
> [aaron@doer]$ svn commit -m ""
> Sending index.php
> svn: Commit failed (details follow):
> svn: Your file or directory 'index.php' 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).

This looks like the "wcprops cache out of date" bug (issue 1851).

Can you show us the output of "svn info" in your working copy?

Can you reproduce the error in a new freshly checked out working copy?


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 9 12:33:20 2004

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

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