Re: The simpliest way to automatically rebuild few Debian packages ?

[deloptes <deloptes@gmail.com>]

Vincent Lefevre wrote:

> I think that you misunderstood. I'm not talking about the build log
> (which the end user will never see), but the Debian changelog file,
> which will be installed as
> 
> /usr/share/doc/<bin_package>/changelog.Debian.gz
> 
> For instance, for libtool on my machines I can see e.g.:
> 
> libtool (2.4.6-13+local1) UNRELEASED; urgency=medium
> 
> * Applied patch fixing bug #814091 (use a run path for tcc).
> 
> -- Vincent Lefevre <vincent@vinc17.net>  Mon, 17 Feb 2020 14:24:48 +0100
> 
> The patch system *alone* (via quilt or not) does not handle that.
> 
>
https://raphaelhertzog.com/2011/07/04/how-to-prepare-patches-for-debian-packages/
> mentions the use of dch, and it seems that the debdiff output
> will contain the change in the Debian changelog file, but even
> if apt-build can handle that (which I doubt), this is not OK
> since after a package upgrade, the debdiff is no longer valid
> (though the original patch may still remain valid, and will
> generally do as I could see; for instance, my patch for the
> above bug has been on the BTS for more than 4 years).

OK I understand now. I did not have a problem to add a new section in the
changelog with
  dch -v "4:$BUILDISTRO_NAME" -D "$DISTRO_NAME" -c $debian/changelog \
  "Autogenerated by building script"

$BUILDISTRO_NAME is the release number (14.1.0-0debian10.3.3+4eko) and
DISTRO_NAME is for example buster

for me it works great. For example

tdelibs-trinity (4:14.1.0-0debian10.3.3+4eko) buster; urgency=medium

  * Autogenerated by building script

does it help?