Bug#830572: UNRELEASED entry and new upstream version

2020-06-17 Thread Guido Günther
Hi, On Thu, Jun 11, 2020 at 10:22:14AM +0200, Raphael Hertzog wrote: > On Wed, 10 Jun 2020, Guido Günther wrote: > > Happy to apply a patch. I'm using > > > > ``` > > [import-orig] > > # Automatically forward the changelog after importing a new upstream version > > postimport = gbp dch -S -a

Bug#830572: UNRELEASED entry and new upstream version

2020-06-11 Thread Raphael Hertzog
On Wed, 10 Jun 2020, Guido Günther wrote: > Happy to apply a patch. I'm using > > ``` > [import-orig] > # Automatically forward the changelog after importing a new upstream version > postimport = gbp dch -S -a --debian-branch=$GBP_BRANCH && git commit --amend > -C@{0} debian/changelog > ``` > >

Bug#830572: UNRELEASED entry and new upstream version

2020-06-10 Thread Guido Günther
Hi, On Wed, Jun 10, 2020 at 09:29:04AM +0200, Raphael Hertzog wrote: > Hi, > > I was about to report that "gbp dch" was not updating the version number > in an UNRELEASED entry even after you have merged a new upstream version. > But I found this (broader) bug report, covering this and more. > >

Bug#830572: UNRELEASED entry and new upstream version

2020-06-10 Thread Raphael Hertzog
Hi, I was about to report that "gbp dch" was not updating the version number in an UNRELEASED entry even after you have merged a new upstream version. But I found this (broader) bug report, covering this and more. It would be really nice to get the changes documented in this bug report...