Release 2.91~beta-1

Joost van Baal-Ilić joostvb-debian-init-diversity at mdcc.cx
Thu Nov 22 08:56:57 GMT 2018


Hi,

On Wed, Nov 21, 2018 at 03:06:51PM +0000, Ian Jackson wrote:
> Dmitry Bogatov writes ("Re: Release 2.91~beta-1"):
> > [2018-11-19 15:17] Ian Jackson <ijackson at chiark.greenend.org.uk>
> > > Joost van Baal-Ilić writes ("Re: Release 2.91~beta-1"):
> > > > On Mon, Nov 19, 2018 at 01:05:23PM +0000, Dmitry Bogatov wrote:
> > > > > By the way, will BTS close bugs, mentioned in previous changelog entry?
> > > > 
> > > > You'd need to call dpkg-genchanges -vVERSION in order to generate a .changes
> > > > file for your upload which contains all needed changelog entries.
> > > 
> > > You should do that anyway, so that the upload has the right set of
> > > stuff in the changes file.
> > 
> > Where should I plug this command? If I just invoke it, it prints on
> > stdout.
> 
> Joost's was speaking slightly loosely.  All builds-for-upload invoke
> dpkg-genchanges in the middle somewhere.  What you need is to arrange
> for it to additionally get the right -v option.

Indeed.  If what you use uses dpkg-buildpackage, you should make sure
dpkg-buildpackage gets called with the right -v option: dpkg-buildpackage
passes it to dpkg-genchanges.

> How to do that that depends on what tools you normally use to do the
> release build and generate the .changes file.  Are you using sbuild or
> pbuilder/cowbuilder or something else ?
> 
> > > == begin plug ==
> > > 
> > > Of course, IMO you should be using `dgit push',
<snip>

Yes you should :)

Bye,

Joost





More information about the Debian-init-diversity mailing list