Issue 7060 <https://github.com/ansible/ansible/issues/7060> created.
On Friday, April 18, 2014 12:20:37 AM UTC+2, Michael DeHaan wrote: > > I'd agree especially for those. > > Please make sure there's a ticket filed if you can't find one already. > We'll probably want to research a bit more which specifically should make > modifications. > > > > > On Thu, Apr 17, 2014 at 5:47 PM, Strahinja Kustudić > <[email protected]<javascript:> > > wrote: > >> The first modules that should use the default system LANG are command and >> shell. Having them as C can give a lot of problems, especially if you are >> inserting something into a database which is UTF8. >> >> >> On Tuesday, April 15, 2014 11:06:24 PM UTC+2, Michael DeHaan wrote: >> >>> It's done because various modules rely on parsing Unix commands and >>> these commands are difficult to parse in different languages. >>> >>> The proposal has been made that if LANG is set in the environment, we >>> possibly not set LANG, though we'll need to consider implications. >>> >>> It may be that only certain modules need to set the LANG to C, so it may >>> warrant reading history and audit specifically what changes may have to >>> occur. >>> >>> >>> >>> >>> >>> >>> On Thu, Apr 10, 2014 at 9:43 PM, Alistair Bayley <[email protected]>wrote: >>> >>>> We've tracked down a bug in our ansible-driven build to the LANG >>>> environment variable being explicitly set to "C". I'm wondering why this >>>> is >>>> done i.e. why modify it at all? Why not just use the environment of the >>>> user/account executing the ansible script? It was confusing, because >>>> running the same commands manually from the ansible user account did not >>>> reproduce the fault. >>>> >>>> I found this post: >>>> https://groups.google.com/forum/#!topic/ansible-project/HD3yxPfsnzg >>>> which says that it is done to avoid encoding issues; which is ironic, >>>> as it has caused us encoding issues... >>>> >>>> We've set module_lang = en_NZ.UTF-8 in ansible.cfg for now. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Ansible Project" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> To post to this group, send email to [email protected]. >>>> >>>> To view this discussion on the web visit https://groups.google.com/d/ >>>> msgid/ansible-project/7aa2587f-423f-450c-87bd- >>>> d3b107d1978f%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/7aa2587f-423f-450c-87bd-d3b107d1978f%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> To post to this group, send email to [email protected]<javascript:> >> . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/681fa534-91c1-46dd-9976-f8315895e11a%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/681fa534-91c1-46dd-9976-f8315895e11a%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/06c1dd1d-c16b-4637-81d0-254fae34e745%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
