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

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_at_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_at_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

If the answer is a revision that's younger than r11893, then that explains
why Subversion has complained.

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