On Thu, 2006-08-31 at 18:10 -0400, Duncan Murdoch wrote:
> On 8/31/2006 4:35 PM, Ernest L. Williams Jr. wrote:
> > On Thu, 2006-08-31 at 11:38 -0400, Duncan Murdoch wrote:
> >> On 8/31/2006 8:53 AM, Ernest L. Williams Jr. wrote:
> >>> On Thu, 2006-08-31 at 19:25 +1200, Gavin Lambert wrote:
> >>>> Quoth Ernest L. Williams Jr. <mailto:firstname.lastname@example.org>:
> >>>>> (1) I need to be able to do a svn update on a project that
> >>>>> someone on my team has already checkout. The problem: Their username
> >>>>> is stored in ".svn"
> >>>>> How did we handle this in CVS, well it was easy: cvs -d $CVSROOT
> >>>>> update
> >>>>> How do we make this happen in SVN?
> >>>>> I tried svn update --username williams but it still prompted
> >>>>> me for my colleague's password. By the way I am using svn+ssh.
> >>>> If you just hit enter when it asks for a password, then it should ask
> >>>> for a username as well.
> >>> Because we are using svn+ssh here is what happens:
> >>> [williams@ics-srv-phy1 svn-xaldev]$ svn update
> >>> tap@ics-srv01's password
> >>> The url that my colleague used to checkout a working copy has his
> >>> username there. Again, in CVS we were able to override this by
> >>> specifying cvs -d <my CVSROOT> update
> >>> So, how can we do something similar with SVN.
> >> You need to switch the WC to a URL that doesn't include the username.
> >> Then svn will use the currently logged-in username. If you don't want
> >> it to do that, you need to tell it to send a different name to ssh. You
> >> can configure that in your config file (see the "SSH authentication and
> >> authorization" section in the SVN book), or using the SVN_SSH
> >> environment variable.
> > Thanks for the reference in the book.
> > What exactly do I set the env variable to?
> > The following does not work.
> > export SVN_SSH=svn+ssh://williams@ics-srv01
> > Can you give me a working example?
> It's the command that svn will use to invoke ssh. So I can't really
> tell you what it should be on your system, but something like
> export SVN_SSH=/usr/bin/ssh -l williams
> should work. Then svn will use it as the prefix for the command that
> opens the tunnel to ics-srv01. As far as I know, this works just the
> way it does in cvs using CVS_RSH.
SVN_SSH would be the best solution since doing a svn --relocate plays
back and forth between developers. Every developer on the team would
have to first relocate and then do a svn update.
Thank you!!! This is actually the best solution and it works!!!
Now we are looking more like CVS. I can deal with this one.
[williams@ics-srv-phy1 svn-xaldev]$ export SVN_SSH='/usr/bin/ssh -l
[williams@ics-srv-phy1 svn-xaldev]$ svn update
Updated to revision 6747.
> Duncan Murdoch
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Sep 1 00:51:59 2006