On Tue, Aug 02, 2016 at 11:28:59PM +0200, Ludovic Courtès wrote: > Leo Famulari <l...@famulari.name> skribis: > > > On Tue, Aug 02, 2016 at 07:32:23PM +0200, Ludovic Courtès wrote: > >> As discussed on IRC, SNAFU! For reasons yet to be elucidated, the > >> glibc@2.23 package no longer honors /run/current-system/locale.
> > The variable 'libc_cv_localedir', which we set as > > "/run/current-system/locale/" in the glibc/linux package definition, has > > been renamed to 'libc_cv_complocaledir'. > > ;; See > > <http://sourceware.org/ml/libc-alpha/2013-03/msg00093.html>. > > - ;; FIXME: This hack no longer works on 2.23! > > - (string-append "libc_cv_localedir=/run/current-system/locale/" > > + (string-append > > "libc_cv_complocaledir=/run/current-system/locale/" > > ,version) > Otherwise LGTM; could you push it to core-updates-next? I've rebuilt my GuixSD system with this change, and I can confirm that it works. Setting GUIX_LOCPATH does not work in all cases, at least for me. For example, the remote shell program 'mosh' requires a UTF-8 environment on the host. Even with GUIX_LOCPATH set correctly in my login profile, mosh does not find the locales. Also, the calendar app 'ikhal' is no longer working, and setting GUIX_LOCPATH does not work for me. I think we should prioritize this fix.
