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

Re: commit failed - Invalid change ordering: new node revision ID without delete

From: Duncan Murdoch <murdoch_at_stats.uwo.ca>
Date: 2006-03-12 21:35:10 CET

On 3/12/2006 3:47 AM, Craig Lawson wrote:
> Hi subversion users,
> I'm new to the group and to svn. I'm using 1.2.3-r2 on gentoo to
> manage a web project, and just recently moved a bunch of files and
> directories around. When I commit, I get:
> $ svn commit -m "big change"
> (Adding, Deleting, Sending, etc.)
> Transmitting file data ............................svn: Commit failed
> (details follow):
> svn: Invalid change ordering: new node revision ID without delete
> Just to be sure I hadn't messed things up with too much fiddling, I
> started from a fresh copy and repeated my svn commands, synchronizing
> file and directory contents with the failed working copy but keeping the
> .svn content independent. Same result.
> Is this an svn bug? Sure looks like a bug. svn appears to be telling me
> that it cannot construct a valid transaction even though I used valid
> svn commands. What to do next?

I think it looks like the bug discussed here:


In that thread it was triggered by doing a copy from the working copy to
a new branch, and the workaround was to do the copy in the repository,
and then switch the working copy. I.e. instead of

svn cp . URL:newbranch


svn cp URL:trunk URL:newbranch -m"create branch"
svn switch URL:newbranch
svn commit -m"big changes to new branch"

(where URL:trunk and URL:newbranch aren't to be taken literally, of
course: put in the actual URL of your original copy).

At least I think that's a correct summary....

Duncan Murdoch

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Mar 12 21:36:04 2006

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