From: Eduardo Habkost <ehabkost@redhat.com>
To: Matthias Maier <tamiko@43-1.org>
Cc: qemu-devel@nongnu.org,
"Daniel P . Berrange" <berrange@redhat.com>,
Arfrever Frehtes Taifersar Arahesis <arfrever.fta@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 1/2] Partially revert commit d4e5ec877ca
Date: Fri, 15 Jun 2018 17:34:25 -0300 [thread overview]
Message-ID: <20180615203425.GF7451@localhost.localdomain> (raw)
In-Reply-To: <20180614154357.20132-2-tamiko@43-1.org>
On Thu, Jun 14, 2018 at 10:43:56AM -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
> setting above locales results in build errors even though another UTF-8
> locale was originally set [1]. The only stable way of fixing the
> encoding problem is by explicitly annotating encoding/decoding in the
> python script.
Thanks for the patches. It's nice to see that hack go away.
Patch 2/2 is necessary to make the removal of PYTHON_UTF8 safe,
correct? In that case, I plan to reverse the order of the
patches before applying.
>
> [1] https://bugs.gentoo.org/657766
[...]
--
Eduardo
next prev parent reply other threads:[~2018-06-15 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 15:43 [Qemu-devel] [PATCH 0/2] Fix compilation with python-3 if en_US.UTF-8 is unavailable Matthias Maier
2018-06-14 15:43 ` [Qemu-devel] [PATCH 1/2] Partially revert commit d4e5ec877ca Matthias Maier
2018-06-15 20:34 ` Eduardo Habkost [this message]
2018-06-15 21:12 ` Matthias Maier
2018-06-14 15:43 ` [Qemu-devel] [PATCH 2/2] qapi: open files in binary mode and use explicit decoding/encoding in common.py Matthias Maier
2018-06-14 17:04 ` [Qemu-devel] [PATCH 0/2] Fix compilation with python-3 if en_US.UTF-8 is unavailable no-reply
2018-06-18 22:15 ` Eric Blake
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180615203425.GF7451@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=arfrever.fta@gmail.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tamiko@43-1.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).