-----BEGIN PGP SIGNED MESSAGE-----
Thanks for clearing up my confusion.
I did a svn up and svn commit. Same problem.
I did a svn revert on the file (after copying the contents to a a new file)
Everything looked fine.
I opened up the reverted file and pasted in the code that I previously
Tried to svn commit
svn: Commit failed (details follow):
svn: Your file or directory 'ItemActionImpl.java' 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)
Ryan Schmidt wrote:
> On Apr 25, 2007, at 02:43, David Harrigan wrote:
>> I get, every so often, a very strange error when trying to commit into
>> the repository. Here's the error:
>> david@piccolino:~/javastuff/eclipse-3.3m6/workspace/mediaservice$ svn
>> commit -m "test"
>> svn: Commit failed (details follow):
>> svn: Your file or directory 'actions/ItemActionImpl.java' is probably
>> 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).
> It can be perfectly normal to encounter that message. You may have a
> mixed-revision working copy. Please read:
> Especially item #2, and also the link to the extended discussion of the
> topic in the Subversion Book.
>> 1. I'm the only person working on the repository presently.
> That's fine, and you can still see that message when you're the only one
> working on a project, as explained above.
>> 2. The local file is more up-to-date that the remote file.
> Um... that's not... possible. Up-to-dateness in Subversion terminology
> refers to a working copy only and is in respect to the repository
> version. If by "remote file" you mean the version in the repository,
> then it does not make sense to say that the remote file is up-to-date
> because a) it's not a remote file; it's a record in the Subversion
> repository database, which is not actually a file on disk, and b) the
> repository is always up-to-date with itself, whereas the working copy
> may be up-to-date, or it may be some revisions behind the repository.
> Now, if you meant that your working copy has changes in it which are not
> yet in the repository, then that's fine but the way to express it would
> be that the local working copy has uncommitted changes. Separately from
> that, your working copy may or may not be up-to-date.
>> 3. Both client and server are running 1.4.3
>> 4. Server and client are both Linux (Server = Redhat, Client = Ubuntu)
>> 5. Both machines have similar dates (the client is a few seconds ahead)
> That's probably fine.
>> 6. Running svn cleanup doesn't help.
> Unless Subversion told you "run cleanup", running cleanup won't help
>> 7. Running svn up and then svn commit doesn't work
> This is the only thing you wrote that indicates something else may be
> wrong. Are you absolutely sure that "svn up" and then "svn commit" still
> produces the same error message? If so, then I do not know what the
> problem is, other than that your working copy may be messed up, and you
> should check out a new working copy and use that in the future.
PGP Key Id: E2BE72FC
Public Key: http://www.harrigan.info/public.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Apr 25 11:18:35 2007