Control: reassign -1 debhelper
Control: found -1 debhelper/13.11.4

On Sun, 2023-12-24 at 14:27:22 +0000, Simon McVittie wrote:
> Package: libacl1,debhelper
> Control: found -1 libacl1/2.3.1-3
> Control: found -1 debhelper/13.11.9
> Severity: important
> X-Debbugs-Cc: debian-rele...@lists.debian.org

> I notice that libacl1 uses dh_installchangelogs --no-trim in its
> debian/rules to suppress the default exclusion of older changelog
> entries. It appears that using that option also suppresses the separation
> of binNMU changelog entries into a separate file? I think it probably
> should not, because the trimming of old changelog entries is merely
> a nice-to-have to save some disk space, but the separation of binNMU
> changelog entries is functionally necessary if we want packages to remain
> multiarch co-installable across binNMUs.

Yes, I don't see why the old behavior, when requested explicitly,
would no longer behave as previously. This would seem like a regression
in debhelper due to the trimming handling.

> A sourceful upload of libacl1 would temporarily address this (until the
> next binNMU) by not being a binNMU, but would not be a long-term solution,
> unless we stop using binNMUs entirely and replace them with "no-changes"
> machine-assisted sourceful uploads like Ubuntu has done.

I've uploaded acl now with some minor pending changes I had queued as
a temporary workaround. But the obvious and correct way forward to me
is to fix debhelper (instead of having to change all affected packages,
or having to stop using binNMUs due to this…).

And I've just tested this and it also affects the current debhelper
version in Debian (stable) bookworm. :/

Thanks,
Guillem

Reply via email to