If there was an ABI change the libtool 'current' would need to be bumped. This change just bumps the libtool 'revision', indicating no ABI change. The end result is the .so version goes from libutouch- geis.so.1.0.1 to libutouch-geis.so.1.0.2. Since the NEEDED section of any ELF binary that links to the .so specifies only libutouch-geis.so.1 and the debian package installer runs ldconfig to link the new library to that name, there is no problem running older built apps against the newer library. Or even vice-versa, if you discount the bug being fixed.
The benefit of bumping the revision on a non-API change, and one of the main purposes of .so versioning in the first place, is that it is possible to distinguish between version of the library just by looking at its name. That is, libutouch-geis.so.1.0.1 contains a bug, and libutouch-geis.so.1.0.2 does not. It would be an error to not increment the revision. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/656503 Title: event dispatch can hang under some circumstances -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
