Release 2.91~beta-1

[Ian Jackson]

Joost van Baal-Ilić writes ("Re: Release 2.91~beta-1"):
> 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.

In general, it is not adviseable to do binary builds for upload with
dpkg-buildpackage directly.  You want to do the build in a clean
environment, which means you need to be using a chroot build manager
such as sbuild, pbuilder or cowbuilder.  With sbuild (which is what I
use) that would involve passing
 --debuildopt=-vVERSION
or some such.  Others can advise for pbuilder.

However you should be doing a source-only upload where possible; the
main case where it isn't is when your package will end up in NEW
(including because it has new binary packages).  In that case you can
safely just use dpkg-buildpackage in your development environment, and
then you want to pass -v.

But:

> > > > Of course, IMO you should be using `dgit push',
> 
> Yes you should :)

As I say, dgit gets this right automatically because it knows how to
query the archive to find out what the last version was.

Also, to do a source-only upload with dgit, you do not need to do a
build at all.  You can just say `dgit push-source' and dgit will do
everything for you.

Ian.

-- 
Ian Jackson <ijackson at chiark.greenend.org.uk>   These opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.