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

Subversion and FreeBSD permission problems

From: Darrell Blake <darrell.blake_at_gmail.com>
Date: Sun, 23 Mar 2008 16:01:25 +0000

I'm fairly new to FreeBSD and SVN but myself and a few developer
friends are undertaking a small project and I've been tasked with
getting the source control working. I decided to use FreeBSD for the
server for numerous reasons, stability and security among them. I'm no
stranger to Unix, however, I've been using Linux for a long time.

Anyway, my server is up and running and I've install svn via the ports
system (acquire from portsnap). I have set up a repository in
/usr/local/svn/repository via "svnadmin create
/usr/local/svn/repository" and imported a test project into it via
"svn import TestProject file:///usr/local/svn/repository/TestProject".
I then fired off the deamon server via "svnserve -d -r
/usr/local/svn/repository" which all seems to have worked well.

The thing is, I can't actually perform a checkout of the repository
via the server.

If I move into a temp directory and do "svn checkout
file:///usr/local/svn/repository/TestProject" it works fine but if I
do "svn svn://" I get an error stating "svn:
Can't connect to host '': Connection refused".

Also, if I try and use TortoiseSVN to browse the repository externally
I get an error stating "Error * Can't connect to host '':
No connection could be made because the target machine actively
refused it."

Does anyone have any idea what I could be doing wrong? I've been
reading the free O'Reilly Subversion book but I'm a bit clueless. I
suspect it's something to do with permissions on FreeBSD but I just
don't know enough about it =o)

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-23 17:01:46 CET

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.