RE: Locale problem: Can't convert string from native encoding to 'UTF-8'

I was able to solve this problem by rebuildling subversion from source on Suse 9.3. I think they may have built against their own apr libs, and something wasn't right. All is right in the world.
 
Thanks
Rich
 
P.S. It was pretty easy to build, esp with the included apr sources - kudos to those responsible!

________________________________

        From: Richard Sheldon [mailto:richardsheldon@comcast.net]
        Sent: Thursday, October 20, 2005 8:11 AM
        To: 'users@subversion.tigris.org'
        Subject: Locale problem: Can't convert string from native encoding to 'UTF-8'
        
        
        All,
         
        I have been having the same problem as David has. I've setup the most noddy example I can think of, to rule out as many things as possible. Here's the setup
         
        Client
            - Windows XP Pro, SP2
            - Locale - American English
            - Subversion 1.2.3
            - TortoiseSVN 1.2.4
         
        Server
           - Suse Linux 9.3 Pro
           - Subversion 1.2.3
           - svnserve
           - LANG settings tried en_US.UTF-8, C
         
         
        I created a single directory, with no contents, and tried to import this into the repository, and got the following message:
         
        $ svn import -m message repo2 svn://fubar/repos
        svn: Transaction cleanup failed
        svn: Can't convert string from native encoding to 'UTF-8':
        svn: Ph?\17Xx?\21h?\1 ¢À
         
        I tried this both from the command line (bash shell under cygwin), and from TortoiseSVN, and got the same resultin both cases. I tried changing the LANG of the server to "C" and restarting, but no joy.
         
        I'm almost at a loss here. I've spent the last 4 hours screwing around trying to get this to work.
        One thing I have noticed is that the SUSE version of subversion is NOT linked against libiconv - should it be for the conversions to work? (although I don't know what it's converting, as I can't see any non-ASCII characters in the dir name or log message). I guess the next step is to build from scratch.
         
        Suse 9.3 doesn't appear to have the iconv library, so I guess I'll have to do that one too (and perhaps the apr). Sheesh!
         
        Any help or advice would be appreciated. It does seem suspicious that both David and are having problems on Suse systems.
         
        Thanks
        Rich
Received on Thu Oct 20 16:57:24 2005