Anyone know of a reason why I should not `apt-get install locales' on
vcs.sv? I'd leave the default locale as None, as it is now.
I think every system should have the locales package installed. So
definitely installing it is the right thing to do.
(BTW: PAM uses the default locale setting for
It actually looks like the Savannah gecos data (real names etc) is in
latin-1 rather than utf-8; does anyone know if that is indeed the case?
I do not know, but it wouldn't surprise me.
Anyone know of a reason why I should not `apt-get install locales' on
vcs.sv? I'd leave the default locale as None, as it is now.
As long as the default locale doesn't change, sounds safe enough to
me to try. Please just keep an eye for it for people reporting new and
strange errors that
Karl Berry wrote:
Anyone know of a reason why I should not `apt-get install locales' on
vcs.sv? I'd leave the default locale as None, as it is now.
As long as the default locale doesn't change, sounds safe enough to
me to try.
Done.
It actually looks like the Savannah gecos data
Hi,
Anyone know of a reason why I should not `apt-get install locales' on
vcs.sv? I'd leave the default locale as None, as it is now.
I think this is the way to solve a bzr commit email issue with non-ascii
characters in people's Savannah user names.
It seems a bit odd that the package is not
