Unable to checkout a project I don;t have locally from svnserve using Subclipse or TortoiseSVN from outside my network

[Robert Elliot <ro...@dial.pipex.com>]

Hello all,

I hope this isn't something asked everyday; I have looked for an answer.

I am running Subversion on a Windows Small Business Server 2003 box on my local network, using
svnserve wrapped as a service using SrvAny.  I am accessing it from another machine on my network
running the Subclipse Eclipse plugin as my client.  And it works fine.

However, when I use it or TortoiseSVN from outside my network I get strange behaviour.  I can log
in, browse the remote repository and, if I create a new Eclipse project locally, check it in.  I can
also alter an item in this project I have created locally and checked in, check that in, and then
revert to the older version.  But I can't check projects that don't yet exist on the client out.

Has anyone encountered this issue before?  It can't be a firewall issue, as not only do I have 3690
open but I can clearly communicate across the firewall fine - with the one exception of checking new
projects out.

Thanks for any help,
Rob

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: Unable to checkout a project I don;t have locally from svnserve using Subclipse or TortoiseSVN from outside my network

[Robert Elliot <ro...@dial.pipex.com>]

> -----Original Message-----
> From: Ulrich Eckhardt [mailto:eckhardt@satorlaser.com]
> Sent: 24 May 2006 10:22
> 
> 
> It's not exactly clear what you did and what happened, seeing the
> actual error
> messages would be beneficial, but I can guess one situation that might
> cause
> weird behaviour.

I never received an error message; both Subclipse and TortoiseSVN both
hung.  I had to kill the Eclipse process to get Subclipse to stop,
though I was able to close the window on TortoiseSVN.

The exact sequence of events:
1) Installed Subversion on server, using svnserve on port 3690
2) Created new Eclipse project on workstation on local network
3) Using Subclipse on the workstation, added it to the repository on the
server
4) Using a laptop external to my network, with Eclipse & Subclipse,
browsed the repository on the server.  Able to view the project, its
folders and files in the browser.
5) Attempted to check the project out onto the laptop.  Subclipse
console shows the following command:

checkout -r HEAD svn://www.mydomain.org.uk/CodeRepository/testProject

and hangs.  No error message.  Had to kill the process tree.

I then tried the following:

1) Created another new project testProject2 on the laptop (so outside
the network)
2) Shared it to the repository using Subclipse over the internet.  It
checked in fine.
3) Updated files, checked them in, reverted to previous versions - all
fine
4) Deleted the project locally.  Browsed the repository and attempted to
check testProject2 out of the repository again.  Same problem as before.

I then installed Tortoise on the external machine, thinking it might be
a Subclipse issue.  Right clicked on a folder and chose "SVN
Checkout...".  Entered the url as
svn://<url>/CodeRepository/testProject2 and put in a local directory of
C:\testProject2.  Clicked OK and agreed to create the C:\testProject2
folder.  A window appears headed "testProject2 - TortoiseSVN
Checkout..." which is clearly meant to show a table with Action, Path
and Mime type fields - but nothing in it.  It has a greyed out OK button
and an active Cancel button - but clicking Cancel does nothing.  After a
long period of time I closed the window using the windows X.

> 
> The problem arises when the server-name is different when accessing it
> from
> the local network and from outside. In that case, Subversion doesn't
> know
> that both are in fact the same machines and the same repositories and
> rightly
> refuses to check into one repository something that comes from another
> repository.

The server's local name is mydomain-server, and it's accessible over the
net at www.mydomain.org.uk.

Would that still be a problem if I was checking the project in for the
first time from outside the network as well as trying to check it out
from outside the network?

> There are two ways around this that I know of:
> 1. Use 'svn switch --relocate' to inform SVN of the 'moved'
> repository.
> 2. Use a virtual tunnel. This works by installing a tunnel from a port
> on your
> own machine to the port of the server. That way, for subversion it is
> always
> a repository on localhost but the tunnel redirects traffic to the real
> server
> via whatever transport is applicable.

Thanks very much, I'll give these a go when I get home.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Unable to checkout a project I don;t have locally from svnserve using Subclipse or TortoiseSVN from outside my network

[Ulrich Eckhardt <ec...@satorlaser.com>]

On Wednesday 24 May 2006 11:07, Robert Elliot wrote:
> I am running Subversion on a Windows Small Business Server 2003 box on my
> local network, using svnserve wrapped as a service using SrvAny.  I am
> accessing it from another machine on my network running the Subclipse
> Eclipse plugin as my client.  And it works fine.

Okay.

> However, when I use it or TortoiseSVN from outside my network I get strange
> behaviour.  I can log in, browse the remote repository and, if I create a
> new Eclipse project locally, check it in.  I can also alter an item in this
> project I have created locally and checked in, check that in, and then
> revert to the older version.  But I can't check projects that don't yet
> exist on the client out.

It's not exactly clear what you did and what happened, seeing the actual error 
messages would be beneficial, but I can guess one situation that might cause 
weird behaviour. 

The problem arises when the server-name is different when accessing it from 
the local network and from outside. In that case, Subversion doesn't know 
that both are in fact the same machines and the same repositories and rightly 
refuses to check into one repository something that comes from another 
repository.

There are two ways around this that I know of:
1. Use 'svn switch --relocate' to inform SVN of the 'moved' repository.
2. Use a virtual tunnel. This works by installing a tunnel from a port on your 
own machine to the port of the server. That way, for subversion it is always 
a repository on localhost but the tunnel redirects traffic to the real server 
via whatever transport is applicable.

Uli

****************************************************
Visit our website at <http://www.domino-printing.com/>
****************************************************
This Email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this Email in error please notify the system manager.

This footnote also confirms that this Email message has been swept by MailSweeper for the presence of computer viruses.
****************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org