You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ben Collins-Sussman <su...@collab.net> on 2004/05/23 16:27:13 UTC

Re: Commit error: "The version resource does not correspond to theresource within the transaction."

On Sun, 2004-05-23 at 10:16, John Peacock wrote:
> Vilar Camara Neto wrote:
> >>So run 'svn update' to bring your entire working copy to HEAD.  Then
> >>commit.
> > 
> > 
> > I already tried it, an it worked.  But I think this is just a workaround,
> > the real thing isn't addressed yet...
> 
> No, it isn't a workaround; it is the nature of working with mixed revision 
> working copies.  Even though *you* are the only one working with the WC and the 
> only one committing to the repository, you must 'svn up' before certain 
> operations, otherwise the software assumes you are not up to date.  Just doing 
> 'svn ci' is not sufficient in the general case.

Vilar, you need to understand that your working copy has mixed revision
numbers.  This happens after *every* commit, and is completely normal.
If you never, ever run 'svn update', then your working will become more
and more "mixed" as time goes on.  

Please read chapter 2;  it explains all this.  The critical section is
at the end, "The Limitation of Mixed Revisions."




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org