Control: retitle -1 gbp-dch: Support x.y.z-1 UNRELEASED type of changelog 
opening commits

Hi,
On Sat, Jul 09, 2016 at 06:33:36PM +0300, Otto Kekäläinen wrote:
> Package: git-buildpackage
> Severity: wishlist
> 
> Current snapshot number style workflow supported by git-buildpackage
> does not fit my workflow.
> 
> I'd wish there was a option like 'git-dch --unreleased' which simply
> added to the changelog an empty entry with the Debian revision
> incremented by one and target set to UNRELEASED.
> 
> Then I could work as normally and not commit any snapshot commits, but
> instead only generate snapshots at build time in my own build array or
> as Launchpad does it. When all changes are done I'd like to run
> 'git-dch --release' which would remove the temporary empty entry and
> replace it with the normal git-buildpackage automatic changelog entry.

As discussed offline this sound reasonable. What I currently dislike is
that we have a -1 debian revision by default. This makes it hard to
build several candidates with ever increasing version numbers (but
smaller than the release). Can you explain how you generate "snapshots
at build time" as said above to avoid this problem?

> For this new --unreleased option to work also the --release logic
> should be updated to be compatible with it.
> 
> In addition if would be nice that import-orig would follow this same
> logic and automatically open an empty changelog entry with the
> imported version number so that I don't accidentally build the new
> upstream with old version in an un-updated changelog.

As discussed offline I do like that part since currently doing

    gbp import-orig --uscan
    gbp buildackage

fails due to a changelog still pointing to the old version and therefore
dpkg-source comparing the new upstream version in git with the old
tarball which fails. It is is already doable with a postimport hook
since you get the version number on the command line and could just
invoke

   dch -v $1 && git commit --amend debian/changelog

but it should be integrated into import-orig proer after we've sorted
out the gbp-dch parts.

Cheers,
 -- Guido

Reply via email to