FS#15925 - LANGUAGE and LC_ALL not set before installing packages.
Attached to Project:
Release Engineering
Opened by Māris Vilks (kaaposc) - Thursday, 13 August 2009, 09:34 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 26 November 2012, 04:45 GMT
Opened by Māris Vilks (kaaposc) - Thursday, 13 August 2009, 09:34 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 26 November 2012, 04:45 GMT
|
Details
As I understand worker_auto_locale runs *after* installing
packages, but while installing ca-certificates, perl
complains:
> perl: warning: Setting locale failed. > perl: warning: Please check that your locale settings: > LANGUAGE = (unset), > LC_ALL = (unset), > LC_COLLATE = "C", > LANG = "en_US.UTF-8" > are supported and installed on your system. > perl: warning: Falling back to the standard locale ("C"). It does not fail ca-certificates installation, just a warning. |
This task depends upon
Closed by Gerardo Exequiel Pozzi (djgera)
Monday, 26 November 2012, 04:45 GMT
Reason for closing: Deferred
Monday, 26 November 2012, 04:45 GMT
Reason for closing: Deferred
> installing perl...
> error: command failed to execute correctly
Not sure where it comes from as Alt+F7 does not mention any errors. Maybe some LANGUAGE or LC_ALL setting command fails?..
dieter@dieter-ws-a7n8x-arch aif [experimental] grep -R LANG .
./src/aif.sh:# NOTE: Pacman will run with currently active locale, if you want to parse output, you should prefix with LANG=C
./src/core/libs/lib-pacman.sh: PACKAGE_GROUPS=`LANG=C $PACMAN_TARGET -Si $1| awk '/^Name/{ printf("%s ",$3) } /^Group/{ print $3 }'`
so we should basically have a locale active during the whole installation so that the user can see output of programs and such in his own language if he wants (and maybe someday , have a translated AIF).
i'm not sure what the best way is to implement this.
OTOH, maybe it's not necessarily bad to have no locale active yet in this phase. after all it's just a warning.