glibmm2.4 (2.64.2-2) unstable; urgency=medium
* Team upload
* Stop managing shlibs version by hand.
This approach to dependency generation relies on maintainers
remembering to update the version when necessary, which in practice
isn't reliable, so it's only appropriate for libraries that very rarely
add new ABI. Normally I'd add a symbols file, but those are problematic
for C++ code unless it manages its ABI very carefully. Instead rely on
debhelper compat level 12, which we already use, defaulting to the
equivalent of dh_makeshlibs -VUpstream-Version; this results in
dependent software getting a dependency on at least the same upstream
version it was compiled against. (Closes: #961216)
-- Simon McVittie <email address hidden> Wed, 24 Jun 2020 18:12:03 +0100
