| Summary: | meld 1.0.0 doesn't start | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Daevid Vincent <daevid> |
| Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Daevid Vincent
2005-09-23 20:23:01 UTC
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* |
