Stefan Küng <tortoisesvn@gmail.com> wrote on 01/06/2006 02:16:51 PM:
> Since we've released TortoiseSVN-1.3.0-RC1, I've already received
> several crash and bug reports.
>
> What I could fix, I already did. But there are two issues left which are
> outside TortoiseSVN but in Subversion (and maybe neon).
>
> * a crash happens if you copy an unversioned file
> * computers not part of the same domain as a repository can't connect,
> because the SSPI authentication doesn't work. This also happens if your
> windows username/password is different from the one you use on the
> repository and the repository is hosted on a windows domain.
>
> So, the first is very annoying and is a "bad user impression".
> The second however is more serious: you can't use TortoiseSVN 1.3.0 at
> all to connect to some repositories.
>
> I'm thinking of holding back the 1.3.0 release until those issues are
> resolved (doesn't need to be an official released fix, I would consider
> patching Subversion/neon myself if necessary).
>
> What do you guys think?
It doesn't sound like a bad idea. However, since you control the build of
Neon, can't you just remove the
#define HAVE_SSPI from the config.hw file for Neon?
Or even just build with Neon 0.24.7?
Nothing is forcing you to use 0.25.4 or SSPI.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Jan 6 20:25:40 2006