[Pkg-puppet-devel] Inclusion of new/updated puppet module packages

[Russ Allbery]

Stig Sandbeck Mathisen <ssm at debian.org> writes:

> I use the "pristine-tar commit" command, but if "git-buildpackage" helps
> you commit a tarball with the correct git reference for the "I imported
> / merged upstream at this point" commit, that should be ok. (I didn't
> know git-buildpackage did that, too :)

Yup, git-buildpackage is great.

For special bonus points (although it's not clear it's worth the hassle),
you can even add upstream's Git repository as a remote, and then use gbp
import-orig --upstream-vcs-tag <upstream-release-tag> when importing the
tarball.  Everything works exactly the same as before, except that the
master branch is actually a Git merge with upstream's real history with
any additional tarball contents added, so you can bisect, git log on
upstream files, and all those fun things.

-- 
Russ Allbery (rra at debian.org)               <http://www.eyrie.org/~eagle/>