On Mon, Feb 06, 2017 at 02:03:24PM +0000, Ian Jackson wrote: > What is the right convention for NEW backports ? It can't be "all > changelog entries since the last backport that was uploaded" since > that's "all changelog entries ever" surely.
It can be a bit controversial, but that's it usually, yes.
From the doc:
|It is recommended to include all changelog entries since the last
|version on debian-backports or since stable if it's the first version.
|You should do this by passing "-v" to dpkg-buildpackage. Eg: "debuild
|-v0.7.5-2", where "0.7.5-2" is the version in stable. If the package
|wasn't in stable or backports before you don't have include the
|changelog entries (but you are free to do so). It helps others to follow
|the changes introduced with the backport (by reading the changes mailing
|list).
That's pretty clear on what the expected behaviour is for a new
backport of a package already in stable; it's less unclear about a
package never in stable; that said, I those cases I usually put all of
the changelog, yes... because the changelog of a package never in stable
can't be so big, right?! /me looks at dgit's changelog… ok, this
particular case would not be cool to include all of the changelog
indeed u.U
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
