----- Original Message -----
From: "Garrett Rooney" <firstname.lastname@example.org>
To: "Alex Turner" <email@example.com>
Sent: Sunday, July 30, 2006 9:12 PM
Subject: Re: Working Copy in Inconsistent State
> On 7/30/06, Alex Turner <firstname.lastname@example.org> 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
>> 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.
In particular, describing the Subversion versions of your client and your
server, and the OS on each of them, may be a big help. As a user and
programmer, I note that making checkouts atomic is a very, very different
problem than making checkins atomic, and I can easily beliave that some
subtlety is interfering with your work.
In particluar, are you using MacOS? There are some serious weirdnesses with
resource forks that can be very tough to deal with.
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Jul 31 03:21:24 2006