Re: ERROR:root:Requiring namespace 'Gtk' version '2.0', but '3.0' is already loaded

[John Palmieri <johnp redhat com>]

----- "Robert Park" <rbpark exolucere ca> wrote:

> On Wed, Nov 17, 2010 at 12:54 PM, John Palmieri <johnp redhat com>
> wrote:
> > Oh, ya, Fedora 14 ships with a really old version of PyGObject
> Introspection.  You are not going to see a newer version until Fedora
> 15.  This is because the GObject Introspection ABI changed after the
> freeze.  This is the price of playing on the cutting edge.  I suggest
> running rawhide in a virtual host or using jhbuild to build a
> buildroot.  We are committed to stabilizing introspection in the next
> 5 months (well we freeze in 2 to 3 months).   Until then there is
> going to be pain like this.
> 
> Ok, so realistically, what are my options here? I would ideally like
> for users of Fedora 14 to be able to install and run my app (the goal
> of my app is to be useful to users, not just some toy that only works
> for cutting edge developers). I guess introspection was a premature
> choice for achieving that goal, but it seemed kinda pointless to
> develop against obsolete technology.
> 
> If I install pygobject from rawhide, would it be reasonable to
> provide
> instructions for users to also do that, or should I basically just
> give up on the idea of having any users until Fedora 15?
> 
> -- 
> http://exolucere.ca

Removing the libchamplain CC: since we are venturing into off topic territory.  I tried running your stuff on Fedora 14 and even ClutterGtk isn't correctly introspectable (it has a gir and typelib but nothing is exported).  Users can't install from Rawhide, it would break their whole system as the dependencies go way down the stack.  Realistically you will have to wait, but the truth is in 5 months you won't even remember the issues.  I've been through this countless times with Gtk2, D-Bus, HAL, cairo, Clutter, insert your favorite cutting edge library that we now take for granted here, and a little patience pays off in the long run.  By developing against the cutting edge and finding issues you are not only helping us make a solid release (who doesn't like saying they helped bring a new technology to fruition), but you are ensuring when the next batch of distros are released your application will work.  Deferring until later may mean another 6-8 months of waiting for distros to pick up the latest fixes.

--
John (J5) Palmieri
Software Engineer
Red Hat, Inc.