4 Mar
2006
4 Mar
'06
11:53 p.m.
I set up a Vcs install in another machine today, and I ran into a
new problem :
~/src/nolimips % vcs-svn status
vcs: error: command: svn status --
vcs: error: exit: 1
vcs: error: stderr: svn: error: cannot set LC_ALL locale
vcs: error: stderr: svn: error: environment variable LC_ALL is en_US
vcs: error: stderr: svn: error: please check that your locale name is
correct
vcs: error: command failed
However, after the installation of fresh new en_US locale (thank you,
dpkg-reconfigure!), the error vanished.
Does this means that Vcs has a dependency on a en_US locale?
(`vcs --check' doesn't mention it, BTW.)
6 Mar
6 Mar
10:05 a.m.
On 3/4/06, Roland Levillain <roland(a)lrde.epita.fr> wrote:
Yes there is an issue with locales. The problem is:
- Vcs cannot parse the subversion output with any locale.
- The locale LC_ALL=C has stranges behaviors.
- The locale en_US works fine but must be installed.
Yes vcs --check will check it.
Thanks for the report.
--
Nicolas Pouillard aka Ertai <ertai(a)feydakins.org>
http://uttk.org Uttk -- Unified Test Tool Kit
11:06 a.m.
>>>> "Nicolas" == Nicolas
Pouillard <nicolas.pouillard(a)gmail.com> writes:
Nicolas> On 3/4/06, Roland Levillain <roland(a)lrde.epita.fr> wrote:
Nicolas> Yes there is an issue with locales. The problem is:
Nicolas> - Vcs cannot parse the subversion output with any locale.
That's fair.
Nicolas> - The locale LC_ALL=C has stranges behaviors.
Bur that's rather strange! The C locale is meant to be the default
one, and should always behave correctly, shouldn't it? It is always
present and a program should not depend on a specific locale.
Do you remember the issues you had with the C locale? Maybe we/one
can help you fix them and use it instead of a en_US locale (remember
that the user may not have the right permissions to install such a
locale).
Nicolas> - The locale en_US works fine but must be installed.
6972
days inactive
6974
days old
2 comments
2 participants
participants (2)
-
Nicolas Pouillard -
Roland Levillain