gbp-pristine-tar

&dhsection;

gbp-pristine-tar

Manage pristine-tar commits in a git repository

          &gbp-pristine-tar;

          &man.common.options.synopsis;
          --upstream-tag=tag-format
          --component=component

            commit

            filename

## DESCRIPTION

&gbp-pristine-tar; adds the pristine-tar commit for a given upstream tarball to a &git; repository. This can be useful if a original tarball has been already imported and the pristine-tar commits should be added at a later time or if you're tracking upstream git and want to create pristine-tar commits nevertheless.

## OPTIONS

&man.common.options.description;

`--upstream-tag=``tag-format`

- use this tag format when tagging upstream versions, default is `upstream/%(version)s`

`--component=``COMPONENT`

- When creating the pristine-tar commits also look for an additional tarball with component name `COMPONENT`. E.g. in `hello-debhelper_1.0.orig-foo.tar.gz` the component name would be `foo`. The additional tarball is expected to be in the same directory than the upstream tarball and to use the same compression type. This option can be given multiple times to add multiple additional tarballs.

  Using additional original tarballs is a feature of the 3.0 (quilt) source format. See the `dpkg-source` manpage for details. This is currently considered an experimental feature and might change incompatibly.

## EXAMPLES

Add pristine-tar commits for an upstream tarball:

          &gbp-pristine-tar; ../upstream-tarball-0.1.tar.gz

Same as above with an additional tarball `../upstream-tarball-foo-0.1.tar.gz:`

          &gbp-pristine-tar; --component-tarball=foo ../upstream-tarball-0.1.tar.gz

&man.gbp.config-files;

## SEE ALSO

man.gbp.import.orig, man.gbp.conf, &man.seealso.common;

## AUTHOR

&dhusername; &dhemail;