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

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

From: Tom <tomas.bartek3_at_gmail.com>
Date: Fri, 15 Mar 2013 03:48:31 -0700 (PDT)

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. Problem is that as I
browse the repository in Tortoise svn Repo Browser for revision 11893
theres IS path https:\\...\\branch10.
(even that is was 11894 renamed and the new https:\\...\branch7 was
copied from another path in 11895.

I would consider it as a feature but when I do the same thing with
another branch in our respository. I obtain different result:

svn co https:\\...\branch7_at_11893 -r 11893

(again works fine. checkouts branch7 in 11893 revision.)

svn co https:\\...\branch7 -r 11893

This command will end without error and checkouts the branch from
which the branch7 was copied.
I am confused why there is not the same result for the branch10??

Here is some screenshot from TortoiseSvn revision graph, maybe there
will be hidden some answer to this:

<http://subversion.1072662.n5.nabble.com/file/n179019/coBehavior.png>

Thanks in advance.
Tom

--
View this message in context: http://subversion.1072662.n5.nabble.com/confusing-E195012-error-Unable-to-find-repository-location-when-location-exists-tp179019.html
Sent from the Subversion Users mailing list archive at Nabble.com.
Received on 2013-03-15 11:49:08 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.