gbp-pristine-tar(1)

📦
version 0.9.43 · 6 versions
, in ubuntu stonking

✨ gbp-pristine-tar ✨

okay bestie, so this is the git-buildpackage tool that handles your pristine-tar commits — and it's literally called gbp-pristine-tar, and it lives in the git-buildpackage manual. it manages pristine-tar commits in a git repository. no cap. 💖

🌸 SYNOPSIS 🌸

gbp pristine-tar [--version] [--help] [--verbose]
                 [--color=[auto|on|off]] [--color-scheme=COLOR_SCHEME]
                 [--upstream-tag=tag-format]
                 [--upstream-signatures=[auto|on|off]] [--component=component]... commit filename

🎀 DESCRIPTION 🎀

so what it does: gbp pristine-tar adds the pristine-tar commit for a given upstream tarball into a Git repository. that's the whole vibe. 🦋

now, ngl, you're normally not gonna run this yourself — creating new pristine-tar commits is something that happens automatically, done by stuff like gbp import-orig. the tool does it for you while you're off being the main character. ✨

but here's where it eats: this command is still useful when your original tarball is already imported and you want the pristine-tar commits added later, at some point in the future. or — if you're tracking upstream git and you want to create pristine-tar commits anyway, no matter what. so yeah, it's giving "backup plan that slays". 👑

💅 OPTIONS 💅

  • --version — print the version of the program, like the version of the whole git-buildpackage suite. it's the "who am i" moment. 🌈
  • -v, --verbose — verbose execution. it says more stuff. we love a chatty icon. 🗣️
  • -h, --help — print help and exit. your little map, bestie. 🗺️
  • --color=[auto|on|off] — whether to use colored output. pick your aesthetic. 🎨
  • --color-scheme=COLOR_SCHEME — the colors to use in output (when color is enabled, obvi). 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, --git-color-scheme='cyan:34::' would show debug messages in cyan, info messages in blue, and other messages in default — which means warning and error messages show up in red. so like, custom palette, periodt. 💜
  • --upstream-tag=tag-format — use this tag format when tagging upstream versions. the default is upstream/%(version)s. 🏷️
  • --upstream-signatures=[auto|on|off] — whether upstream signatures should be imported as well. off turns this off completely. on always tries to import a signature — which can be useful if you want things to fail when e.g. uscan did not fetch a signature (yes that's a feature, dramatic but correct 😭). the default auto means: import a signature file if it's present, but do nothing otherwise. very "read the room" energy. 🙈
  • --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. ⚠️ so don't get too attached, bestie.

🔥 EXAMPLES 🔥

add pristine-tar commits for an upstream tarball:

gbp pristine-tar commit ../upstream-tarball-0.1.tar.gz

same as above but with an additional tarball ../upstream-tarball-foo-0.1.tar.gz:

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

look at that, two whole tarballs, ate and left no crumbs 🍓

🧚 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. it's the "set it and forget it" zone. ✨

👑 SEE ALSO 👑

🫶 AUTHOR 🫶

Guido Günther <agx@sigxcpu.org> — thank you for your service, king 👑

okay and for the cute sign-off: this lil page comes from the git-buildpackage Manual, dated 26 May 2026, section gbp-pristine-tar(1). that's the whole thing bestie, go make some pristine-tar commits 💖✨🎀

📦 where this page comes from