Subversion : svn+ssh:// : No repository found

Posted on November 8, 2006 by Sébastien

You can use “svn checkout svn://hostname.tld/project/” but you can’t check out your projects using svn+ssh:// ?

Let’s clear things, svn+ssh:// doesn’t require svnserve to run on the server as a daemon or through (x)inetd to work.

svn+ssh:// is only doing some kind of scp connection to the server.
That’s why you need to USE ABSOLUTE PATH WHEN USING svn+ssh

Usage :

svn only
svn checkout svn://hostname.tld/project/

svn+ssh
svn checkout svn+ssh://hostname.told/full/path/to/project/

22 thoughts on “Subversion : svn+ssh:// : No repository found”

Ben Lam on January 14, 2008 at 03:34 said:

Thanks for the tip about svn+ssh needing a full directory path. I had created a symbolic link within the user’s home directory to the svn repository located elsewhere under the assumption that svn would use the home dir as its relative path. So much for my assumptions.
Krishna Kishore on September 2, 2008 at 10:49 said:

Thanks alot for the much needed tip!! givving absolute path in svn+ssh solved
my problem checking out using ant script over ssh!!! Thanks again
Pascal Pollet on January 7, 2009 at 15:52 said:

Thanks, this tip was also very usefull to me
loommy on January 27, 2009 at 07:25 said:

thanks, it really helps me.
amandeep goyal on March 7, 2009 at 09:01 said:

hi there

i am working with svn on windows environment. tried ur concept on tsvn, bt failed. any help for implementing svn over ssh in windows environement will be really appreciated.
thanks….
Sébastien Wains on March 7, 2009 at 16:39 said:

Sorry mate, I don’t use Windows at all..
cyberklin on March 14, 2009 at 15:53 said:

thanks!
manuel on March 21, 2009 at 22:13 said:

hi
Thanks a lot for this tip…

cheers
Jonathan on October 23, 2009 at 19:29 said:

Thanks, been searching for this answer for almost an hour now.
icegood on December 5, 2009 at 22:39 said:

I don’t understand then why protocol calles “svn+ssh” and not simply ssh?!
icegood on December 5, 2009 at 22:40 said:

I don’t understand then why protocol called “svn+ssh” and not simply ssh?!
Dmitry Zh. on January 21, 2010 at 13:48 said:

Thanks a lot for this tip! It was more usefull for me.
owen on March 4, 2010 at 16:33 said:

you are damn genius~~~ Thank you~~
Michael Tan on March 14, 2010 at 07:35 said:

There is another way of setting up such that you don’t need the full path to project folder.

Check out step 7 (and possibly AllowUsers of step 5) of the following site:
http://www.scottboms.com/2008/10/macsvnsshserver/
Sébastien Wains on March 15, 2010 at 21:24 said:

Thanks Michael !
Didn’t know the trick
pierre on April 15, 2010 at 01:47 said:

You’re an alive god !! thanks
Scott F on August 12, 2010 at 19:36 said:

Thank you for this. It is amazing how many people do not know this. I spent 3 freaking hours trying to access my repository!!!
josh on September 1, 2010 at 18:45 said:

Did anyone get the repository path to work that was suggested by Michael? I’m still having no luck, even after trying steps 7 & 8 of that tutorial.

thanks!
Vlad on January 5, 2011 at 16:00 said:

Merci Sébastien! Your post did save me a few bang of head onto the keyboard on why didn’t the copy of svn on the new machine didn’t work?!? An svn info svn+ssh://host/svn/trunk gave me the infamous svn: No repository found in error message… and that’s because the rsync didn’t copy the symlink svn -> /home/svn… Thank you, thank you!
- Sébastien Wains on January 6, 2011 at 21:31 said:
  
  you’re welcome, de rien
UncleSiggy on June 20, 2011 at 22:43 said:

Many thanks for this tip. After hours of searching… it was right here all along!
carlo on November 24, 2011 at 16:52 said:

thank you so much!!! for the tip

Comments are closed.