Max Bowsher wrote:
> Craig Lawson wrote:
> >> Hi Subversion developers,
> >> I'm new to the dev list, and I signed on to resolve a "Invalid change
> >> ordering: new node revision ID without delete" message which is
> blocking
> >> my commit. I've somehow tied my workspace into a knot which svn can't
> >> swallow. Before trying a different approach to complete my check-in, I
> >> wanted to make a proper bug report.
> >>
> >> I'm using subversion 1.2.3, FSFS, trunk only.
> >>
> >> There has been some traffic on this issue in the past, but it's
> >> infrequent:
> >>
> >> Discussion I had on the subversion-users list:
> >>
> http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=46296
> >>
> >> Discussion on subversion-dev last year:
> >> http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=100290
> >>
> >> Someone else saw this problem and has a work-around:
> >> http://www.raditha.com/blog/archives/000590.html
>
>
> Thankyou for the report - there's clearly some lurking bug somewhere for
> that message to be appearing.
>
> I don't suppose you might know of a recipe to reproduce this error
> state, do you? I fear that tracking the bug down without that is
> unlikely to be possible.
>
> Max.
Yes, I do know the recipe. I've been through it twice now.
I kept notes during my second attempt. Which was essentially to
check-out a new copy of my files, and then make all the moves, renames,
deletes, and modifications necessary to satisfy a recursive diff.
Probably not exactly the same sequence, but it gave the same result.
What information would best help the subversion team? Probably not my cribs.
Philip Martin wrote:
> Craig Lawson <craig.lawson@alum.mit.edu> writes:
>
>
>> I'm new to the dev list, and I signed on to resolve a "Invalid change
>> ordering: new node revision ID without delete" message which is blocking
>> my commit. I've somehow tied my workspace into a knot which svn can't
>> swallow. Before trying a different approach to complete my check-in, I
>> wanted to make a proper bug report.
>>
>> I'm using subversion 1.2.3, FSFS, trunk only.
>>
>
> I think this was fixed last year by r14770, try 1.3 or 1.4.
>
I could try this with 1.4. My approach would be:
1. Archive my repository and workspace just in case.
2. Build 1.4
3. Attempt to check in my changes made with 1.2.3 with svn 1.4
Am I missing something? Please stop me before I waste my time.
Thanks for your replies,
Craig.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 21 03:29:10 2006