&dhemail;
&dhfirstname;
&dhsurname;
gbp-export-orig
&dhsection;
gbp-export-origExport upstream tarballs from a &git; repository
&gbp-export-orig;
[auto|on|off]=COLOR_SCHEMEBRANCH_NAMEtag-format[TAG|BRANCH|TREEISH]DIRECTORYTYPELEVELcomponent[auto|on|off]DESCRIPTION
&gbp-export-orig; is used to export upstream tarballs from a
&git; repository. Usually upstream tarballs are created by
&gbp-buildpackage; when needed but if you don't want to perform
a build you can use this command.
OPTIONS
verbose execution
[auto|on|off]
Whether to use colored output.
=COLOR_SCHEME
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 --color-scheme='cyan:34::' would
show debug messages in cyan, info messages in blue and other messages
in default (i.e. warning and error messages in red).
=BRANCH_NAME
Branch to build the orig tarball from if
is set to
BRANCH. Default is
upstream.
Include git submodules in the orig tarball.
TAG-FORMAT
Use this tag format when looking for tags of upstream versions,
default is upstream/%(version)s.
Force creation of an orig tarball (overwriting a pre-existing one if
present).
[BRANCH|TAG|TREEISH]
How to find the upstream sources used to generate the tarball.
TAG (the default) looks at a tag corresponding to the
version in the changelog. BRANCH looks at
the upstream branch given via the
option.
Other values are interpreted as treeishs.
This doesn't have any effect if
is being used.
DIRECTORY
Search for original tarballs in DIRECTORY
instead of generating them.
DIRECTORY can contain a version format
substitution pattern, eg: foo-%(version)s.
TYPE
Specifies the upstream tarball compression type. This will be used to
locate and build the upstream tarball if necessary. The default is
auto which derives the compression type
from the pristine-tar branch if available and falls back to gzip
otherwise. Other options are gzip,
bzip2, lzma and
xz.
LEVEL
Specifies the upstream tarball compression level if an upstream
tarball needs to be built.
COMPONENT
When generating tarballs create an additional original
tarball of directory COMPONENT
in the source tree. Using additional original tarballs is
a feature of the 3.0 (quilt) source format. See
the dpkg-source manpage for details. Note that the
--pristine-tar-commit
option is currently incompatible with this option.
This is considered an experimental feature and might
change incompatibly.
Use pristine-tar when generating the upstream tarball if it doesn't
exist.
Commit the pristine-tar delta to the pristine-tar branch if a new
tarball was generated and the pristine-tar data isn't already there.
[auto|on|off]
Whether to export with upstream signatures.
EXAMPLES
Generate an upstream tarball of the version currently referenced
in the changelog using &pristine-tar;:
&gbp-export-orig; --pristine-tar
Same as above but generate and additional tarball for
directory foo.
&gbp-export-orig; --pristine-tar --component=foo
&man.gbp.config-files;
SEE ALSO,
,
,
,
&man.seealso.common;
AUTHOR
&dhusername; &dhemail;