Re: confusing E195012 error: Unable to find repository location.(when location exists)

[Daniel Shahaf <d....@daniel.shahaf.name>]

C. Michael Pilato wrote on Fri, Mar 15, 2013 at 09:42:53 -0400:
> On 03/15/2013 06:48 AM, Tom wrote:
> > 
> > Hi mailing list :)
> > 
> > Please, help me to find out what is going on in our repository. I am
> > preparing some automatic tool
> > to work with svn and there is one thing, which is confusing to me.
> > 
> > I want to do checkout to some revision:
> > If I use peg revision everything is ok as expected:
> > 
> > svn co https:\\...\branch10@11893  -r 11893
> > 
> > But when I try to ommit peg revision:
> > 
> > svn co https:\\...\branch10  -r 11893
> > 
> > "E195012 Unable to find out repository location occurs for
> > https:\\...\branch10" occurs.
> 
> Your first syntax instructs Subversion to:
> 
>    - find the 'line of history' that intersects the path
>      "https:\\...\branch10" in revision 11893 (the @ rev)
>    - walk that line of history until you get to revision 11893
>      (the -r rev)
>    - checkout that object (regardless of its path in the -r
>      revision)
> 
> As you can tell, the second step of that set of instructions seems
> redundant, right?  And in fact, it *is* redundant.  Your command-line could
> have just been:
> 
>    svn co https:\\...\branch10@11893   # without the -r
> 
> The second command syntax instructs Subversion to:
> 
>    - find the 'line of history' that intersects the path
>      "https:\\...\branch10" in HEAD (the implied @ rev)
>    - walk that line of history until you get to revision 11893
>      (the -r rev)
>    - checkout that object (regardless of its path in the -r
>      revision)
> 
> > Problem is that as I
> > browse the repository in Tortoise svn Repo Browser for revision 11893
> > theres IS path https:\\...\\branch10.
> 
> If I understand you correctly, back in r11893 there was a "branch10".
> Later, that "branch10" was moved elsewhere and a new "branch10" came into
> being.  That's fine.
> 
> The question is:  what is the very first revision for the directory which is
> called "branch10" in HEAD?  You should be able to get the answer using this
> command:
> 
>    svn log -q -r1:HEAD --limit 1 https:\\...\branch10

Need to pass --stop-on-copy too

> 
> If the answer is a revision that's younger than r11893, then that explains
> why Subversion has complained.
> 
> 
> -- 
> C. Michael Pilato <cm...@collab.net>
> CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development
> 

Re: confusing E195012 error: Unable to find repository location.(when location exists)

["C. Michael Pilato" <cm...@collab.net>]

On 03/15/2013 03:58 PM, Daniel Shahaf wrote:
> C. Michael Pilato wrote on Fri, Mar 15, 2013 at 09:42:53 -0400:
>> The question is:  what is the very first revision for the directory which is
>> called "branch10" in HEAD?  You should be able to get the answer using this
>> command:
>>
>>    svn log -q -r1:HEAD --limit 1 https:\\...\branch10
> 
> Need to pass --stop-on-copy too

Well, actually, for the information I was seeking, --stop-on-copy *could*
yield misleading results.

However, your mentioning it does call to mind what *might* be happening -- a
history gap in the lineage of branch10 which straddles the revision of
interest (r11893).  In other words, if there's a revision which appears in
the output of `svn log -qv https:\\...\branch10` like:

   r11895 | ...

   Changed paths:
      A  ...branch10 (from /some/other/path, r11890)

where an object in a pre-11893 rev was copied in a post-11893 rev, that
would also produce this symptom.

-- 
C. Michael Pilato <cm...@collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development