I tried to re-open the bug #46682 myself, but i'm not allowed. I thought new comments made them go into triage, but since nothing has been done, I assume they're ignored (then why let people comment on closed bugs?!) I too have this same problem with the latest meld 1.0 which is marked as stable http://packages.gentoo.org/ebuilds/?meld-1.0.0 locutus bin # emerge -a meld [ebuild R ] dev-util/meld-1.0.0 locutus bin # which meld /usr/bin/meld locutus bin # /usr/bin/meld Traceback (most recent call last): File "/usr/bin/meld", line 87, in ? import meldapp File "/usr/lib/meld/meldapp.py", line 27, in ? import prefs File "/usr/lib/meld/prefs.py", line 52, in ? import gconf ImportError: No module named gconf But I have gconf it seems... locutus ~ # emerge -a gconf [ebuild R ] gnome-base/gconf-2.10.1-r1 in any event, I just deleted everything related to meld, unmerged the rest, and tried to emerge again. same problem. I then did a emerge -Dav gnome-python, now i get a different error when i run 'meld' Fatal Python error: could not import ORBit module Aborted locutus portage-logs # esearch orbit * dev-python/orbit-python Latest version available: 1.99.0-r1 Latest version installed: [ Not Installed ] Size of downloaded files: 0 kB Homepage: http://orbit-python.sault.org/ Description: Orbit bindings for Python * dev-python/pyorbit Latest version available: 2.0.1 Latest version installed: 2.0.1 Size of downloaded files: 237 kB Homepage: http://www.daa.com.au/~james/pygtk/ Description: ORBit2 bindings for Python * gnome-base/orbit Latest version available: 2.12.4 Latest version installed: 2.12.3 Size of downloaded files: 661 kB Homepage: http://www.gnome.org/ Description: ORBit2 is a high-performance CORBA ORB I tried to emerge dev-python/orbit-python, but got the same error (so i unmerged it)
if you type "python" in a shell, and then type "import ORBit", what happens? Try re-emerging pyorbit as well.
Did you recently update python? You'll want to run "python-updater" as well.
python-updater seemed to fix the problem. so WTF! doesn't the python ebuild (or whatever is the appropriate ebuild script) run that for me?! ugh! lame.
also, why do I get these errors whenever 'meld' exits? /usr/lib/meld/meldapp.py:557: GtkDeprecationWarning: gtk.idle_add is deprecated, use gobject.idle_add instead gtk.idle_add( self.on_idle ) /usr/lib/meld/filediff.py:1195: DeprecationWarning: use gtk.gdk.Drawable.draw_pixbuf pix0.render_to_drawable( window, gctext, 0,0, 0, points0[ 0][1], -1,-1, 0,0,0) /usr/lib/meld/filediff.py:1196: DeprecationWarning: use gtk.gdk.Drawable.draw_pixbuf pix1.render_to_drawable( window, gctext, 0,0, x, points0[-1][1], -1,-1, 0,0,0) /usr/lib/meld/filediff.py:1193: DeprecationWarning: use gtk.gdk.Drawable.draw_pixbuf pix0.render_to_drawable( window, gctext, 0,0, 0, points0[ 0][1], -1,-1, 0,0,0) E
it does tell you to do so in the ebuild: echo ewarn ewarn "If you have just upgraded from an older version of python you will need to run:" ewarn ewarn "/usr/sbin/python-updater" ewarn ewarn "This will automatically rebuild all the python dependent modules" ewarn "to run with python-${PYVER}." ewarn ewarn "Your original Python is still installed and can be accessed via" ewarn "/usr/bin/python2.x." ewarn ebeep 5 The errors you are seeing are just warnings that the API the author is using is now deprecated, and to use the newer version. Nothing to be worried about, its probably already fixed in upstream cvs.
Not to start a thread on this or anything (I realise this has gone off of the 'meld' topic and more onto Python), and I appreciate your help/comments, but it just seems to me that, if the python ebuild knew what version it installed, and the one i had, and furthermore, it knows that i need to run this updater script, then just do it. Or just run it anyways in any case, as I'm sure it will handle things gracefully if there's nothing to do! why am I constantly bothered with these ewarn messages and sifting through install logs and other minutea. This to me is one of the biggest hinderences of linux adoption by general users. It's just not friendly enough. It expects the user to do things that should just be done for them automatically. *sigh*
