Thanks. I have applied that and released libgdamm 2.82. Note that the *mm libraries don't bother changing the .so version name usually. GTK+ doesn't change it either.
This is because - It's really hard to get right, because the version string in configure.ac is so disconnected from the eventual version name of the .so file. - If we specify an ABI break of new API between, for instance, GTK+ 2.11.1 and 2.11.2 (unstable releases) we have no way then to show that there is no API/ABI break (just API additions) between GTK+ 2.10.x and GTK+ 2.12.0 (stable releases). So you shouldn't really expect us to do this in future. If you think we should (I'm often wrong) then please do try to provide some exact examples of what libraries such as GTK+ should do in particular cases. I've tried to do that for GNOME before and failed. -- Request: Upgrade libgdamm3.0 to upstream version 2.9.81 https://bugs.launchpad.net/bugs/190744 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
