On 7 September 2012 21:23, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 07.09.2012 14:14, Simon Large wrote:
>> On 7 September 2012 12:42, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
>>> On Fri, Sep 7, 2012 at 9:28 AM, Simon Large <simon.tortoisesvn_at_gmail.com> wrote:
>>>> Hi Stefan,
>>>> The SVN command line tools bundled with TSVN do not work properly with
>>>> SASL-secured repositories. I have a local working copy checked out
>>>> against such a repo and tried to update it:
>>>> TSVN->Update works OK
>>>> Wandisco vanilla svn 1.7.6 client works OK
>>>> TSVN 184.108.40.20627 bundled svn fails
>>>> svn up
>>>> Updating '.':
>>>> svn: E210007: Unable to connect to a repository at URL
>>>> svn: E210007: Cannot negotiate authentication mechanism
>>>> svn --version
>>>> svn, version 1.7.7-dev (under development)
>>>> compiled Aug 25 2012, 04:05:32
>>>> I guess there is something different in the build options for our
>>>> command line tools.
>>>> I can give you access to a repository for testing if that will help.
>>> maybe this:
>> So how does TSVN work, and SVN built using the same dlls doesn't?
> TSVN calls sasl_set_path() so sasl doesn't have to use the registry to
> find the dlls but looks in the path we specify.
OK, I see. Maybe the Wandisco installer is setting that registry key,
in which case our installer should too if the command line tools are
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-09-09 00:08:25 CEST