> -----Original Message-----
> From: MARTIN PHILIP [mailto:codematt...@ntlworld.com] On Behalf Of
> Philip Martin
> Sent: dinsdag 19 maart 2013 05:10
> To: Scott Hartman
> Cc: dev@subversion.apache.org
> Subject: Re: SVN upgrade error
>
> Scott Hartman <scotthartma...@gmail.com> writes:
>
> > In file
> > 'D:\Development\SVN\Releases\TortoiseSVN-
> 1.7.11\ext\subversion\subversion\libsvn_wc\entries.c'
> > line 1666: assertion failed (parent_node || entry->schedule ==
> > svn_wc_schedule_normal)
>
> Were there any "Upgraded ..." lines printed before this error? Do you
> still have a 1.6 client? If so what does it show for the status of the
> working copy?
This case is easy to trigger if you break your working copy:
In 1.6 use 'svn mkdir' to create a subdirectory.
Then move the directory to a different location that is outside a working
copy. And then 'svn upgrade' just this directory that now no longer has an
ancestor.
And with the WC-NG working copy design there is no way to represent this
working copy as the root of a working copy can't be replaced.
(And even with <=1.6 it would be a useless working copy as there is no url
stored in the working copy to commit it to. That information is in the
parent, but there is no parent or parent_node wouldn't be NULL)
Bert
