On 6/6/07, Jerome Benezech <email@example.com> wrote:
> Hi All,
> I finally got to compile subversion 1.4.3 on a
> GNU/Linux server and now run into problems trying to
> access it.
> I am running subversion on a shared host so it is
> installed in my home directory and svnserve is started
> with my user account.
> When starting snvserve like this:
> svnserve -d -r /home/user/svn/repositories
> I can connect to my repository fine using either
> file:/// or svn://
> svn ls svn://firstname.lastname@example.org/myproject works fine
> Now I would like to use SSH tunelling for remote
> access. So I start svnserve like this:
> svnserve -t -r /home/user/svn/repositories &
You don't need to start the svnserve when trying to access the repository
I believe the client sends to command over to the server to start svnserve.
This usually means that svnserve should be in the default system path in
order to start svnserve. And by default (unless you do some tricks:
http://svn.collab.net/repos/svn/trunk/notes/ssh-tricks) it starts the server
without the -r param. So the client has to provide the full path in the URL.
Then I try to access the repository from my server,
> using the same user account:
> svn ls svn+ssh://email@example.com/myproject
> There I get the "No repository found" error. I tried
> using several URL
> svn ls
So, as explained above, this is the right way to access the repository using
However, I am lost why it could not find the repository. The only remotely
possible reason I can think of is that the repository is not readable to
'user'. Usually the problem in such instances is when svnserve is not in the
system path and it could not start it when executing the command. But in
that case the error is not "No repository found". That error usually means
just that -- no repository found.
> None of these work. I really don't know where to go
> from there and any help would be great.
Received on Thu Jun 7 08:22:36 2007