SVN cannot set LC_CTYPE locale

Question

I started getting the following error when I use SVN on my server:

svn: warning: cannot set LC_CTYPE locale svn: warning: environment variable LC_CTYPE is UTF-8 svn: warning: please check that your locale name is correct 

I suppose there might be something wrong with my svn client (using the Versions app) and the svn server ...

How can I make this warning disappear from the server forever whenever I use such commands?

Answer 1

Check output

 locale -a 

If the locale that SVN binds to is not set, you can set it.

You may need to do:

 sudo apt-get install language-pack-en-base 

followed by one of (depending on the exact SVN error, your first case):

 sudo locale-gen UTF-8 sudo locale-gen en_GB.UTF-8 sudo locale-gen en_US.UTF-8 

Alternatively, as Ankit writes:

 export LC_ALL=C 

may work (in your current session or in your .profile).

Answer 2

Although setting LC_CTYPE to an empty value worked for me, the main reason was that the Terminal application on my Mac set locales at startup, even when I SSH to another system.

This can be fixed in Terminal> Preferences:

• Select the “Profiles” tab and select “Advanced” in the sub-tabs
• Uncheck "Set locale environment variables at startup"

Answer 3

If you want to fix this, set the LC_ALL variable manually.

To make it permanent, simply edit the file "/ etc / environment" and add the line:

 LC_ALL=C 

Save the file and exit the editor. To use it, you must exit the current shell session. The next time you log in, the problem with SVN will disappear.

Answer 4

The LC_ALL and LANG settings did not work for me, but LC_CTYPE.

 LC_CTYPE=en_US.UTF-8 

Answer 5

In Debian Jessie :

I ran:

 sudo dpkg-reconfigure locales 

Added and installed the missing locale. Then it worked.

Answer 6

commenting out lines using SendEnv LANG LC_* in / etc / ssh / ssh _config helps me (openSUSE)

Answer 7

This is because the correct locales are not created on your system.

Uncommented lines that you want to support in /etc/locale.gen

For example:

 en_GB.UTF-8 UTF-8 en_US.UTF-8 UTF-8 ru_RU.UTF-8 UTF-8 

and then run sudo locale-gen

Answer 8

We had this problem in our company when using IntelliJ. My colleague just fixed it.

For us, the problem was the SendEnv LANG LC_* in /etc/ssh/ssh_config . When I commented on this line, everything was fine.

Answer 9

I found that combining multiple answers allows you to get the right behavior.

• We must set the correct locale (localadm for sunos, locale-gen for linux)
• We must set LC_ALL to the appropriate locale.

It depends on what file names you have in the source tree. For example, I have English, Hebrew and Arabic. en_US.UTF-8 works for me "C" on its own led to files that I could not update.

Answer 10

For iTerm2:

Profiles → Open profiles ... → Change profiles ... → Terminal → Cancel Automatically set language variables