Weblog entry #5 for drgraefy
See all weblog entries made by drgraefy.
#5
svn+ssh username issues
Posted by drgraefy on Tue 30 Oct 2007 at 14:32
I was having trouble using svn+ssh when the username differed on the local and remote hosts. For instance, if the user on the local machine is 'ape' and the user on the local machine is 'chimp', the following would fail:
ape@local:0:~$ svn co --username chimp svn+ssh://remote/path/to/repoAfter a little bit of research, I found a relevant debian bug report filed against subversion. In it the reporter mentions something that works for him, that I confirmed does the trick: the username goes in the url:
ape@local:0:~$ svn co svn+ssh://chimp@remote/path/to/repoClearly this is still a bug with the svn client for not passing the username argument properly, but at least there's an easy way to get around it.
Comments on this Entry
Posted by dkg (216.254.xx.xx) on Tue 30 Oct 2007 at 15:04
[ Send Message | View dkg's Scratchpad | View Weblogs ]
[ Send Message | View dkg's Scratchpad | View Weblogs ]
I think you could also set up your ~/.ssh/config with a stanza to handle this:
Host remote User chimpThen you can run svn without any explicit reference to the username.
[ Parent | Reply to this comment ]
Posted by Anonymous (147.210.xx.xx) on Wed 25 Jan 2012 at 08:26
It's a little bit late, but thank you :-)
[ Parent | Reply to this comment ]
Posted by Anonymous (66.51.xx.xx) on Sun 18 Nov 2007 at 07:25
> Clearly this is still a bug with the svn client for not
> passing the username argument properly, but at least
> there's an easy way to get around it.
The --username argument is for the Subversion username,
which is not necessarily the same as the login name that SSH
needs.
--
Aaron Brown
> passing the username argument properly, but at least
> there's an easy way to get around it.
The --username argument is for the Subversion username,
which is not necessarily the same as the login name that SSH
needs.
--
Aaron Brown
[ Parent | Reply to this comment ]