Summary: | x11-terms/gnome-terminal-3.8.4 fails to build with dev-util/gdbus-codegen-2.36.4, non-UTF8 system locale, and python3 as system python interpreter | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Fernando (likewhoa) <email> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | python |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 378027 | ||
Attachments: | build log |
Description
Fernando (likewhoa)
2013-08-30 20:03:00 UTC
Created attachment 357460 [details]
build log
What locales are you using? Also this looks a bit risky to me: ACCEPT_KEYWORDS="amd64 ~amd64 ~x86" running 'export LANG="<YOUR LANGUAGE>.UTF-8"' allows emerge to complete. @Pacho Ramos submitted last comment at the same time, anyways i am using default locale. It fails in python stuff... I think python had some problems with non-utf8 :/ (In reply to Pacho Ramos from comment #5) > It fails in python stuff... I think python had some problems with non-utf8 :/ same with net-im/empathy, I will file that bug also. CCing python team to clarify this problem Pretty common issue in Python. If the script doesn't declare an encoding when opening a file, it is opened with the encoding specified in locale. Depending on the exact task the code is performing, it either needs to specify the encoding when opening the file (e.g. using io.open(..., encoding='utf8')) or open the file in binary mode. Can't tell much more not knowing the exact internals. In any case, this is upstream issue. In the particular case of building gnome-terminal, the error manifests only when using python3 as the default python interpreter. But this is a real bug in gdbus-codegen which has existed for a long time and can in theory also happen when using python2. The problem is that gdbus-codegen does not respect the encoding specified in input XML files' declaration, and instead always uses the build environment's encoding. Ah, looks like it's already fixed in upstream git: https://bugzilla.gnome.org/show_bug.cgi?id=696633 Fixed, thanks for reporting the problem. +*gdbus-codegen-2.36.4-r1 (01 Sep 2013) +*gdbus-codegen-2.34.3-r1 (01 Sep 2013) +*gdbus-codegen-2.32.4-r2 (01 Sep 2013) + + 01 Sep 2013; Alexandre Rostovtsev <tetromino@gentoo.org> + +gdbus-codegen-2.32.4-r2.ebuild, +gdbus-codegen-2.34.3-r1.ebuild, + -gdbus-codegen-2.36.3.ebuild, +gdbus-codegen-2.36.4-r1.ebuild, + +files/gdbus-codegen-2.36.4-input-encoding.patch: + Do not open input files as build-environment encoding text when using python3 + as the python interpreter (bug #483060, thanks to Fernando V. (likewhoa)). |