[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: 1.4.0-rc1 tarballs up for testing/signing

From: Jens Peters <jpeters7677_at_gmx.de>
Date: 2006-06-05 17:00:28 CEST

> I don't much about language issues, but my understanding is
> that if you build using --with-libintl then it should work fine.

The gettext stuff is working fine, the subversion messages are translated
correctly. It is rather an encoding issue. The official MSVC6 build and my
VS2003 build have no problems showing the german 'umlaute' on the console,
but I never got it working with VS2005.

See also this thread:

Could you please try the german output once with your build?
> I'm not sure what you mean here -- I rebuild everything from
> source and haven't had to do that.

See this thread:

With svn 1.3 and BDB 4.3 you have to use this directive in VS2005 otherwise
the bdb shared memory files are incompatible with bdb memory files of a svn
build compiled with an older VS or gcc.
> No, I haven't tried USE_SSPI. You might try asking on the TSVN list
> -- I believe they have lots of users using it.

Sorry, the correct name is HAVE_SSPI in neon. Stefan (The TSVN Stefan) has
disabled this directive in his build, because svn 1.3 is not able to fall
back to basic authentication if you use a server with mod_dav_sspi and a
sspi enabled client. Otherwise svn --username --password ignores the given
credentials and uses everytime the credentials from the current user. This
is the case with the official build and essentially the problem of this


My question is if this would still be the case with the upcoming 1.4 release
if I would define HAVE_SSPI.

Thanks for your anwsers.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jun 5 17:01:32 2006

This is an archived mail posted to the Subversion Dev mailing list.