Re: Preparing for the libc/locale upgrade

2015-10-01 Thread Taylan Ulrich Bayırlı/Kammer
Leo Famulari writes: > Just want to confirm I'm doing your workaround properly... like this? > $ ln -s gnu/store/...-glibc-utf8-locales-2.22/lib/locale > /run/current-system/locale > $ echo $LOCPATH > > The previous line is blank, showing that $LOCPATH is unset. I think that would leave you with

Re: Preparing for the libc/locale upgrade

2015-10-01 Thread Leo Famulari
Just want to confirm I'm doing your workaround properly... like this? $ ln -s gnu/store/...-glibc-utf8-locales-2.22/lib/locale /run/current-system/locale $ echo $LOCPATH The previous line is blank, showing that $LOCPATH is unset. On Tue, Sep 29, 2015, at 10:32, Mark H Weaver wrote: > Federico Bef

Re: Preparing for the libc/locale upgrade

2015-10-01 Thread Konrad Hinsen
On 30/09/2015 14:35, Federico Beffa wrote: From my point of view Mark's suggestion sounds as the most acceptable (although I've not tested it as I've not updated my Guix yet). I just tested it, it works fine. And, finally, no more error messages about missing locales anywhere! Konrad.

Re: Preparing for the libc/locale upgrade

2015-10-01 Thread Federico Beffa
On Wed, Sep 30, 2015 at 3:46 PM, Ludovic Courtès wrote: > Federico Beffa skribis: > >> On Mon, Sep 28, 2015 at 10:45 PM, Ludovic Courtès wrote: > > [...] > >> From my point of view Mark's suggestion sounds as the most acceptable > > Which one is it? For some reason I don't see Mark's message on

Re: Preparing for the libc/locale upgrade

2015-09-30 Thread Ludovic Courtès
Federico Beffa skribis: > On Mon, Sep 28, 2015 at 10:45 PM, Ludovic Courtès wrote: [...] > From my point of view Mark's suggestion sounds as the most acceptable Which one is it? >> IMO Guix is not at fault; rather, it sheds light on a shortcoming of >> libc’s handling of locale data, which w

Re: Preparing for the libc/locale upgrade

2015-09-30 Thread Federico Beffa
On Mon, Sep 28, 2015 at 10:45 PM, Ludovic Courtès wrote: > Federico Beffa skribis: > >> l...@gnu.org (Ludovic Courtès) writes: >> >> [...] >> >>> Consequences for Guix on foreign distros: >>> >>> • If the host distro provides binaries that use libc < 2.22 and you >>> use a mixture of Guix-p

Re: Preparing for the libc/locale upgrade

2015-09-30 Thread Federico Beffa
On Tue, Sep 29, 2015 at 4:32 PM, Mark H Weaver wrote: > Federico Beffa writes: > >> l...@gnu.org (Ludovic Courtès) writes: >> >> [...] >> >>> Consequences for Guix on foreign distros: >>> >>> • If the host distro provides binaries that use libc < 2.22 and you >>> use a mixture of Guix-provi

Re: Preparing for the libc/locale upgrade

2015-09-30 Thread Mark H Weaver
Federico Beffa writes: > l...@gnu.org (Ludovic Courtès) writes: > > [...] > >> Consequences for Guix on foreign distros: >> >> • If the host distro provides binaries that use libc < 2.22 and you >> use a mixture of Guix-provided and distro-provided programs, this is >> pretty bad. >> >>

Re: Preparing for the libc/locale upgrade

2015-09-28 Thread Ludovic Courtès
Federico Beffa skribis: > l...@gnu.org (Ludovic Courtès) writes: > > [...] > >> Consequences for Guix on foreign distros: >> >> • If the host distro provides binaries that use libc < 2.22 and you >> use a mixture of Guix-provided and distro-provided programs, this is >> pretty bad. >> >

Preparing for the libc/locale upgrade

2015-09-28 Thread Federico Beffa
l...@gnu.org (Ludovic Courtès) writes: [...] > Consequences for Guix on foreign distros: > > • If the host distro provides binaries that use libc < 2.22 and you > use a mixture of Guix-provided and distro-provided programs, this is > pretty bad. > > Solution: unset LOCPATH and say g

Preparing for the libc/locale upgrade

2015-09-24 Thread Ludovic Courtès
Problem: Programs linked against libc < 2.22 abort when trying to load libc 2.22-or-later locale data: https://lists.gnu.org/archive/html/guix-devel/2015-08/msg00737.html Programs linked against libc 2.22 do not abort when trying to load 2.21 locale data, but they fail to load data for the LC_C