Re: Truncated changelog leads to file conflict with MultiArch: same
Dominique Dumont <[email protected]>
| Newsgroups | gmane.linux.debian.devel.general |
|---|---|
| Message-ID | <118614863.nniJfEyVGO@ylum> |
On Sunday, 17 May 2026 14:14:51 Central European Summer Time Gioele Barabucci wrote: > Hi, the issue you are seeing is due to the fact that the loong64 buildd > chroot has (had) a newer version of debhelper compared to the one used > in the other archs. Right.. Since we're going to release a new libisoburn package in the next week or so, I'll ignore this problem until then. However, for the specific problem of changelog trimming, it's unfortunate that the cutoff date depends on an external event (a Debian release). I would think an algorithm depending only on the changelog entries would be preferable. Something like keep the last 5 years of entries counting from the date of the last changelog entry. Thanks for the explanation. All the best
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEn3I5/LZk8Qsz6dwDwx9P2UmrK2wFAmoMB3YACgkQwx9P2Umr K2xRbw//TS/72yiVK/SPOaylEbRfvC0RIMzPuGUWqpeSubg1zZIq2lTAmii07F2+ NpjDlydR6z7YvXCx3D/sv/L4iON/gHyoOo2ffT8/PAaJZVLfwmQ1PiXZAItHW+eb BrE43UI9/CR84mMBW9/HhdTOUnVwgtLXl9qppId1P/vvPvCNtSBHDz6DeChNOuqk cwYiK2bEpgH6p2+UNkbBzUMY0EslOxfwmVeRLCVyFJEaNlkgy5hbi/4e59mvomYN D0vXCg9coazl6FfQvVpCI/8QilVA2s9lA1V/xgqYu9NAn0imyzgGIpYpQRuB0QX6 QOXmmmGDH2qZT47Xuw9XY0TPU6xuwTJVx3MybI32D83p/BkdwCiP6GHWzh0dm5xM b2e8Wh1gU7PjyBGOF8DJxM84E7g7pJ3dFRfbmNfn052f/D+5WMGQgdpne8Xy8uEt tzUz82KMQzyZMGEfx4FAjbunPaVOYgCz6Ut8Yl0OdPaiUS85q2gYyU2HAkOL8KBY dUmemA8n+sMmVI27qQTvq9Wg3rGsf+fUgifmoQwCm03DwGzWAW+CIH3OHtU4hrSn CuOac9F76gk5GSUFvq3RhZO2n63MlwEfHU+ze1C5izsY3LVZ2w1NLZW2t2VUmzz7 1Phr/2RwETl+qCTlrMO8yJ46E6cr42C7GTuyxH4EynKN2DZogJc= =x/Tt -----END PGP SIGNATURE-----