orbit-python is supposed to be ORBIT 1 bindings pyorbit is supposed to be ORBIT 2 bindings latest orbit-python (1.99.0) is an ORBIT2 binding => bad please remove orbit-python-1.99 and change ebuilds that badly depends on this one (meld beeing the only one ??). Make them depend on pyorbit-1.99 or even 2.0 grep -r "dev-python/orbit-python-1" /usr/portage/*-* /usr/portage/dev-util/meld/meld-0.8.3.ebuild: >=dev-python/orbit-python-1.99.0" /usr/portage/dev-util/meld/meld-0.8.5.ebuild: >=dev-python/orbit-python-1.99.0"
remove meld 0.8.3 ebuild also. 0.8.5 works ok so, only 1 ebuild to change and 2 ebuild to remove
looks like 1.99.0 was added, and then the decision was made to split pyorbit, likely that the project name changed and 1.99 was missed in the orbit-python dir.
hmm, i'll have to go and fix this one then and move orbit-python-1.99 out and replace it with a dummy package that just depends on pyorbit. and also change meld over to pyorbit
fixed in portage now. new orbit-python-1.99 is a placeholder that just deps on pyorbit-1.99. fixed meld deps as well. we could probably just remove the orbit-python-1.99 ebuilds but i prefer to keep them there to prevent more breakage.
Id vote for removing that orbit-python, since having that package in portage heavily confuses user like me, who had to rebuild their site-packages after upgrading to python 2.3: For me gdesklet was broken. Looked at it's dependencies, re-emerged gnome-python and orbit-python and wondered why it still was not working. Then realized that orbit-python does nothing. Thought it would be broken, well and with some luck I've found this bug report. Well, but I guess, that not everyone will have that much luck: Some more impatient users could consider Gentoo to be horribly broken, cause of this dummy package....
