[OS X TeX] svnX and Leopard [OT]
David Watson
dewatson at mac.com
Mon Jun 16 23:18:56 CEST 2008
On my older computer I had set up svnserve through Fink, and this is
what I had prepended to my authorized key:
command="/sw/bin/svnserve -t --tunnel-user=myusername -r /Volumes/
SVNVolume/SVNRoot",no-port-forwarding,no-agent-forwarding,no-X11-
forwarding,no-pty
So it would appear that you do need to point to your svnserve
application on the server machine. I believe the tunneled user has to
have permissions on the repository, and the extra fluff was there to
ensure that the subversion user was sufficiently limited in terms of
shell/X11 capabilities, which you can read all about in the excellent
manual.
I have never used svnX, and indeed everything I have done is from the
CLI. I recall that there were other ways of setting up subversion than
through svn+ssh, and perhaps svnX uses one of those other
authorization methods.
Good luck,
David
On Jun 16, 2008, at 11:36 AM, Alan Munn wrote:
> Hi, I sent the following to the subverion list, but noone replied,
> probably because it's too Mac specific. Since I know some of us
> here use svn, perhaps someone here has encountered this problem and
> knows how to solve it.
>
> I use svnX on Macs to access my repositories using svn+ssh. Now with
> a new machine running OS 10.5.3 I get the following error:
>
> tchs: svnserve: Command not found
> svn: Connection closed unexpectedly
>
> I can access the repository from the command line, but not through
> the client. I've set up a dsa key specifically for subversion, and
> added it to the authorized keys on the server machine. This works
> for two other Macs running 10.4. (One these machines I use
> sshagent, but I understand this is not required on OS 10.5.
>
> In the authorized keys file on the server side the key for
> subversion includes the prefix "command=/usr/local/bin/svnserve -t" .
>
> Should this command have a path that is to svnserve on the server
> side? (The server is running 10.4, so svn is in /usr/local/bin
> whereas svn is now part of OS 10.5, so on the client machine it's
> in /usr/bin. Could this be a source of the problem?
>
> Any help much appreciated.
>
> Alan
More information about the macostex-archives
mailing list