On Mon, Jun 29, 2009 at 09:46:20PM +0200, Mehdi Dogguy wrote:
> There is no new changelog entry when/after binNMUing a package. It
> just appears in the package version.
That's not entirely true.
There is a new changelog entry in the binNMU-ed package, which
contains a fixed template + various lines usually coming from the
binNMU request by maintainers, for instance:
zack@usha:/tmp$ dpkg -l libmagick10 | tail -n1
ii libmagick10 7:6.3.7.9.dfsg2-1+b1 image manipulation library
zack@usha:/tmp$ zcat /usr/share/doc/libmagick10/changelog.Debian.gz |head -n 6
imagemagick (7:6.3.7.9.dfsg2-1+b1) unstable; urgency=low
* Binary-only non-maintainer upload for amd64; no source changes.
* Rebuild against libltdl-dev.
-- Debian amd64 Build Daemon <buildd_i386-excelsior@buildd.debian.org> Tue, 07 Apr 2009 07:16:21 +0000
But, that entry is added automatically by the autobuilders to the
binary packages and does not appear in the corresponding source
packages.
To answer Eric's question: no, there is no need to integrate the
binNMU-ed changelog entries in future release of the source
package. They just get dropped; intuitively they don't matter for the
source evolution and their were needed only due to (enlarged)
toolchain changes.
Cheers.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Dietro un grande uomo c'è ..| . |. Et ne m'en veux pas si je te tutoie
sempre uno zaino ...........| ..: |.... Je dis tu à tous ceux que j'aime
Attachment:
signature.asc
Description: Digital signature