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

Accessing repository with svn vs. svn+ssh

From: Rick Haller <rphaller_at_dstsystems.com>
Date: 2007-07-17 19:34:06 CEST

I created a repository in /svnrepos. The repository was populated with
projects using cvs2svn.
The filesystem is berkely-db. We won't be using Apache, just svnserve.
I am able to checkout projects using svn: and svn+ssh: and commit
changes. However, there appears to be a discrepency between
the two protocols.

To use svn: the command looks like svn checkout
svn://myserver/trunk/proj1
To use svn+ssh: the cmd looks like svn checkout
svn+ssh://myserver/svnrepos/trunk/proj1

If I don't use the commands as shown above, I receive the following errors.
svn: URL 'svn://myserver/svnrepos/trunk/proj1' doesn't exist
svn: URL 'svn+ssh://myserver/trunk/proj1' doesn't exist

Can someone explain the difference and why ? Is there a way to use
the svn: protocol so that it includes "svnrepos" in the url ?

Thanks,
Rick
rphaller@dstsystems.com
-----------------------------------------
This e-mail and any attachments are intended only for the
individual or company to which it is addressed and may contain
information which is privileged, confidential and prohibited from
disclosure or unauthorized use under applicable law. If you are
not the intended recipient of this e-mail, you are hereby notified
that any use, dissemination, or copying of this e-mail or the
information contained in this e-mail is strictly prohibited by the
sender. If you have received this transmission in error, please
return the material received to the sender and delete all copies
from your system.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 17 21:56:32 2007

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.