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:ernesto@ornl.gov>:
>> > (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.
Duncan Murdoch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 31 19:36:45 2006