Hi, Quoting Thomas Pircher (2016-09-14 20:21:14) > Changes since the last upload: > > * Non-maintainer upload. > * New upstream release (closes: #833081, #811988, #798624, #645616). I once made a similar mistake in one of my packages and just listed all the closed bugs without writing down how the new release closes them. You can see for yourself which version you like better in this commit where I fixed the problem for my package: https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?h=debian/unstable&id=5b06c85f93862f004053f1d85c1d69c9d7716955 Indeed it is not strictly *necessary* to list exactly how each bug was closed, but it is nice for the submitter of the bug to read how it got handled in the email they receive when your upload closes the bug. With just a list, as a bug submitter you don't know how your problem was taken care of without manually diffing the two versions. Here is a nice write-up about why to be more elaborate in d/changelog: https://www.debian.org/doc/manuals/developers-reference/ch06.en.html#bpp-debian-changelog Thanks! cheers, josch
Attachment:
signature.asc
Description: signature