Compile of gtk+-2.22.1 fails with the error:
/usr/share/gir-1.0/Atk-1.0.gir: Incompatible version 1.1 (supported: 1.2)
when dev-libs/atk-1.30.0 is installed.
Steps to Reproduce:
Upgrading to >=dev-libs/atk-1.32.0 allows the compilation to complete.
But this is only with USE=introspection, right?
And doesn't recompiling atk rebuild the .gir to the new version, or it just uses the one in the tarball, that happens to be built with 1.1?
(In reply to comment #1)
> But this is only with USE=introspection, right?
> And doesn't recompiling atk rebuild the .gir to the new version, or it just
> uses the one in the tarball, that happens to be built with 1.1?
Oops, you're right on both accounts. dev-libs/gobject-introspection had been updated beyond version 0.9.0-r1 and atk hadn't been rebuilt since then.
On a different subject, this doesn't seem trivial - I was updating 'world' and I hit this bug. Perhaps it's something that the atk or gobject-introspection package will need to address.
# Nirbheek Chauhan <email@example.com> (30 Dec 2009)
# gobject-introspection USE-flag
# introspection is not mature yet.
# gir-repository especially is a big pile of junk
The hope is that the gir format is fully stabilized by the time we need to remove this use.mask (primarily for gnome-shell purposes, iirc).
This use.mask quoting is another way of saying - if it breaks, you get to keep both pieces for now :)
This issue is not specific to Atk or Gtk. When gobject-introspection bumps the repository version number:
All introspection data needs to be rebuilt. This is similar to soname bumps in libraries.
The user should be told to run scripts/gir-rebuilder.py after updating gobject-introspection so that the rebuilding is done.
(In reply to comment #4)
> The user should be told to run scripts/gir-rebuilder.py after updating
> gobject-introspection so that the rebuilding is done.
*cough* I forgot to mention that this script is in the gnome.git overlay: http://git.overlays.gentoo.org/gitweb/?p=proj/gnome.git;a=blob;f=scripts/gir-rebuilder.py
How will this be finally handled in main tree? (maybe this should be added to gnome3 trackers :-/)
As I explained on IRC last time someone brought up this issue, the problem is that there is currently no way to tell if any solution we came up with right now will have any benefit when the next change happens. It's now been a while since situation stabilized and I think we better close this bug now, and eventually reopen it the day it actually hits us.
Hopefully things would then be tested in overlay so gentoo-x86 uses would never have to know about the problems that could have happened.