[Pkg-puppet-devel] Inclusion of new/updated puppet module packages
Michael Weiser
michael.weiser at gmx.de
Wed Dec 3 11:40:59 UTC 2014
Hi,
On Tue, Dec 02, 2014 at 06:13:47PM +0100, Michael Weiser wrote:
> As for the uploading: Let me have a look into cowbuilder/pbuilder and
> DEP-8 testing first. When I'm happy with that, I'll take you up on it.
Whilst playing around with pbuilder I noticed that pristine-tar data
wasn't updated by git-import-orig --uscan for all but
puppet-module-puppetlabs-apt.
For puppet-module-puppetlabs-{ntp,concat,stdlib} I guess it's due to the
fact that there's no debian/gbp.conf with
[import-orig]/pristine-tar=true in it (and I didn't run git-import-orig
with --pristine-tar because I had no clue, what I was doing).
My other four packages do have the debian/gbp.conf stolen from
puppet-module-puppetlabs-apt. Here the pristine-tar branch wasn't
created either. I guess that didn't work, because I was doing an initial
import via git-import-dsc without --pristine-tar.
Anyhow:
- Should I add debian/gbp.conf to puppet-module-puppetlabs-{ntp,concat,stdlib}?
- Is git-buildpackage --git-pristine-tar-commit the correct way to add
that data retroactively? I've tried it and it seems to work as expected.
--
Thanks,
Michael
More information about the Pkg-puppet-devel
mailing list