As there is no package requiring python-libgsf, I think it could be just dropped.
2012/4/20 Olav Vitters <o...@vitters.nl>: > In just released libgsf (1.14.23), Python is not built by default. > > Quoting https://bugzilla.gnome.org/show_bug.cgi?id=672663: > | The python bindings depends in pygtk-codegen-2.0 which is now a wrapper > | for pygobject-codegen-2.0 which itself was removed from pygobject. > | Instrospection being available they are obsolete either way. > | > | This patch disable their generation by default. > > What to do with above? By default python support is not built anymore > due to above. I can enable it in configure again, but prefer to just not > build it (despite above, still compiles with --with-python). If > something needs libgsf, they should use gobject introspection (which you > can use from Python as well as js, etc). > > Nothing seems to depend on python-libgsf AFAICS > > Should I: > - disable for Mageia 2 (as nothing seems to require python-libgsf) > should I add a Obsolete and where? task-obsolete or libgsf itself? > - enable static python bindings only for Mageia 2, remove after > in case something actually requires it > - stay with current libgsf version > problem sounds generic though, would apply to previous as well > > -- > Regards, > Olav