gbp-pristine-targbp-pristine-tar — Manage pristine-tar commits in a git repository |
gbp pristine-tar
[--version
] [--help
] [--verbose
] [--color=
[auto|on|off]] [--color-scheme=
COLOR_SCHEME
] [--upstream-tag=
tag-format
] [--component=
component
...] [commit
] filename
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.
|
Print version of the program, i.e. version of the git-buildpackage suite |
|
Verbose execution |
|
Print help and exit |
|
Whether to use colored output. |
|
Colors to use in output (when color is enabled). The format for
COLOR_SCHEME is
'<debug>:<info>:<warning>:<error>'.
Numerical values and color names are accepted, empty fields imply
the default color. For example,
|
|
use this tag format when tagging upstream versions,
default is |
|
When creating the pristine-tar commits also look for an additional tarball
with component name 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. |
Add pristine-tar commits for an upstream tarball:
gbp pristine-tar commit ../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 commit ../upstream-tarball-0.1.tar.gz
Several gbp.conf
files are parsed
to set defaults for the above command-line arguments. See the
gbp.conf(5) manpage for details.
gbp-import-orig(1), gbp.conf(5), debuild(1), git(1), pristine-tar(1), The Git-Buildpackage Manual