Valters Jansons [Fri, 10 Jul 2026 13:48:12 +0000 (22:48 +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.
Valters Jansons [Sun, 28 Jun 2026 13:37:59 +0000 (22:37 +0900)]
House-keep for Lintian tags
* I: older-debian-watch-file-standard 4 [debian/watch]
d/watch now follows RFC822 similar to other d/ files.
* I: out-of-date-standards-version 4.6.1 (released 2022-05-11) (current is 4.7.4)
Reading the changelog, we seem to be safe to mark compatibility.
* P: package-uses-old-debhelper-compat-version 13
The latest recommended level is v14, and we do not have any breaking
changes according to debhelper-compat-upgrade-checklist. Updating
our debhelper references accordingly.
* P: redundant-priority-optional-field [debian/control:9]
This key-value is redundant. "optional" is the default.
Furthermore, Standards-Version 4.7.3: 5.6.6: Specifying the Priority
field in source package control fields is no longer recommended
unless the priority needs to be changed from the default.
* P: redundant-rules-requires-root-no-field [debian/control:26]
This key-value is redundant. "no" is the default.
Valters Jansons [Mon, 17 Mar 2025 18:12:09 +0000 (20:12 +0200)]
Update `versionmangle` to handle time in filename
Since 2024-03-19, the database files have a time component in their
filenames. Previously, versionmange handled the date component,
dropping the dashes from 2024-03-19 to 0~20240319. However, now the
time component gets added as a Debian revision, and messes the logic
up. So with this commit the versionmange transforms timestamp into
a similar upstream component, from -03:45 to ~0345.
Upstream filename 2024-03-20-03:45 now becomes 0~20240320~0345,
while retaining 2024-03-19 as 0~20240319 for backwards compatibility.