Hi Adam Am 16.08.19 um 22:08 schrieb Adam D. Barratt: > Control: tags -1 + confirmed > > On Fri, 2019-07-26 at 21:43 +0200, Michael Biebl wrote: >> I'd like to make a stable upload for systemd, fixing the following >> issues: > [...] >> 241-5+deb10u1 is identical to 241-7 which has been uploaded to >> unstable/bullseye and we haven't received any regression reports so >> far. > > In that case, feel free to make it -7~deb10u1, with the appropriate > changelog wrangling, if that would be preferable.
I considered adding a changelog entry like this as it seemed the most obvious correct one: --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,9 @@ +systemd (241-7~deb10u1) buster; urgency=medium + + * Rebuild for buster + + -- Michael Biebl <bi...@debian.org> Sat, 17 Aug 2019 11:00:59 +0200 + systemd (241-7) unstable; urgency=medium [ Michael Biebl ] But this then triggers warnings from dpkg-genchanges: dpkg-genchanges: warning: the current version (241-7~deb10u1) is earlier than the previous one (241-7) and lintian: W: systemd: latest-debian-changelog-entry-without-new-version To avoid that, I could rewrite the old changelog entry for 241-7 like this --- a/debian/changelog +++ b/debian/changelog @@ -1,4 +1,4 @@ -systemd (241-7) unstable; urgency=medium +systemd (241-7~deb10u1) buster; urgency=medium [ Michael Biebl ] * network: Fix failure to bring up interface with Linux kernel 5.2. Rewriting the old changelog entry for 241-7 feels wrong though. Adam, so I wonder, what's the proper changelog wrangling in this case? Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
