Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

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.

share|improve this question

3 Answers 3

up vote 3 down vote accepted

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

share|improve this answer
    
HTTP tutorial worked, thanks a lot. –  Alex S Aug 10 '09 at 14:45
    
Shadow - you are welcome –  Adam Benayoun Aug 11 '09 at 9:45
  • Is the svnserve run with correct permissions?
  • Have you checked the logs from svnserve (usually /var/log/ somehwere).
  • Try running the client with a verbose or debug setting (-v and -d in most programs).
  • Same, but for the server svnserve client.
  • Are you testing from localhost? If so, check that connecting over loopback (interface name lo) actually is permitted.

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.

share|improve this answer

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.

share|improve this answer
    
I got the impression from my limited reading that http(s) was only for reading - i.e. you can't commit changes using it. Do you know of any setup information for your suggestions? –  Alex S Aug 10 '09 at 7:45
    
I strongly support what David said, I'd configure your repositories to be accessed via https - read my answer below –  Adam Benayoun Aug 10 '09 at 7:50

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.