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 ceb492a9beca0494f20be97b2061fd8b647e6126
Author: Nicolas Boulenguez <nicolas@debian.org>
Date: Mon Mar 16 08:38:16 2026 +0100
MANIFEST-FORMAT: add missing semicolon in create-symlink examples
commit d832823507bf0ff3dc8fa3c29d809ab279daa77b
Author: Niels Thykier <niels@thykier.net>
Date: Sun Mar 15 07:09:27 2026 +0000
Tweak the autoscropts generated for service management
Based on:
* https://salsa.debian.org/debian/debhelper/-/merge_requests/148
* https://salsa.debian.org/debian/debhelper/-/merge_requests/149
commit 3952b2d185434bc18c6b7354b28291d73420fb97
Author: David Kalnischkies <david@kalnischkies.de>
Date: Wed Mar 11 11:38:33 2026 +0000
Allow multiple equal relations in Provides
My package ycmd has this gem:
| Provides: ycmd-core-version (= ${ycmd:Core-Ver}), ycmd-core-version (= 48)
deputy was complaining about this with:
| warning: File: ./debian/control:30:50:31:0: Duplicate relationship. Merge with the previous relationship [Policy 7.2]
| 30: Provides: ycmd-core-version (= ${ycmd:Core-Ver}), ycmd-core-version (= 48)
| Related information: The previous definition
| 30: Provides: ycmd-core-version (= ${ycmd:Core-Ver}), ycmd-core-version (= 48)
This is not a duplicate relation (assuming `${ycmd:Core-Ver}` doesn't
happen to be 48) and it can not be merged as the warning suggests.
Such provides are not common and they can produce some fun if you think
too hard about it, but e.g. `debhelper` uses them as well for providing
various debhelper-compat versions – its not affected by this through as
it generates the entire set and hides it in a variable.
As such, while not common they are legal and (occasionally) useful,
so debputy shouldn't produce incorrect warnings about them.
commit 384c5a2c27ab1f3a28342565a9025dd9ef5cf247
Author: David Kalnischkies <david@kalnischkies.de>
Date: Wed Mar 11 12:28:22 2026 +0000
Allow directories in File-Excluded in d/copyright
My package ycmd (as well as the hover doc) use a directory for
exclusion in a Files-Excluded which debputy warns about:
| warning: File: ./debian/copyright:11:1:11:12: Directories cannot be a match. Use `dir/*` to match everything in it [debputy][Correctable via --auto-fix]
| 11: third_party
The documentation (uscan man page) clearly show directories as valid
entries, as does the debputys hover text. Other places do mention it
has "the same syntax" as Files through, which probably helps this
confusion.
Haven't tried, but I presume `dir/*` will leave an empty `dir` around
in the repack, which might or might not be a problem. In either case,
the warning is wrong – a dir can be a match in this field – and so
it should not be fixed, even automatically.
commit 61b61b5741f052ba8286b180c0ca0ecb79bd2f71
Author: Niels Thykier <niels@thykier.net>
Date: Wed Mar 11 20:26:55 2026 +0000
CI: Use `testing` for CI tasks
The new version of `black` in unstable has different formatting rules
than the one in `unstable` and it is stuck (migration-wise).
Gbp-Dch: ignore
commit 383c7ac16988b8c1748dfe4f2f03c46abe4927d3
Author: Bastian Germann <bage@debian.org>
Date: Tue Mar 10 08:54:50 2026 +0100
lsp: Fix typo in common-licenses path
![[bug history graph]](https://qa.debian.org/data/bts/graphs/d/debputy.png){kind=link}