gbp-export-orig(1)

📦
version 0.9.43 · 6 versions
, in ubuntu stonking

🦋 gbp-export-orig(1) — the git-buildpackage manual, but make it cute 🦋

okay bestie, sit down, hydrate, because we're talking about gbp export-orig from the git-buildpackage manual and honestly? it's a whole vibe. it's giving "I just want my upstream tarballs without doing a full build" and honestly, same.

✨ NAME ✨

gbp-export-orig — recreate upstream tarballs from a Git repository 💖

no cap, that's literally the whole job. tarball go brrr. 🎀

✨ SYNOPSIS ✨

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] [--[no-]pristine-tar-commit]
                [--upstream-signatures=[auto|on|off]]

look at all those flags, she's got range 💅

✨ DESCRIPTION ✨

so gbp export-orig is the girl whose entire personality is exporting upstream tarballs out of a Git repository. 🌸

normally those upstream tarballs get made by gbp buildpackage whenever they're needed — like, it handles it, it's fine, she's got it. but if you don't want to actually perform a build (mood, honestly, sometimes you just don't) then this command is your bestie. 🫶

✨ OPTIONS ✨

  • --verbose — verbose execution. she tells you everything. 🔍
  • --color=[auto|on|off] — whether to use colored output. pick your fighter. 🌈
  • --color-scheme=COLOR_SCHEME — the colors to use in output (when color is enabled, obviously, no point painting an invisible canvas 💀). the format for COLOR_SCHEME is '<debug>:<info>:<warning>:<error>'. numerical values and color names are both accepted, and 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. iconic, tbh.
  • --upstream-branch=BRANCH_NAME — branch to build the orig tarball from if --upstream-tree is set to BRANCH. default is upstream. 🍓
  • --[no-]submodules — include git submodules in the orig tarball. let the submodules in, they're part of the family now. 👑
  • --upstream-tag=TAG-FORMAT — use this tag format when looking for tags of upstream versions. default is upstream/%(version)s. periodt.
  • --force-create — force creation of an orig tarball, which means overwriting a pre-existing one if present. ⚠️ bestie she will simply replace it, so know what you're doing.
  • --upstream-tree=[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 --upstream-branch option.

other values are interpreted as treeishs. 🧚

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

  • --tarball-dir=DIRECTORY — search for original tarballs in DIRECTORY instead of generating them. DIRECTORY can contain a version format substitution pattern, eg: foo-%(version)s. she'll go looking instead of making ✨
  • --compression=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. choose your crunch 💅
  • --compression-level=LEVEL — specifies the upstream tarball compression level if an upstream tarball needs to be built. squeeze accordingly.
  • --component=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. she's still figuring herself out, be nice. 🙈
  • --pristine-tar — use pristine-tar when generating the upstream tarball if it doesn't exist. 🔥
  • --pristine-tar-commit — 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. she commits, she's responsible 💖
  • --upstream-signatures=[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

slay. copy, paste, go off. 🎀

✨ CONFIGURATION FILES ✨

several gbp.conf files are parsed to set defaults for the above command-line arguments. see the gbp.conf(5) manpage for details. your defaults are pre-loaded, she remembers everything about you 🥰

✨ SEE ALSO ✨

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/git-buildpackage/manual-html/index.html⟩

go read the whole extended universe, iykyk 📚✨

✨ AUTHOR ✨

Guido Günther <agx@sigxcpu.org> — the legend, the moment, the main character 👑

okayyy and that's the whole page bestie!! this was the git-buildpackage Manual version, dated 26 May 2026, and the page is gbp-export-orig(1). 💜 no cap, you're gonna export the prettiest tarballs. go be great. 🦋💅🌟

📦 where this page comes from