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

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

From: Vilar Camara Neto <vilarneto_at_hotmail.com>
Date: 2004-05-23 16:46:14 CEST


> You're getting a generic out-of-date message, meaning that the server
> isn't letting you change something, because you don't have the latest
> version of it. In this case, it's probably the fact that you changed
> properties on a directory. One of Subversion's restrictions is that you
> cannot commit a directory propchange unless your working copy of the
> directory is at HEAD.

Thanks, for the explanation. But here's my scenario: My system is
configured to allow only one user (that's me :-) ) and I've checkout only
one copy of it, so I'm always working at HEAD, right? In fact, I'm not
using SVN to manage collab development, but just as a personal versioning

Mmmm, maybe here's a tip: I think I never did a checkout since the very
first Rev 0. I mean, I did a series of modifs/commits, never needed
checkouts. The last successful commit (say, Rev 6) didn't include any dir
propchanges. So I'm wondering: Maybe this commit trial (to Rev 7) is
*thinking* that the local directory is out-of-date, because the last dir
propchange was made, say, in Rev 4? It *is* at HEAD, but maybe the SVN
client didn't update this info since Rev 4...

> 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...

Anyway, I have a backup of client and server files, so I can restore it and
give informations as if the problem was still happening.

Best regards,

Vilar Camara Neto

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 23 16:47:51 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.