SVN upgrade error

[Scott Hartman <sc...@gmail.com>]

SVN Problem:

The server containing the repositories was retired before moving the
repositories to a new server (using the svn command).
The repository directory was copied to the new server
The version of VisualSVN was upgraded
The version of TortoiseSVN was upgraded
The VisualSVN directory of a program in the repository was upgraded by
right-click and choosing  SVN Upgrade working copy
The URL of the new SVN server was entered by choosing relocate

The problem occurred because a folder in the directory for setup was not
included in the SVN project, so I tried to SVN upgrade working copy on that
directory and got this error:

---------------------------
Subversion Exception!
---------------------------
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailing list archives for the error message
to avoid reporting the same problem repeatedly.
You can find the mailing list archives at
http://subversion.apache.org/mailing-lists.html

Subversion reported the following
(you can copy the content of this dialog
to the clipboard using Ctrl-C):

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)
---------------------------
OK
---------------------------

RE: SVN upgrade error

[Bert Huijben <be...@qqmail.nl>]

> -----Original Message-----
> From: MARTIN PHILIP [mailto:codematters@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 <sc...@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

Re: SVN upgrade error

[Philip Martin <ph...@wandisco.com>]

Scott Hartman <sc...@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?

-- 
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download