dev-python/libgksu-python-2.19.1 requires pygtk, but no such entry exists in the ebuild's DEPEND or RDEPEND variables. Reproducible: Always Steps to Reproduce: 1. emerge dev-python/libgksu-python Actual Results: Fails at ./configure Expected Results: Installs fine checking for a Python interpreter with version >= 2.3... python checking for python... /usr/bin/python checking for python version... 2.6 checking for python platform... linux2 checking for python script directory... ${prefix}/lib/python2.6/site-packages checking for python extension module directory... ${exec_prefix}/lib/python2.6/site-packages checking for headers required to compile python extensions... found checking for i686-pc-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for PYGTK... configure: error: Package requirements (pygtk-2.0 >= 2.4.0) were not met: No package 'pygtk-2.0' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables PYGTK_CFLAGS and PYGTK_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. !!! Please attach the following file when seeking support: !!! /var/tmp/portage/dev-python/libgksu-python-2.19.1/work/gnome-python-extras-2.19.1/config.log * * ERROR: dev-python/libgksu-python-2.19.1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3846: Called gnome2_src_compile * environment, line 2652: Called gnome2_src_configure * environment, line 2666: Called econf '--disable-allbindings' '--enable-gksu2' * ebuild.sh, line 534: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/dev-python/libgksu-python-2.19.1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-python/libgksu-python-2.19.1/temp/environment'.
emerge -pv --tree libgksu-python please pygtk is already in R/DEPEND of gnome-python-extras which is a R/DEPEND of libgksu-python.
dan@parakeet ~ $ emerge -pv --tree libgksu-python These are the packages that would be merged, in reverse order: Calculating dependencies... done! [ebuild N ] dev-python/libgksu-python-2.19.1 USE="-debug -examples" 0 kB Total: 1 package (1 new), Size of downloads: 0 kB dan@parakeet ~ $ Don't know if this helps any, but I don't have dev-python/gnome-python-extras installed. dan@parakeet ~ $ eix dev-python/gnome-python-extras * dev-python/gnome-python-extras Available versions: ~*2.14.2-r1 2.19.1-r3 {X debug doc firefox seamonkey xulrunner} Homepage: http://pygtk.org/ Description: Meta build which provides python interfacing modules for some GNOME libraries [I] dev-python/gnome-python-extras-base Available versions: 2.19.1!t {debug} Installed versions: 2.19.1!t(19:30:41 04/02/09)(-debug) Homepage: http://pygtk.org/ Description: Provides python the base files for the Gnome Python Desktop bindings Found 2 matches. dan@parakeet ~ $ And I can't see dev-python/gnome-python-extras in R/DEPEND anywhere. dan@parakeet ~ $ grep DEPEND /usr/portage/dev-python/libgksu-python/libgksu-python-2.19.1.ebuild RDEPEND=">=x11-libs/libgksu-2.0.4" DEPEND="${RDEPEND}" dan@parakeet ~ $
I meant gnome-python-extras-base sorry and the dependency can't be seen because it is inherited from eclass. I guess we'll need to add pygtk/pygobject to the eclass dependencies since it's likely to affect other bindings. @ford_prefect, I saw that you have further commits that never went to the tree in your overlay branch, could you enlighten us on this ?
I wouldn't be so sure about it being something for the eclass. While all modules in gnome-python-extras probably do use gtk+, not all of them might actually do it via pygtk in python, but for example merely by directly wrapping the relevant C library which itself only uses C gtk+. While some libraries indeed might try to import (py)gtk or (py)gobject. Also some other python bindings outside -extras might not even use C gtk+ indirectly, e.g pyorbit and such things can probably do without. So basically a full import audit might be in order here?
re-reading the configure, pygtk check is unconditional in gnome-python-extras, gnome-python-desktop and gnome-python. However each -base ebuild already RDEPENDS on it. So I think someone fixed it since the original report. Closing fixed. Feel free to reopen if it is not.