Bug#881467: git-buildpackage: gbp dch should filter out commits behind upstream-vcs-tag

[Guido Günther]

Hi,
On Sun, Nov 12, 2017 at 02:15:26PM +0800, Daniel Kahn Gillmor wrote:
> Package: git-buildpackage
> Version: 0.9.1
> Severity: wishlist
> 
> I use upstream-vcs-tag to include upstream's commits in addition to
> the debian packaging commits in debian packaging git history.
> 
> This works great for many parts of my workflow, thanks!
> 
> However, it causes "gbp dch" to propose incredibly verbose changelogs
> when i import new versions from upstream -- the proposed changelog
> entry includes all of upstream's commits as well as the debian
> packaging.
> 
> But, "gbp dch" should be able to tell that upstream-vcs-tag is
> available (e.g. debian/gbp.conf) and it could exclude upstream's
> changes (maybe replacing them all with "New upstream release") when
> generating a new debian/changelog entry.
> 
> Does that make sense as a feature request?

Gbp-Dch can ge told which files/directories to look at for changes like

gbp dch debian/

so while something you describe could be added too I'm not sure it's
really useful.

That said if somebody comes up with a clean patch I'm happy to apply
it. Given all the other bugs we have currently open in gbp it's not
likely I'm going to implement this anytime soon.

Cheers,
 -- Guido

Bug#881467: git-buildpackage: gbp dch should filter out commits behind upstream-vcs-tag

[Daniel Kahn Gillmor]

Package: git-buildpackage
Version: 0.9.1
Severity: wishlist

I use upstream-vcs-tag to include upstream's commits in addition to
the debian packaging commits in debian packaging git history.

This works great for many parts of my workflow, thanks!

However, it causes "gbp dch" to propose incredibly verbose changelogs
when i import new versions from upstream -- the proposed changelog
entry includes all of upstream's commits as well as the debian
packaging.

But, "gbp dch" should be able to tell that upstream-vcs-tag is
available (e.g. debian/gbp.conf) and it could exclude upstream's
changes (maybe replacing them all with "New upstream release") when
generating a new debian/changelog entry.

Does that make sense as a feature request?

 --dkg

-- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (500, 'oldstable'), 
(200, 'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git-buildpackage depends on:
ii  devscripts 2.17.11
ii  git1:2.15.0-1
ii  man-db 2.7.6.1-2
ii  python33.6.3-2
ii  python3-dateutil   2.6.1-1
ii  python3-pkg-resources  36.6.0-1

Versions of packages git-buildpackage recommends:
pn  cowbuilder | pbuilder | sbuild  
ii  pristine-tar1.42
ii  python3-requests2.18.1-1

Versions of packages git-buildpackage suggests:
pn  python3-notify2  
pn  sudo 
ii  unzip6.0-21

-- no debconf information