You are not logged in.
Pages: 1
Weird... Even though I have a locale (en_US.utf8) specified in rc.conf, and I've got the latest version of glibc (which should autodetect that), the locale wasn't detected. :? Ah well, it's not hard to do this manually...
Offline
Did you check the article on the news page? You probably have to run locale-gen.
Offline
en_US.utf8 is not a correct locale name, so glibc doesn't enable it when upgrading. Glibc autodetects locales only on updates. The locale.gen file contains a list of supported locales, uncomment the ones you need and run locale-gen.
Offline
Done... What I was looking at was this:
The glibc package will look in the $LANG variable and in /etc/rc.conf for the LOCALE setting.
The default LOCALE setting is "en_US.utf8". Perhaps this should be changed?
Offline
It doesn't detect en_US.iso885915, too. Had to edit locale.gen, add en_US ISO-8859-15 and rebuild locales, and then it works.
Excessive showering, grooming, and toothbrushing is not only vain, it wastes valuable coding time.
Offline
en_US.utf8 is not a correct locale name, so glibc doesn't enable it when upgrading.
I did an Arch FTP base install just this past weekend, and the newest glibc was placed on the system fresh, but I still had this same locale problem. The Arch news item refers to issues when upgrading but I just wanted to mention that it also is problematic on a fresh install using all the latest packages from the outset.
/path/to/Truth
Offline
Ah, perhaps that should be clarified in the news article. It applies to any installation of glibc-2.6.1 and above.
Offline
Yes, it might be helpful. I only looked at it after filing a bug report on an application that was actually the result of not having locale properly set on my system. The dev working the bug correctly identified the problem and I now have everything addressed. But even the dev mentioned 'glibc upgrade', though by this time I had become suspicious the issue was not only confined an upgrade session.
/path/to/Truth
Offline
I guess we're all thinking in terms of "upgrade" because we've had the earlier glibc on our machines. Sort of a mental shorthand.
I see your point, however. JCG, if you're still following the thread, perhaps you could edit the news article so it makes it clear that whether it's a new install or an upgrade, any version of glibc from 2.6-1 up needs this done?
(Just like the fortune quote, nothing is too much trouble for the one who doesn't have to do it.)
Offline
The 0.7.2 release won't take much longer I guess, the installer will have an option to edit locales from the installer, just like you have to edit rc.conf.
Offline
Anyway, the problem I'm finding is that, if you do locale-gen after installing, and have something in your LOCALE setting in rc.conf, locale-gen will not detect that. The news entry's mentioning of autodetection of the LOCALE entry, and locale generation based on that, is therefore erroneous.
Offline
Yes, I'm certain I had LOCALE="en_US.utf8" set in the rc.conf, and it was not detected when running locale-gen following the base install.
/path/to/Truth
Offline
Pages: 1