vcswatch reports that
this package seems to have a new changelog entry (version
0.1.87~1.gbpc97330, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit 61786de5406b79ac0b504f486ec692cdc83d8674
Author: Niels Thykier <niels@thykier.net>
Date: Sun Apr 26 16:50:39 2026 +0000
CI: Second attempt to disable `uscan` test
commit cf95cefea99e43d8f267f0590fb03da166bbcf96
Author: Niels Thykier <niels@thykier.net>
Date: Sun Apr 26 11:11:49 2026 +0000
CI: Disable `uscan` check
It fails because there is no watch file (which is given since
the Debian release is the "upstream" release as well currently).
commit 89220c4ac31316a282c401c4927e616e8e0e7e88
Author: Niels Thykier <niels@thykier.net>
Date: Sun Apr 26 10:35:14 2026 +0000
d/changelog: Generate snapshot version
Gbp-Dch: ignore
commit c97330a85c2d30cd481aa0b7f0e969c38a0b257f
Author: Niels Thykier <niels@thykier.net>
Date: Sun Apr 26 10:31:50 2026 +0000
Manifest: Support `dpkg-gensymbols` keyword
This per-package keyword can be used to configure the
`dpkg-gensymbols` call. Currently, it supports `check-level` (the `-c`
command line option).
commit ed061b4dc9c41224f46b76e922ea7114a71a7493
Author: Niels Thykier <niels@thykier.net>
Date: Sun Apr 26 09:08:11 2026 +0000
debputy: Generalise logic for loading debconf module
With this any `MaintscriptSnippet` can set `uses_debconf=True` and
the complete `maintscript` will now initialise `debconf` at the
stop of the script.