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 a93e338aa4477ded9763a6d5d229a2f0b804dff6
Merge: c62a0e4 0fca1c9
Author: Valters Jansons <valter.jansons@gmail.com>
Date: Fri Jul 10 13:59:23 2026 +0000
Merge branch 'compat-14-single-binary' into 'master'
Avoid implicit activation of single-binary addon
See merge request debian/libloc-database!8
commit 0fca1c990d6c4cde77f109cd8d70cd719533923b
Author: Valters Jansons <valters@vibesolutions.eu>
Date: Fri Jul 10 22:48:12 2026 +0900
Avoid implicit activation of single-binary addon
Historically, dh auto-install behavior depended on whether the
source was building just one package. If so, then all the files
were automatically installed as that package. However, when two
or more packages were configured, then the installable files had
to be defined explicitly. This kind of automagical helper behavior
sounded good in theory, but resulted in accidentally broken builds
when a second package was being added.
With compat 15, this behavior will not be automatically determined,
and instead, single-binary behavior will be an opt-in. And trying
to keep single-binary enabled for multiple packages will be breaking.
This will ensure maintainers can benefit from this helper, while also
adding safeguards against future breakage.
In compat 14, when dh sees a single package, it enables the legacy
behavior, and shouts a warning block to inform about this behavior
change. In our case, we already have d/*.install, so we can safely
adopt the compat 15 behavior which supports multiple packages.
For suppressing the compat 14 warning, this commit simply adds a
`--without single-binary` flag to dh. This will be removable in
compat 15, as this behavior will be the default without a warning.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/libl/libloc-database.png){kind=link}