After using python-updater to go from 2.5x to 2.6x, it seems that pygtk is not automatically included. I had whaawmp installed and it worked fine before running python-updater. However, after python-updater, it terminated at runtime throwing the error: Cannot continue, pygtk is not installed (version 2.12 required) When checking, I actually did not have pygtk installed anymore. As pygtk is included by default (as a RDEPEND of dev-python/gst-python), I was surprised to see it no longer installed. After reinstalling pygtk manually, whaawmp ran as expected. Reproducible: Always Steps to Reproduce: 1. Install whaawmp (which will pull in pygtk as part of gst-python). 2. Run python-updater to go from 2.5* (previous stable) to 2.6* (current stable). 3. Try to run whaawmp. Actual Results: whaawmp terminates with error: Cannot continue, pygtk is not installed (version 2.12 required) Expected Results: whaawmp should run without problem, as pygtk should remain installed.
Can't reproduce. Whaawmp worked flawlessly for the 2.5 -> 2.6 change for me, as well as through the 2.5.x changes. Makes me think that you borked your system by somehow unmerging pygtk, either manually or by running an unattended emerge --depclean or failing to let python-updater/revdep-rebuild finish its task. yngwin, if you want to add in a specific RDEP on pygtk for whaawmp, that's fine with me. Sure, the gst-python dep is in theory simpler, as it already has an RDEP on pygtk, but maybe we can work around user errors or python-updater/portage tool failures by including pygtk in the whaawmp ebuilds.
Oops, didn't mean to close with this resolution. Let's see what yngwin's response is, as he's the one who will actually make the commit for me.
I do think that pygtk was removed by --depclean, but I'm wondering why it was if it is listed as an RDEP for dev-python/gst-python.
(In reply to comment #3) > I do think that pygtk was removed by --depclean, but I'm wondering why it was > if it is listed as an RDEP for dev-python/gst-python. --depclean is known to break in certain cases, hence why running revdep-rebuild after every --depclean is required. In this case, though, it may be functioning as designed -- I notice that both the latest gst-python versions (.15 and .16) now have a dependency on *either* pygobject or pygtk. So if pygobject is explicitly required by some other package and nothing else on your system deps on pygtk, probably --depclean kept pygobject but pruned pygtk. yngwin: at this point I recommend we stick an RDEP on dev-python/pygtk into the whaawmp ebuilds, since we can no longer assume that gst-python will pull in the correct dependencies.
Ahhhhhhhh, thanks for the clarification Josh! I have never had problems with --depclean getting rid of something that was really an RDEP. Thanks again.
Ben: Please add an unconditional RDEP on dev-python/pygtk to the latest whaawmp ebuild, and please remove the old whaawmp 0.2.10 ebuild. Thanks!
Done. Sorry for the delay.
