Summary: | app-i18n/ibus-anthy should depend on dev-python/pygobject | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | 白川間瀬流 <vamp898> |
Component: | Current packages | Assignee: | CJK Team <cjk> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | toralf |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
白川間瀬流
2014-12-10 19:32:11 UTC
Given the deptree, this can only happen if you didn't set gtk3 useflag on ibus. I tried to reproduce - Set GTK3 Useflag on ibus - Recompile ibus - compile ibus-anthy Crashes [...] checking whether /usr/bin/python2.7 version is >= 2.5... yes checking for /usr/bin/python2.7 version... 2.7 checking for /usr/bin/python2.7 platform... linux2 checking for /usr/bin/python2.7 script directory... ${prefix}/lib64/python2.7/site-packages checking for /usr/bin/python2.7 extension module directory... ${exec_prefix}/lib64/python2.7/site-packages checking if your ibus version is supported... Traceback (most recent call last): File "<string>", line 5, in <module> ImportError: No module named gi.repository configure: error: no [...] The issue seems to be the python use-flag + gtk3 use-flag. ibus also needs the python USE-Flag + the gtk3 USE-Flag to pull in pygobject should ibus-anthy depend on ibus[python gtk3] ?!? (In reply to 白川間瀬流 from comment #2) > I tried to reproduce … > ibus also needs the python USE-Flag + the gtk3 USE-Flag to pull in pygobject > > should ibus-anthy depend on ibus[python gtk3] ?!? I've hit this as well, and got Traceback (most recent call last): File "<string>", line 5, in <module> ImportError: cannot import name IBus configure: error: no after following your advice although i clearly see stuff in /usr/lib/python2.7/site-packages/ibus. Oh okay, the proper USE combo is "+python +gtk3 +introspection -deprecated". https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4487fa29cd5d45c9fae0ba960068a37486003503 Thank you for reporting! *** Bug 591924 has been marked as a duplicate of this bug. *** |