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

Re: Working Copy in Inconsistent State

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-07-31 03:12:58 CEST

On 7/30/06, Alex Turner <armtuk@gmail.com> wrote:
> You know, for an atomic SCM, subversion sure as hell seems to leave my
> working directories screwed up a little too often:
> svn: Invalid change ordering: new node revision ID without delete.
> Well - I sure as hell typed the commands in the right order, it's not too
> hard: svn mv a b.
> How many other people have had to check out a new working copy and copy
> changes over and commit because their working copy was broken _again_
> without any explanation provided and a cryptic error message that doesn't
> really explain what the problem actualy is?
> Is there any hope that Subversion will improve on the current state of
> affairs or should we all be looking to shell out for a commercial scm that
> works more often?

Unfortunately, you've hit a bug. Sorry, it happens, even in
commercial scms. Welcome to the real world, where things are
occasionally imperfect.

If you can provide a sequence of commands that gets your repository
and working copy into that state (i.e. something that starts from an
empty repository and makes it happen) I'll be happy to look into
fixing the problem. Unfortunately, you haven't actually provided much
information in your email other than "I get this weird error when I do
something", so it's rather difficult for me to determine what the
problem is based on it.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 31 03:14:24 2006

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

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