pygtk should not add an interface to a class that has already been initialised

[Marc Deslauriers]

pygtk applications in raring are getting a warning similar to the following:

/usr/lib/python2.7/dist-packages/gobject/__init__.py:115: Warning: attempting to add an interface (GtkEditable) to class (HistoryFileEntry) after class_init
  type_register(cls, namespace.get('__gtype_name__'))

Because of recent glib changes:
http://blogs.gnome.org/desrt/2012/11/05/a-warning-about-glib/

Example bugs:
meld - bug 1103170
dia - bug 1102960

[Martin Pitt (pitti)]

Fixed package uploaded to Debian. I'll sync it tomorrow morning, when it made its way into Debian and imported in Launchpad.

[Launchpad Janitor (janitor)]

This bug was fixed in the package pygobject-2 - 2.28.6-11

---------------
pygobject-2 (2.28.6-11) unstable; urgency=low

  * debian/control.in: Drop the "Provides: python2.6-gobject". There are no
    reverse dependencies anyway, and we don't encourage any new ones.
  * Add 00git_class_init.patch: Move property and signal creation into
    _class_init(). This allows old PyGTK applications to work with static
    PyGObject and GLib 2.35.x. (LP: #1129309)

 -- Martin Pitt <email address hidden> Tue, 19 Feb 2013 16:19:52 +0100