I'm trying to set up an SVN server on Linux (ubuntu, if it matters) and getting behavior that seems strange. When I'm on the actual server and try to just do svn list file://... it works and lists my test repo I have set up, but when trying to connect remotely from another server with svn list svn://... I get "No repositories found". All the google results I got told me it's usually an issue with the svnserve root path, but I've checked that three times now, and I know its right.
|
|
|||
|
|
|
I assume you're running svnserve if you're trying to access the svn using svn:// - check if svnserve is running (I know this is silly but sometimes it does happen, being able to connect to svn using file:// does not indicate if svnserve is running and configured propertly). To configure propertly svnserve: check this tutorial I would suggest you configure SVN to be accessed by http - here how you can do that |
|||||
|
|
|
I suggest using ssh+svn:// or https:// for accessing Subversion repositories, based on whether you want local users on your subversion server. In either case, my preference is for https://. You should find these more flexible than using svnserve. |
|||||
|
While I run SVN through Apache2 (HTTP + SSL), I do recall having difficulty debugging what's going on, as the SVN error messages can be a tad too generic. |
|||
|
|