gbp-buildpackage-rpm

Don't abort if there are uncommitted changes in the source tree or the current branch doesn't match the PACKAGING-BRANCH.

Don't abort if there are untracked files in the source tree.

Add a git tag after a successful build.

Use BUILD_CMD instead of rpmbuild -ba.

Use CLEAN_CMD.

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 --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).

Whether to send a desktop notification after the build.

Base directory under which temporary directories are created.

Distribution vendor name.

Branch to build the orig tarball from if --git-upstream-tree is set to BRANCH. Default is upstream.

If you're not on this branch when invoking gbp buildpackage-rpm it will fail. Default is master. This is done to make sure you don't accidentally release from a topic branch. Not being on this branch will be ignored when using --git-ignore-new.

Name (format string) of the patch-queue/development branch. This makes building easier when working with separate packaging and development branches.

If --git-patch-export is enabled and gbp buildpackage-rpm detects that the current branch has a patch-queue/development branch it exports the patches from there instead of the tip of the current branch (unless --git-patch-export-rev is defined, of course). Similarly, if the current branch is a patch-queue/development branch gbp buildpackage-rpm will automatically enable patch-export and export packaging files from the packaging branch instead of the current branch (unless --git-export) is defined.

Don't check if the current branch matches PACKAGING-BRANCH.

Include git submodules in the orig tarball.

GPG sign all created tags.

Use this keyid for gpg signing tags.

Excecute COMMAND after tagging a new version.

Exported environment variables are: GBP_TAG (the name of the generated tag), GBP_BRANCH (the branch the package was build from) and GBP_SHA1 (the sha1 of the commit the tag was created at).

Execute COMMAND after successful build.

Exported environment variables are: GBP_CHANGES_FILE (the name of the generated changes file), GBP_BUILD_DIR (the build dir).

Execute COMMAND after exporting the source tree.

Exported environment variables are: GBP_GIT_DIR (the repository the package is being built from), GBP_TMP_DIR (the temporary directory where the sources have been initially exported).

Execute COMMAND from the build directory before calling rpmbuild or the application specified via --git-builder.

Exported environment variables are: GBP_GIT_DIR (the repository the package is being built from), GBP_BUILD_DIR (the build dir).

Enable builder. Note: --git-no-build causes the postbuild hook to be disabled, too.

Enable running all (cleaner, postexport, prebuild, postbuild, and posttag) hooks. Note: the --git-builder command is not affected by this option.

Use this tag format when tagging released versions of the package.

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).

Don't try to create any orig tarball.

Export the packaging files from the current branch head (or the treeish object given via --git-export to DIRECTORY before building.

Build subdirectory options for rpmbuild builder. Of these --git-rpmbuild-sourcedir and --git-rpmbuild-specdir also affects where gbp buildpackage-rpm exports the packaging files under the export directory.

Instead of exporting the current branch head, export the treeish object TREEISH. The special name INDEX exports the current index, WC.TRACKED exports all files tracked by Git in the current working copy as is, WC.UNTRACKED exports all untracked files too whereas WC (or WC.IGNORED) exports all files in the current working directory, even ignored files.

Only export packaging files without running builder.

Subdirectory that contains the RPM packaging files.

Relative path to the spec file to use. Special value auto causes gbp buildpackage-rpm to search and guess. Other values cause the --git-packaging-dir option to be ignored: the directory of the spec file is used, instead.

How to find the upstream sources used to generate the tarball. TAG looks at a tag corresponding to the version in the changelog. BRANCH looks at the upstream branch given via the --git-upstream-branch option. Other values are interpreted as treeishs.

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

Search for original tarballs in DIRECTORY instead of generating them.

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

Prefix (directory) to be used when generating tarballs. Special value auto causes gbp buildpackage-rpm to guess the prefix.

Don't build, only tag and run post-tag hooks.

Don't fail tag operations if a tag with the same version already exists, but, overwrite the existing tag, instead.

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.

Create patches from the commits between the upstream version and export-treeish. That is, after exporting packaging files (from the pacakging directory) gbp buildpackage-rpm creates one patch per commit (similar to git-format-patch) and updates the spec file in the export dir. You use --git-patch-export-rev to specify the tip commit of the patch series.

Use TREEISH as the tip commit of the patch series instead of the default - i.e. treeish from which the packaging files are exported (which is defined with --git-export.

Compress (auto-generated) patches larger than given THRESHOLD bytes. Special value 0 disabled patch compression.

Exclude changes to path(s) matching REGEX in patch generation.

Squash commits up to the given COMMITISH into one monolitic diff. Could be used if one wants to squash commits from an upstream release up to a stable update into a single diff (commits on top of the stable would generate one patch per commit as usual). The format is '<commit_ish>[:<filename_base>]', i.e. commitish optionally followed by a colon and the desired filename base for the diff (suffix '.diff' is automatically added by gbp buildpackage-rpm). Magic word 'HEAD' translates to the patch-export-treeish when given as the squash-point. This allows one to configure gbp to always squash all commits into one monolithic diff.

Whether the patch files should start with a number or not.

gbp buildpackage-rpm always automatically sets/updates the 'VCS:' tag in the spec file after exporting. This option defines the format string for the 'VCS:' tag. An empty value causes no 'VCS:' tag to be inserted and possible old 'VCS:' tag to be removed. Otherwise, the old 'VCS:' tag is updated or a new 'VCS:' tag is added if one does not exist. In the format string '%(tagname)s' expands to the long tag name (from git-describe) and '%(commit)s' expans to the sha1 of the exported commit.