Release 2.91~beta-1

Ian Jackson ijackson at
Wed Nov 21 15:06:51 GMT 2018

Dmitry Bogatov writes ("Re: Release 2.91~beta-1"):
> [2018-11-19 15:17] Ian Jackson <ijackson at>
> > 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.

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', and if you do, dgit
> > will take care of this for you.  For the sysvinit tree with its
> > gbp-style patches-unapplied approach, and since there is no change to
> > the binary packages, I think all you need is
> > 
> >   git checkout master
> >   # check that git contents is good and changelog version
> >   #   is right right, committing any needed changes
> >   git-deborig   # if you don't have a suitable .orig.tar.* yet
> >   dgit --gbp push-source sid
> > (to do a source-only upload).
> Is being DD enough to use dgit? Or I need special access to

tl;dr: Being a DD is enough.  No special access is required.

Longer explanation:

When you run `dgit push' it will want to use your pgp key to sign not
only the .dsc and the .changes but also a couple of git tags.

It will then use your ssh private key to ssh to the dgit git server,
which knows the ssh public keys of DDs.  (The public key list is the
same as used for DD access to porterboxes, DD-only servers, etc.)
(The ssh key check is mostly there to defend the repo from DoS type
attacks; the primary permission check is done by verifying the pgp
signature on the tag.)


Ian Jackson <ijackson at>   These opinions are my own.

If I emailed you from an address or, that is
a private address which bypasses my fierce spamfilter.

More information about the Debian-init-diversity mailing list