the pygobject testsuite fails if pygtk isn't installed: make[2]: Entering directory `/var/tmp/portage/dev-python/pygobject-2.14.0/work/pygobject-2.14.0/tests' Traceback (most recent call last): File "./runtests.py", line 42, in <module> suite.addTest(loader.loadTestsFromName(name)) File "/usr/lib64/python2.5/unittest.py", line 533, in loadTestsFromName module = __import__('.'.join(parts_copy)) File "../tests/test_subtype.py", line 9, in <module> import gtk ImportError: No module named gtk make[2]: *** [check-local] Error 1 unfortunately pygtk RDEPENDs on pygobject, creating a circular dependency. because of this, it might be best to add RESTRICT=test to the pygobject ebuild.
Hmm... That's a very very hard one. Gnome team: maybe patch out any tests needing pygtk? Or block tests all together? In general, a new system should probably not be installed with FEATURES=test, but that's not a real solution.
I had this issue while upgrading to python-2.5 and running /usr/sbin/python-updater. pygobject bailed out with same error. Solved this by manually running: # FEATURES="-test" emerge -1 pygobject && emerge -1 pygtk && emerge -1 pygobject What about making pygobject DEPEND="test? ( dev-python/pygtk )"? This would introduce a circular dependency, which needs to be resolved the way described above. BR, Dustin
*** Bug 228497 has been marked as a duplicate of this bug. ***
*** Bug 231412 has been marked as a duplicate of this bug. ***
*** Bug 217349 has been marked as a duplicate of this bug. ***
If no one wants to fix this, I'll be adding RESTRICT=test to pygobject.
Why not add the DEPEND mentioned in comment #2? Plus a message on how to resolve the circular dependency.
Because a circular dependency happens when the package manager is building a dependency graph, before the list of packages to build is displayed, and before any particular package can display a message.
*** Bug 233362 has been marked as a duplicate of this bug. ***
For the record, the latest versions pygtk and pygobject should be fixed as the codegen tool needed for the tests has been moved to pygobject. So basically, the circular dep is gone. Hopefully, we should get those versions into portage along with Gnome 2.24. Keeping this bug open until it's in portage. Thanks
I was sick of this test suite failing in my chroot for arch testing so I added RESTRICT="test" to pygobject-2.14.2 as a simple workaround. Hope no one screams too loudly ;)
(In reply to comment #10) > For the record, the latest versions pygtk and pygobject should be fixed as the > codegen tool needed for the tests has been moved to pygobject. So basically, > the circular dep is gone. > I'm not sure what version "the latest" is, but I still see this with pygobject 2.15.4. Is this fixed with a newer version, or should it have been fixed in this version?
this stuff should be fixed since pygtk-2.14/pygobject-2.15, closing since there are stable revisions of there or a later release on most arches.
*** Bug 282930 has been marked as a duplicate of this bug. ***
Still not fixed
Still a problem with pygobject-2.18.0
I confirm it's still not fixed in pygobject-2.18.0, the problem can be fixed exactly in the same way as comment #2. Naturally the thing causes both python-updater (2.5->2.6) and emerge system/world to fail, please put a message there to avoid having the user come here to discover if it's something serious or if he can just jump the tests.
I fixed this in pygobject master by moving the tests that require gtk to pygtk itself.
Thanks a lot Gian, I will probably try to backport pygtk and pygboject patches if possible if nobody does it faster ;-): http://git.gnome.org/browse/pygtk/commit/?id=48f0a43f2faffee931ba419dac2687a93344bf5a http://git.gnome.org/browse/pygobject/commit/?id=4cbd9941c5705970a9f7a429e236e1203d3155a1
Thanks Pacho, see also http://git.gnome.org/browse/pygtk/commit/?id=b7ac3513997ad7c561bb830341e96db1bc9d529a
If I don't misremember, this should be fixed with pygtk-2.17 and latest pygobject
