Re: The simpliest way to automatically rebuild few Debian packages ?
On 2020-04-22 22:18:19 +0200, deloptes wrote:
> Vincent Lefevre wrote:
>
> > On 2020-04-22 08:29:09 +0200, deloptes wrote:
> >> 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?
> >
> > No. Could you give an example with the apt-build call?
>
> No, cause I use debuild, however your question was how to put it in the
> changelog, or I misunderstood.
You misunderstood, and probably didn't pay attention at the beginning
of the thread. In my message from 21 Apr 2020 17:31:38 +0200, I gave
an example using dch and debuild (which is the solution I've been
using for years). And to the suggestion about using apt-build, I asked
"can one provide a log message associated with each patch?".
> I have no idea what apt-build does. I looked at the package, but not
> likely that I will ever need it
I was wondering whether apt-build could automate things even more
than my current solution, but it seems that my current solution can
do more, at least for the goal of just patching source packages and
rebuilding.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: