On 6/5/06, Jens Peters <firstname.lastname@example.org> wrote:
> > 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?
Sure, but I'm totally unfamiliar with language options -- do I just
change some regional settings or do I need to install a language pack
> > 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.
I don't believe that has changed at all, but I haven't tried or tested
anything like that. It is basically only an issue with the file://
protocol, right? Since server based installations can just 'recover'
the repository to get rid of the old shared memory files?
> > 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.
So the --username and --password parms on the commandline are ignored
if you have SSPI on? That does sound like a problem in Subversion's
auth code. Is there an issue filed?
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Tue Jun 6 01:49:03 2006