On Mar 7, 2008, at 14:16, Ben Schonle wrote:
> A short update:
> -------------------
>
>
> Hello,
>
> I can now check out to a remote machine using Tortoise.
> - I mark a folder to be used for the local working copy and click
> "Checkout" in the context menu appearing on right click.
> - I enter: svn+ssh://ben3@192.168.0.38/home/svn/myproject
> - It asks the psw for ben3 twice
> - I enter password twice.
> - It checks out and creates a local copy.
Great! So it works. Seems like you're done...
> Now to the persisting problem:
> -------------------------------------
> - I use putty, ssh
> - I login first with ben3, enter the password for ben3
> - Then I enter:
>
> svn co svn+ssh://ben3@192.168.0.38/home/svn/myproject BBBB
> ben3_at_192.168.0.38's password:
> ben3_at_192.168.0.38's password:
> A BBBB/bewegtesbild
> A BBBB/bewegtesbild/sbf
> A BBBB/testsvnfolder
> A BBBB/eigen
> A BBBB/eigen/trunk
> A BBBB/eigen/trunk/test
> A BBBB/eigen/branches
> A BBBB/eigen/tags
> Checked out revision 3.
>
> It checks out into a folder BBBB, BUT on the machine where the
> repository is, not the remote machine.
Makes sense, doesn't it? You've ssh'd to the remote machine. Then on
that machine, you've issued a checkout command. The working copy is
checked out to the same machine on which you ran the checkout command.
> I was wondering now whether I somehow have to define the path BBBB
> differently like
> svn co svn+ssh://ben3@192.168.0.38/home/svn/myproject [url]http://
> 192.168.0.35/C:/IBBBB[/url] ???
No, the working copy is always checked out to the machine on which
you ran the checkout command. If you want to check out the working
copy on the machine whose IP address is 192.168.0.35, then run the
checkout command on the machine whose IP address is 192.168.0.35, not
on the machine whose IP address is 192.168.0.38 like you're doing.
> The problem is that this is not working and how would I define the
> path if the remote machine uses Windows as OS?
Use the svn command in the DOS command prompt on the Windows machine
to do the checkout. Or use TortoiseSVN as you've already done.
> Cheers,
> Ben
>
> PS: I started svn serve with:
>
> $ svnserve -d --foreground -r /home/svn
Since you're using the svn+ssh protocol (and not the svn protocol),
you don't need to start svnserve manually (and a copy you've started
manually won't be used). The svn+ssh protocol starts a copy of
svnserve for you when needed and closes it when it's done.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-07 22:57:32 CET