Good morning Sebastien, can you please describe why is it a problem to upgrade Glibmm?
We are affected by an issue in the current version (2.58). After some changes in GTK+ theme mechanisms in order to be able to configure the CSS class names properly it is important to be able to call gtk_widget_class_set_css_name() in the object instance init function. However, this was not possible until Glibmm team add the support to this in version 2.60. Without these change there is no way to solve the problem. The discussion about this can be found in GNOME issue tracking: https://gitlab.gnome.org/GNOME/glibmm/issues/33 https://gitlab.gnome.org/GNOME/gtkmm/issues/17 ** Bug watch added: gitlab.gnome.org/GNOME/glibmm/issues #33 https://gitlab.gnome.org/GNOME/glibmm/issues/33 ** Bug watch added: gitlab.gnome.org/GNOME/gtkmm/issues #17 https://gitlab.gnome.org/GNOME/gtkmm/issues/17 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glibmm2.4 in Ubuntu. https://bugs.launchpad.net/bugs/1841793 Title: Don't update to 2.61.1 Status in glibmm2.4 package in Ubuntu: Triaged Bug description: The .news entry starts with '2.61.1: (unstable): Distro packagers should probably not package this yet.' Let's follow upstream's advice there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibmm2.4/+bug/1841793/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
