You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Catto, James (Corp)" <Ja...@coates.com.au> on 2006/11/08 00:32:16 UTC
issue 1145 is resolved in subserve version 1.4.0?
Good morning folks,
I am trying to use Subversion 1.4.0. I have installed successfully, I
believe. There is now data in my repository.
$ svnserve --version
svnserve, version 1.4.0 (r21228)
compiled Sep 11 2006, 21:50:51
Copyright (C) 2000-2006 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
This product includes software developed by CollabNet
(http://www.Collab.Net/).
The following repository back-end (FS) modules are available:
* fs_base : Module for working with a Berkeley DB repository.
* fs_fs : Module for working with a plain file (FSFS) repository.
I am now trying to use svnserve under xinetd on a Linux box to allow
access to clients.
$ uname -a
Linux machineName 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:30:39 EST 2005 i686
i686 i386 GNU/Linux
I can access the repository as user 'svn' using:
$ svn list file://localhost/usr/share/svn/webapps
branches/
tags/
trunk/
and also:
$ svn list svn+ssh://localhost/usr/share/svn/webapps
svn@localhost's password:
branches/
tags/
trunk/
But I do not want to tunnel through SSH. And I get the following error
without it:
$ svn list svn://localhost/usr/share/svn/webapps
svn: Malformed network data
I have found reference to this error message at issue 1145 on SVN issue
tracker,
http://subversion.tigris.org/issues/show_bug.cgi?id=1145
This seems to indicate that it has been resolved in version 1.4.0.
Can you see what I am doing wrong? Am I using the wrong SVN version? Any
advice will be much appreciated.
Thanks
James
Coates, Coates Hire, Coates Prestige, Coates Shorco and Allied
Equipment are all registered Business Names of Coates Hire
Operations Pty Limited (ABN 99 074 126 971).
This email and any attachment may be confidential. If received in
error, please delete and inform us by return email.
Disclaimer:- Our company accepts no liability for the content of this
email, or for the consequences of any actions taken on the basis of the
information provided, unless that information is subsequently confirmed
in writing. Any views or opinions presented in this email are solely
those of the author and do not necessarily represent those of the
company. WARNING: Computer viruses can be transmitted via email. The
recipient should check this email and any attachments for the presence
of viruses. The company accepts no liability for any damage caused by
any virus transmitted by this email.
Please consider our environment before printing this email.
Re: issue 1145 is resolved in subserve version 1.4.0?
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 7, 2006, at 18:32, Catto, James ((Corp)) wrote:
> I am now trying to use svnserve under xinetd on a Linux box to
> allow access to clients.
>
>
>
> $ uname -a
>
> Linux machineName 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:30:39 EST 2005
> i686 i686 i386 GNU/Linux
>
>
>
> I can access the repository as user ‘svn’ using:
>
> $ svn list file://localhost/usr/share/svn/webapps
>
> branches/
>
> tags/
>
> trunk/
>
>
>
> and also:
>
>
>
> $ svn list svn+ssh://localhost/usr/share/svn/webapps
>
> svn@localhost's password:
>
> branches/
>
> tags/
>
> trunk/
>
>
>
> But I do not want to tunnel through SSH. And I get the following
> error without it:
>
>
>
> $ svn list svn://localhost/usr/share/svn/webapps
>
> svn: Malformed network data
>
>
>
>
>
> I have found reference to this error message at issue 1145 on SVN
> issue tracker,
>
>
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=1145
>
>
>
> This seems to indicate that it has been resolved in version 1.4.0.
Bug 1145 seems to have been fixed in revisions 6052 and 6055 in May
2003. It also indicates it only applies to tunnel mode, which I think
means tunneling through SSH, which you've said works for you. You're
only having problems with non-tunneling mode, which that bug does not
talk about.
How are you starting the svnserve process? Note that when using the
svn+ssh protocol, you do not start svnserve yourself, but svn starts
it for you when your connection opens, and stops it when the
connection closes. With the svn protocol, on the other hand, you must
have an svnserve daemon already started, and running all the time.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org