On Thu, Dec 20, 2012 at 04:07:11PM +0000, Philip Martin wrote:
> "Bert Huijben" <bert_at_qqmail.nl> writes:
>
> > 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.
>
> Hmm, yes:
>
> $ svnadmin create repo
> $ svn1.6 co file://`pwd`/repo wc
> $ svn1.6 mkdir wc/A
> $ mv wc/A wc2
> $ svn st wc2
> A wc2
> $ svn1.7 upgrade wc2
> svn: E235000: In file '../src-1.7/subversion/libsvn_wc/entries.c' line 1666: assertion failed (parent_node || entry->schedule == svn_wc_schedule_normal)
> Aborted
>
> Does that look like the sort of working copy that triggered the original
> report? Does anybody use working copies like that? Any supported for
> that sort of working copy in 1.6 was accidental, it can't be committed
> or updated.
In any case, it shouldn't assert. It should print an error message
explaining what is wrong...
Received on 2012-12-20 19:52:51 CET