gbp-pq-rpm

Create a development (patch-queue) branch by applying all patches from the packaging branch on top of the upstream version. The patches must apply without fuzz.

Export patches from the development branch into the packaging branch. It generates patches (one-per-commit) from the development branch and updates the spec file accordingly. It doesn't automatically commit the changes though - they need to verified and committed manually.

Switch to the development branch and rebase it against the current upstream version (indicated in the spec file of the associated packaging branch).

Drop (delete) the development branch associated to the current branch. For example, you're on branch foo this would drop branch development/foo.

Add a single patch to the development branch - similar to using git-am.

Switch between the development branch and the associated packaging branch.

Convert a package from the "joint-packaging" maintenance model and git-layout to the "orphan-packaging" model. It takes the content of the packaging directory, auto-generates patches and puts these into a new orphan packaging branch. You can use the --retain-history to try to preserve as much of the git history as possible. Converting is a one-time action - conversion back to the "joint-packaging" model is not supported (yet).

Print version of the program, i.e. version of the git-buildpackage suite

Verbose execution

Print help and exit

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

Distribution vendor name.

Branch the packaging files are being maintained on. Only relevant if a invariable/single development (pq-branch) is defined with --pq-branch, in which case this is used as the "base" branch.

Name (format string) of the development (patch-queue) branch. The following string fields are accepted: "%(branch)s" (the base branch, i.e. the packaging branch that the development branch is associated to), "%(upstreamversion)s" (the upstream version), "%(release)s" (the rpm patchlevel, i.e. Release), "%(version)s" (full rpm package version).

Subdirectory that contains the RPM packaging files.

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

Use this tag format when looking for tags of upstream versions, default is upstream/%(version)s.

Import even if the development (patch-queue) branch already exists. Only valid for the import action.

Comma-separated list of additional file(s) to import from packaging branch. These will appear as one monolithic patch in the development (patch-queue) branch. By default, the local gbp conf files are imported in order to try to ensure that gbp sees the same settings on the development (pq) branch as on the packaging branch.

Export patches from TREEISH instead of the default which is HEAD of the development (patch-queue) branch.

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

Directory where packaging files are put in the new orphan packaging branch after convert. If --new-packaging-dir= is not defined, packaging-dir is used.

Try to preserve as much history as possible when converting. That is, for each commit in the old branch create one corresponding commit in the new orphan packaging branch. However, commits that will not generate any changes are skipped (i.e. no empty commits are generated) - these are caused e.g. by changes in files that are ignored by patch-generation.

Ignores the commit, no patch is generated out of it.

Conditional patch. Put patch inside "%if <expression>" in the spec file.

Conditional patch. Put patch inside "%ifarch <expression>" in the spec file.