vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 80d45aa3fbb8cf90ef86d0577f78a2948a6e1915
Author: Simon McVittie <smcv@debian.org>
Date: Wed Jun 24 18:12:15 2020 +0100
Release to unstable
commit 2c83b3d3f9685c4400a3bfe9c87caab089d8c49b
Author: Simon McVittie <smcv@debian.org>
Date: Wed Jun 24 18:07:12 2020 +0100
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
![[bug history graph]](https://qa.debian.org/data/bts/graphs/g/glibmm2.4.png){kind=link}