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

AW: Subversion Tools

From: Hunkel, Manfred <M.Hunkel_at_t-systems.com>
Date: 2004-08-06 10:40:50 CEST

Christian,

Been through purgatory solving, most likely, the same or at least a very related problem. Being German, I'm likely to use umlauts in filenames, etc. :-}

I'm assuming that what you cite as " frmBestand_bersicht.frm" really reads "frmBestandÜbersicht.frm". In my case, the causes for the error message you're citing were as follows:

1. My builds of SVN/apr/apr-util/Apache (running on NetBSD) weren't linked against libiconv. This will cause all svn utilities (i.e. svn, svnlook, ..), which are being run server-side, to fail with this error message, *even if you've correctly set LC_CTYPE*!
LC_CTYPE in my case is set to "de_DE.ISO8859-1".

2. Even if your installation is linked against libiconv and LC_CTYPE has been correctly set for the shell your running them from, server-side utilities *still* will fail when called from an environment where LC_CTYPE is not defined. Example: I'm using WebSVN to
access our repositories. WebSVN uses a set of PHP-scripts which in turn call svnlook server-side, but the invocation environment of svnlook via WebSVN does not contain LC_CTYPE, causing svnlook to fail with that error when it hits the first filename with an umlaut.

So: Check if your installation (apr-util, in particular, I think) uses libiconv. If so, provide a proper definition of LC_CTYPE. If all this is as it should be, make sure that the environment of the process that calls svn clients also has a definition of LC_CTYPE.

;-) -Manfred

| -----Ursprüngliche Nachricht-----
| Von: Barkey, Christian LUX [mailto:Christian.Barkey@HVB.lu]
| Gesendet: Donnerstag, 5. August 2004 20:09
| An: users@subversion.tigris.org
| Betreff: FW: Subversion Tools
|
|
| > > "Barkey, Christian LUX" <Christian.Barkey@HVB.lu> writes:
| > > > I ran into problems with my german developers who commented
| > > > the vss with german umlaute. These where not handled by the
| > > > svn client I use and the script failed.
| > >
| > > The svn client should be able to handle these; if it didn't, it may be
| > > that your locale was not set right. The exact error would help
| > > diagnose this better.
| >
| >
| > attached you can see the output of the vss2svn script.
| >
| > --------------------------------snip------------------------------------------------
| >
| > Could not perform SVN add of frmBestand_bersicht.frm at vss2svn-for-exe.pl line
| 511.
| >
| > ******************************FATAL
| ERROR********************************
| >
| ********************************************************************
| *****
| >
| > A fatal error has occured. The output from the last VSS or SVN command is
| > below, if available.
| >
| > See C:\repository\_vss2svn\logfile.txt for more information.
| >
| > LAST SVN COMMAND:
| > add "frmBestand_bersicht.frm"
| > svn: Safe data:
| > "frmBestand"
| > ... was followed by non-ascii byte 220.
| >
| > Non-ascii character detected (see above), and unable to convert to/from UTF-8
| >
| >
| > --------------------------------snap------------------------------------------------
| >
| > Maybe a stupid question: How can locale be set?
| >
| > Thanks for your help.
| >
| > Best Regards
| > Christian
| >

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 6 10:43:06 2004

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