gbp-import-srpm(1)

📦
version 0.9.43 · 6 versions
, in ubuntu stonking

💖 gbp-import-srpm — git-buildpackage Manual, bestie edition 💖

okay so. picture this: you got a source RPM. you want it in a Git repo. you do NOT want to do it by hand. enter gbp import-srpm, my beloved. this page is the gbp-import-srpm(1) manual, but make it make sense. 🦋

✨ NAME ✨

gbp-import-srpm — import source RPM packages into a Git repository. that's it. that's the whole job. slay. 💅

🌸 SYNOPSIS 🌸

gbp import-srpm [--version] [--help] [--verbose] [--color=[auto|on|off]]
                [--color-scheme= COLOR_SCHEME] [--vendor= VENDOR]
                [--allow-same-versions] [--author-is-committer]
                [--packaging-branch= BRANCH-NAME] [--packaging-tag= TAG-
                FORMAT] [--skip-packaging-tag] [--packaging-dir=
                DIRECTORY] [--filter= PATTERN] [--keyid= GPG-KEYID]
                [--[no-]create-missing-branches] [--[no-]pristine-tar]
                [--[no-]sign-tags] [--upstream-branch= BRANCH-NAME]
                [--upstream-tag= TAG-FORMAT] [--upstream-vcs-tag= TAG-
                FORMAT] [--native] [--repo-user= [GIT|DEBIAN]]
                [--repo-email= [GIT|DEBIAN]] SRPM | DIRECTORY [target]
gbp import-srpm [options] URL [target]

so you literally hand it an SRPM, or a DIRECTORY, or a URL, and optionally a target. and it eats. 🍓

👑 DESCRIPTION 👑

ngl, this is the glow-up you've been waiting for. gbp import-srpm imports an RPM source package into a Git repository, notes the package version in the commit logs, and commits the change. it's giving ✨automation✨.

the way it just knows things? iconic. all information, including package name, version and upstream source, is automatically detected from the source package. but bestie, you're the main character — you can override the location of the new repository by optionally specifying the target argument, no cap. 🫶

the tool supports importing both archived (src.rpm files) or unpacked (directory) source RPMs. and YES it also imports from http(s)-URLs. versatile queen. 🌈

💅 OPTIONS 💅

here's the menu, bestie. every single one. no skipping, i would never do that to you.

  • --version — Print version of the program, i.e. version of the git-buildpackage suite. gotta know what era of the suite you're in. ⭐
  • -v, --verbose — Verbose execution. it tells you EVERYTHING. let her yap. 🗣️
  • -h, --help — Print help and exit. the "wait what was that flag again" button. 😭
  • --color=[auto|on|off] — Whether to use colored output. aesthetic matters. 🎀
  • --color-scheme=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, --git-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). fully customizing your terminal's vibe check fr fr. 🌈
  • --vendor=VENDOR — Distribution vendor name. who's your distro parent, basically. 👑
  • --upstream-branch=BRANCH-NAME — The branch in the Git repository the upstream sources are put onto. Default is upstream. the classic. 💜
  • --packaging-branch=BRANCH-NAME — The branch in the Git repository the packaging files are put onto. Default is master. yes, master, she said what she said. 💀
  • --[no-]sign-tags — GPG sign all created tags. put a little signature on it like a perfumed letter. 💖
  • --keyid=GPG-KEYID — Use this keyid for gpg signing tags. which key is doing the signing today. 🔥
  • --packaging-tag=TAG-FORMAT — Use this tag format when tagging released versions, default is %(vendor)s/%(version)s. ✨
  • --skip-packaging-tag — Do not create packaging tag after importing the packaging files. sometimes we simply don't tag. we skip. slay the urge. 🙈
  • --upstream-tag=TAG-FORMAT — Use this tag format when tagging upstream versions, default is upstream/%(version)s. 💅
  • --upstream-vcs-tag=TAG-NAME — Add TAG-FORMAT as an additional parent of the commit of the upstream tarball. Useful when upstream uses git and you want to link to its revision history. TAG-FORMAT can be a pattern similar to what --upstream-tag supports. it's giving connected lore. 🔗
  • --git-packaging-dir=DIRECTORY — Subdirectory where to put the RPM packaging files. tuck them away in their little room. 🏠
  • --filter=PATTERN — Filter out files glob-matching pattern. Can be given multiple times. bye bye unwanted files. 👋
  • --pristine-tar — Generate pristine-tar delta file. ✨
  • --allow-same-version — Allow one to re-import a package with an already existing version. This will not re-import the upstream sources - only packaging files will be re-imported. recycling is self-care. ♻️
  • --author-is-committer — Use the author identity as the committer when importing upstream sources and packaging files. one person, both roles, main character energy. 👑
  • --[no-]create-missing-branches — Create missing upstream and/or packaging branch if missing. if she's not there, make her. 🦋
  • --orphan-packaging — Import packaging files into an orphan branch that will not be based on the upstream branch. Useful if you want to maintain (non-native) package using the 'orphan-packaging' model. This option have no effect if --native is used. aka she stands alone. 🫶
  • --native — Treat the package as native package. No separate upstream branch or upstream tags will be created. no upstream, no tags, just the package. minimalist. 🤍
  • --repo-user=[GIT|DEBIAN] — When set to DEBIAN use the DEBFULLNAME environment variable to set the user.name Git configuration otherwise use Git's defaults. Only affects newly created repos. 👀
  • --repo-email=[GIT|DEBIAN] — When set to DEBIAN use the DEBEMAIL environment variable to set the user.email Git configuration otherwise use Git's defaults. Only affects newly created repos. 📧

📚 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 live there, go visit them. 🏡

🔍 SEE ALSO 🔍

go read these too, bestie, we support women's wrongs and also women's documentation:

🎀 AUTHOR 🎀

Markus Lehtonen <markus.lehtonen@linux.intel.com> — thank you for your service, king. 🫡

that's the whole page bestie!! you read every single line and i'm so proud of you. now go import an SRPM and be iconic about it. 💖✨

git-buildpackage Manual · 26 May 2026 · gbp-import-srpm(1) — mwah, go forth and commit, and remember: if the docs confuse you, it's not a you problem, it's a manpage problem. 💅🌸🦋

📦 where this page comes from