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

RE: problem when upgrading my working copy

From: Bert Huijben <bert_at_qqmail.nl>
Date: Thu, 20 Dec 2012 16:25:32 +0100

> -----Original Message-----
> From: MARTIN PHILIP [mailto:codematters_at_ntlworld.com] On Behalf Of
> Philip Martin
> Sent: donderdag 20 december 2012 16:20
> To: Pia Unte
> Cc: users_at_subversion.apache.org
> Subject: Re: problem when upgrading my working copy
>
> Pia Unte <pia.unte_at_gess.uni-mannheim.de> writes:
>
> > In file
> > 'D:\Development\SVN\Releases\TortoiseSVN-
> 1.7.10\ext\subversion\subversion\libsvn_wc\entries.c'
> > line 1666: assertion failed (parent_node || entry->schedule ==
> > svn_wc_schedule_normal)
>
> I think that's a new one. Can you describe your working copy? Can you
> use Subversion 1.6 and run status? Do you have adds, deletes, copies,
> switches? Is your working copy mixed revision? Was there any output
> before the assertion?

This is caused by upgrading an added directory without its parent directory.
Most likely caused by moving a single working copy directory.

This state (added to a parent that does not exist) is not supported by the
new working copy database introduced in 1.7. The database always requires
the root of the working copy to exist in the repository.

        Bert
Received on 2012-12-20 16:26:11 CET

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.