On Fri, Jun 15, 2018, at 10:17 CDT, Markus Armbruster wrote:
> "Partially revert"? Which part isn't reverted?
Yes, it ended up being a full revert of the commit in question. I am
sorry for the sloppy wording.
> [...]
>>Recently, however, glibc introduced a new locale "C.utf-8" that just
On Fri, Jun 15, 2018 at 08:20:36AM -0500, Matthias Maier wrote:
>
> On Fri, Jun 15, 2018, at 04:42 CDT, Daniel P. Berrangé
> wrote:
>
> > On Thu, Jun 14, 2018 at 11:40:41PM -0500, Matthias Maier wrote:
> >> This commit removes the PYTHON_UTF8 workaround. The problem with setting
> >>
> >> LC
"Partially revert"? Which part isn't reverted?
Matthias Maier writes:
> On Fri, Jun 15, 2018, at 04:42 CDT, Daniel P. Berrangé
> wrote:
>
>> On Thu, Jun 14, 2018 at 11:40:41PM -0500, Matthias Maier wrote:
>>> This commit removes the PYTHON_UTF8 workaround. The problem with setting
>>>
>>>
On Fri, Jun 15, 2018, at 04:42 CDT, Daniel P. Berrangé
wrote:
> On Thu, Jun 14, 2018 at 11:40:41PM -0500, Matthias Maier wrote:
>> This commit removes the PYTHON_UTF8 workaround. The problem with setting
>>
>> LC_ALL= LANG=C LC_CTYPE=en_US.UTF-8
>>
>> is that the en_US.UTF-8 locale might n
On Thu, Jun 14, 2018 at 11:40:41PM -0500, Matthias Maier wrote:
> This commit removes the PYTHON_UTF8 workaround. The problem with setting
>
> LC_ALL= LANG=C LC_CTYPE=en_US.UTF-8
>
> is that the en_US.UTF-8 locale might not be available. In this case
What platform are you using where UTF8 loc
This commit removes the PYTHON_UTF8 workaround. The problem with setting
LC_ALL= LANG=C LC_CTYPE=en_US.UTF-8
is that the en_US.UTF-8 locale might not be available. In this case
setting above locales results in build errors even though another UTF-8
locale was originally set [1]. The only stable
