Provided by: git-buildpackage_0.9.15_all bug


       gbp-export-orig - Export upstream tarballs from a Git repository


       gbp export-orig [--verbose] [--color=[auto|on|off]] [--color-scheme= COLOR_SCHEME]
                       [--upstream-branch= BRANCH_NAME] [--[no-]submodules] [--upstream-tag= tag-
                       format] [--upstream-tree= [TAG|BRANCH|TREEISH]] [--tarball-dir= DIRECTORY]
                       [--force-create] [--compression= TYPE] [--compression-level= LEVEL]
                       [--component= component]... [--[no-]pristine-tar]


       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.


              verbose execution

              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 --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  to build the orig tarball from if --upstream-tree is set to BRANCH. Default
              is upstream.

              Include git submodules in the orig tarball.

              Use this tag format  when  looking  for  tags  of  upstream  versions,  default  is

              Force creation of an orig tarball (overwriting a pre-existing one if present).

              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 --upstream-branch option.

              Other values are interpreted as treeishs.

              This doesn't have any effect if --pristine-tar is being used.

              Search  for  original  tarballs in DIRECTORY instead of generating them.  DIRECTORY
              can contain a version format substitution pattern, eg: foo-%(version)s.

              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.

              Specifies the upstream tarball compression level if an upstream tarball needs to be

              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.


       Generate  an  upstream  tarball of the version currently referenced in the changelog using

             gbp export-orig --pristine-tar

       Same as above but generate and additional tarball for directory foo.

             gbp export-orig --pristine-tar --component=foo


       Several gbp.conf files are parsed to set defaults for the  above  command-line  arguments.
       See the gbp.conf(5) manpage for details.


       gbp-buildpackage(1),  gbp-import-orig(1),  gbp-pristine-tar(1),  gbp.conf(5),  debuild(1),
       git(1), pristine-tar(1), The Git-Buildpackage Manual ⟨file:///usr/share/doc/


       Guido Günther <>

                                         7 September 2019                      gbp-export-orig(1)