Re: Truncated changelog leads to file conflict with MultiArch: same

debhelper (13.31) unstable; urgency=medium
  * Update cutoff date in dh_installchangelogs to Bookworm release date

Newly built packages (loong64) are built using newer version of debhelper,

Best Regards,
Tianyu Chen


Dominique Dumont <[email protected]> 于2026年5月17日周日 17:59写道：

> Hi
>
> I've an issue with one of my sponsored package (libisoburn [1])
>
> Mulitarch hinter mentions:
>
>  There are issues with the multiarch metadata for this package.
>
>     libisoburn-dev conflicts on
> /usr/share/doc/libisoburn-dev/changelog.Debian.gz on loong64 <-> amd64,
> arm64, armhf and 4 more
>     libisoburn1t64 conflicts on
> /usr/share/doc/libisoburn1t64/changelog.Debian.gz on loong64 <-> amd64,
> arm64, armhf and 4 more
>
> As suggested by the wiki page, I've downloaded and compared loong64 and
> amd64 binary packages.
>
> Turns out that both have a truncated changelog. But the loong64 package
> has less entries.
>
> I see that these packages were built at different time (2026-01-17 vs
> 2026-03-07). I can only guess that truncation is time based so the cut line
> has moved, hence the difference.
>
> I think this is a bug. A package rebuild should not lead to differences in
> truncated changelog.
>
> What do you think ?
>
> Where should I log a bug ?
>
> All the best
>
> Dod
>
> [1] https://tracker.debian.org/pkg/libisoburn