On Thu, 2006-08-31 at 08:28 -0600, Gary Thomas wrote:
> 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 should be able to fix this by doing 'svn switch --relocate '
> which will change the repository information for your tree. Then
> you can run 'svn update'
That also does not work:
[williams@ics-srv-phy1 svn-xaldev]$ svn switch --relocate svn
+ssh://tap@ics-srv01/sns/ADE/svnTop/svnroot/xaldev/trunk svn
+ssh://tap@ics-srv01/sns/ADE/svnTop/svnroot/xaldev/trunk
tap@ics-srv01's password:
Appears that anything done relative to the working copy uses what is
stored in ".svn"
switch (sw): Update the working copy to a different URL.
usage: 1. switch URL [PATH]
2. switch --relocate FROM TO [PATH...]
1. Update the working copy to mirror a new URL within the repository.
This behaviour is similar to 'svn update', and is the way to
move a working copy to a branch or tag within the same repository.
2. Rewrite working copy URL metadata to reflect a syntactic change
only.
This is used when repository's root URL changes (such as a schema
or hostname change) but your working copy still reflects the same
directory within the same repository.
Valid options:
-r [--revision] arg : ARG (some commands also take ARG1:ARG2
range)
A revision argument can be one of:
NUMBER revision number
"{" DATE "}" revision at start of the
date
"HEAD" latest in repository
"BASE" base rev of item's working
copy
"COMMITTED" last commit at or before
BASE
"PREV" revision just before
COMMITTED
-N [--non-recursive] : operate on single directory only
-q [--quiet] : print as little as possible
--diff3-cmd arg : use ARG as merge command
--relocate : relocate via URL-rewriting
--username arg : specify a username ARG
--password arg : specify a password ARG
--no-auth-cache : do not cache authentication tokens
--non-interactive : do no interactive prompting
--config-dir arg : read user configuration files from
directory ARG
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Aug 31 18:48:42 2006