On Jun 30, 2008, at 11:20, Andrew Johnson wrote:
> I'm having a problem checking out a project with a svn:external
> property. We're using the svn+ssh protocol which we find convienient
> as an existing user group can be used to control access to the repo.
>
> I am hitting a problem when trying to checkout from account that
> doesn't exist on the server. i.e.
>
> foo_at_other-server-1 > svn co svn+ssh://a.johnson@svn-server-1/myproj/
> A afile.cpp
> A bfile.cpp
> U utilities
>
> Fetching external item into 'utilities/src'
> foo_at_svn-server-1 password:
>
> a.johnson has an account on svn-server-1. foo however does not. It
> appears that for each external project a new connection is made to the
> server. Unfortunately only the first connection uses the username
> passed in the URL, subsequent ones default to current session (i.e.
> foo in the above case).
>
> I have managed to override this behaviour using the SVN_SSH
> environment variable (e.g. SVN_SSH="ssh -l a.johnson") but this is not
> a practical solution as it involves wrapping the client and
> preprocessing the URL in order to set the environment variable
> (yuck!). Is there a workaround which allows the username supplied in
> the URL to be passed to the checkout for each external project?
Are you using the new relative externals available as of Subversion
1.5? If not, that may help.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-30 21:13:10 CEST