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

Re: Help - svn: vs svn+ssh:

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Mon, 7 Jul 2008 20:40:29 -0500

On Jul 7, 2008, at 19:50, Robert Schwalbe wrote:

>> I have an existing repository on the LAN. The following command:
>> svn list svn://
>> produces:
>> branches/
>> tags/
>> trunk/
>> but the following command:
>> svn list svn+ssh://
>> produces:
>> svn: No repository found in 'svn+ssh://'
>> I can work and get by with the first version just fine (obviously)
>> but I
>> just can't bring myself to explain why the later fails.
>> The server and client are both 1.5. Server is running on OS X
>> Server 10.5.4.
>> Any pointers to documentation or other suggestions would be very
>> welcomed.
>> I'm not afraid of being told to RTFM, but I don't think that's the
>> case here.
> Oh, let me add:
> I can "ssh" and log in successfully.
> svnserve gets started with the following arguments:
> /usr/local/bin/svnserve --inetd --root=/Volumes/data/

The different repository access methods get configured differently.
svn:// access is configured differently from svn+ssh:// access is
configured differently from http:// and https:// access.

When you manually start svnserve for svn:// access you add a --root
parameter to tell it where the repositories are.

When using svn+ssh:// it does not make use of the svnserve you have
manually started. Instead it starts a new svnserve just for that
connection. You must tell it to use the --root parameter there too.
See the book:


To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-08 03:41:20 CEST

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.