You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Otto Visser <o....@tudelft.nl> on 2006/03/27 12:32:12 UTC
issue with relocating
Hi,
As we where switching servers here I noticed the following:
Relocating from server 1 to server 2 with "svn switch --relocate
http://server1 https://server2": svn assumes as username the username of
the currently logged in user. This is a debatable default for checking
out new repositories and even more debatable for switching repositories.
Personally; I don't like it, but that just me perhaps :)
Now after this relocation I did an "svn up" and this is where the issue
starts: it _again_ asks for the username/password and again assumes the
logged in username. I think it should have saved this username/password
at the relocate.
Otto.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: issue with relocating
Posted by Julian Foad <ju...@btopenworld.com>.
Otto Visser wrote:
> Some other minor issue is perhaps that if I do a switch --relocate foo
> bar but foo is not in use that svn does not give an error/warning. Our
> server is called foo but has an alias baz which is the one I apperently
> used to checkout long ago. This being the first relocate with svn I did
> I thought the operation was succesfull because there were no complaints.
Like this example (in a working copy checked out from somewhere under
file:///home/julian...):
$ svn switch --relocate file:///abc file:///def
(no output; exit code 0)
I think this is a bug. Please could you file it.
- Julian
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: issue with relocating
Posted by Otto Visser <o....@tudelft.nl>.
On Tue, 2006-03-28 at 12:14 -0500, Brad Kittenbrink wrote:
> Otto Visser wrote:
> > Hi,
> >
> > As we where switching servers here I noticed the following:
> >
> > Relocating from server 1 to server 2 with "svn switch --relocate
> > http://server1 https://server2": svn assumes as username the username of
> > the currently logged in user. This is a debatable default for checking
> > out new repositories and even more debatable for switching repositories.
> > Personally; I don't like it, but that just me perhaps :)
> >
> Just to clarify, are you suggesting that a different default would be
> worth debating, or that there be no default?
I'd personally opt for no default for two simple reasons. One being less
garbage in the logs and the second is that the server I was talking
about has a firewall which blocks me out after 2 wrong login attempts.
SVN already does the first for me.
But even if you want a default: what's the "better" default; the current
username or the username used for the old location?
> > Now after this relocation I did an "svn up" and this is where the issue
> > starts: it _again_ asks for the username/password and again assumes the
> > logged in username. I think it should have saved this username/password
> > at the relocate.
> >
> Is "svn switch --username foo" unsatisfactory in some way?
No; my point is that if SVN is asking for a username/password
combination for the new location while doing the relocate, that it
should save this the same way it would after the first succesfull
update. Again with the server blocking me out after 2 unsuccesfull
logins: I got blocked at this point, one try at relocate and one try at
update. (The succesfull login in between does not reset that counter)
Some other minor issue is perhaps that if I do a switch --relocate foo
bar but foo is not in use that svn does not give an error/warning. Our
server is called foo but has an alias baz which is the one I apperently
used to checkout long ago. This being the first relocate with svn I did
I thought the operation was succesfull because there were no complaints.
Otto.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: issue with relocating
Posted by Brad Kittenbrink <br...@windwardmark.net>.
Otto Visser wrote:
> Hi,
>
> As we where switching servers here I noticed the following:
>
> Relocating from server 1 to server 2 with "svn switch --relocate
> http://server1 https://server2": svn assumes as username the username of
> the currently logged in user. This is a debatable default for checking
> out new repositories and even more debatable for switching repositories.
> Personally; I don't like it, but that just me perhaps :)
>
Just to clarify, are you suggesting that a different default would be
worth debating, or that there be no default?
> Now after this relocation I did an "svn up" and this is where the issue
> starts: it _again_ asks for the username/password and again assumes the
> logged in username. I think it should have saved this username/password
> at the relocate.
>
Is "svn switch --username foo" unsatisfactory in some way?
-Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: issue with relocating
Posted by mark benedetto king <mb...@lowlatency.com>.
On Mon, Mar 27, 2006 at 02:32:12PM +0200, Otto Visser wrote:
> Hi,
>
> As we where switching servers here I noticed the following:
>
> Relocating from server 1 to server 2 with "svn switch --relocate
> http://server1 https://server2": svn assumes as username the username of
> the currently logged in user. This is a debatable default for checking
> out new repositories and even more debatable for switching repositories.
> Personally; I don't like it, but that just me perhaps :)
>
> Now after this relocation I did an "svn up" and this is where the issue
> starts: it _again_ asks for the username/password and again assumes the
> logged in username. I think it should have saved this username/password
> at the relocate.
>
I believe that this was issue 2360, which was fixed in r19038.
Can you reproduce using the trunk?
--ben
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org