On Thu, Jun 01, 2017 at 11:02:25PM +0200, Miro Hrončok wrote:
On 1.6.2017 20:49, Zbigniew Jędrzejewski-Szmek wrote:
>On Thu, Jun 01, 2017 at 11:26:55AM -0700, Toshio Kuratomi wrote:
>>I think it is better if the build system sets LANG=C.UTF-8, not the
>>python specific macros.
>Yeah, setting it through python macros would mean that e.g. any
>python program invoked during the build would see the obsolete non-utf8
>encoding. Seems better to just set LANG=C.UTF-8 globally.
Who could make that happen? Should I propose this at devel@?
It seems that mock uses $LANG to configure $LANG and all $LC_* variables
in the build environment. But when mock is invoked with LANG=C, it ignores
that and uses C.UTF-8 instead, because of the "Python 3 C.UTF-8 locale"
change in python. So with new-enough python, we'd get C.UTF-8 anyway on the
builders, once the builders are upgraded to F26. But then you'd still get
a warning on every mock invocation.
It seems that right solution, that would work while the builders are
still not F26, would be to configure their locale to C.UTF-8. It'd
just be a matter of dropping LANG=C.UTF-8 into /etc/locale.conf.
I think a ticket on https://pagure.io/fedora-infrastructure
the way to request the change.