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

mergeinfo assertion in trunk Re: 'svn switch' now requires --ignore-ancestry?

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 23 Apr 2011 12:21:22 +0300

On Sat, 23 Apr 2011 07:15 +1000, "Daniel Becroft" <djcbecroft_at_gmail.com> wrote:
> Hi,
>
> I've just updated to trunk_at_1096029, and have noticed the following change in
> behavior.
>
> Previously, any reproduction script I write has the following pattern:
>
> svn checkout <url> workingcopy
> > pushd workingcopy
> > svn mkdir trunk
> > svn commit
> > svn switch <url>/trunk .
> >
>
> This used to work fine. But now I'm getting the following error messages:
>
> subversion/svn/switch-cmd.c:184: (apr_err=195012)
> > svn: E195012: Path '.' does not share common version control ancestry with
> > the requested switch location. Use --ignore-ancestry to disable this check.
> > subversion/libsvn_client/switch.c:201: (apr_err=195012)
> > svn: E195012: 'file:///home/djcbecroft/dev/sandpit/repository/trunk' shares
> > no common ancestry with '/home/djcbecroft/dev/sandpit/workingcopy'
> >
>
> As the error message suggests, using --ignore-ancestry works fine. I don't
> think this is required, though, as the paths share a common ancestry
> already.
>

I've not read the whole thread, but tweaking your recipe I've just run into an assertion in a case I expected to work:

[[[
% rm -rf wc1 r1
% $svnadmin create r1
% $svn co file://$PWD/r1 wc1
Checked out revision 0.
% cd wc1
% $svn cp . trunk
svn: E200007: Cannot copy path '/tmp/svn/wc1' into its own child '/tmp/svn/wc1/trunk'
% $svn cp ^/ ^/trunk -mm

Committed revision 1.
% $svn sw ^/trunk
subversion/libsvn_subr/mergeinfo.c:800: (apr_err=235000)
svn: E235000: In file 'subversion/libsvn_subr/mergeinfo.c' line 800: assertion failed (IS_VALID_FORWARD_RANGE(first))
zsh: abort $svn sw ^/trunk
]]]
Received on 2011-04-23 11:21:51 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.