Going from dbus-glib-0.80 to 0.82, new public function dbus_g_connection_unregister_g_object was added. However, the libtool versioning flags were not changed. Both releases have configure.ac that states the same versioning (along with documentation instructing you to change it): >## increment if the interface has additions, changes, removals. >LT_CURRENT=3 [...] >## increment if any interfaces have been added; set to 0 >## if any interfaces have been changed or removed. removal has >## precedence over adding, so set to 0 if both happened. >LT_AGE=1 Using lib versioning properly allows downstream packagers to handle dependencies more easily (don't need to analyze the whole public header set to decide compatibility) and gives end-users better feedback if they use a version "too old" to have a symbol they need (tells what libversion provides it, not just "symbol not found").
We can't fully fix this til the next release, but it'd be worth adding a reminder to the cheat-sheet in HACKING.
Created attachment 45866 [details] [review] Remind maintainers to update the libtool versioning
Review of attachment 45866 [details] [review]: looks good.
Thanks; HACKING fixed in git for 0.94 based on Guillaume's review + no objections from the reviewer group, and the actual libtool versioning will be fixed in 0.94.
Fixed in 0.94 (I bumped the CURRENT and AGE even though nothing was actually added in 0.94, to compensate for the opposite error in 0.82)
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.