|Building Debian Packages with git-buildpackage: Version: 0.8.13|
gbp pq [
gbp pq helps one to manage quilt patches in Debian packages that are maintained with gbp. This is especially useful with packages using the 3.0 (quilt) source format. With gbp pq, you can maintain the quilt patches that should be applied to a package on a separate branch called patch-queue branch. So if your Debian package lives on master, the associated patch-queue branch will be called patch-queue/master.
See https://honk.sigxcpu.org/piki/development/debian_packages_in_git/ for example workflows.
Create a patch queue branch from quilt patches in debian/patches/ that are listed in debian/patches/series. The patches must apply without fuzz.
Export the patches on the patch-queue branch associated to the current branch into a quilt patch series in debian/patches/ and update the series file.
Switch to the patch-queue branch associated to the current branch and rebase it against the current branch.
Drop (delete) the patch queue associated to the current branch. So if you're on branch foo, this would drop branch patch-queue/foo.
Add a single patch to the patch-queue similar to using
Switch to the patch-queue branch if on the base branch and switch to base branch if on patch-queue branch.
Print version of the program, i.e. version of the git-buildpackage suite
Print help and exit
Whether to use colored output.
Colors to use in output (when color is enabled). The format for
Numerical values and color names are accepted, empty fields imply
the default color. For example,
Whether or not the patch files should be prefixed with a number.
The default is to export patches with patch numbers. Note,
however, that this normally affects patches whose names are
automatically generated, and has no effect on exporting patches
which have a
The format specifier for patch number prefixes. The default format is '%04d-'.
Whether or not to renumber patches exported from the patch queue,
instead of preserving numbers specified in
Topic to use when importing a single patch
When importing a patch queue fails, go back commit-by-commit on the current branch to check if the patch-queue applies there. Do this at most NUM times. This can be useful if the patch-queue doesn't apply to the current branch HEAD anymore, e.g. after importing a new upstream version.
Whether to automatically drop (delete) the patch queue branch after a successful export
In case of
What meta tags to look for to generate a commit message when
What regular expression should be used to parse out the
bug number when using
How to find the starting point for the patch queue base. The options are DEBIAN, that will use the Debian branch as the base for the patch queue branch, and TAG, that will use the corresponding upstream tag as a base for the patch queue branch.
This is only needed if your upstream branch is not merged in the Debian branch. The default is DEBIAN.
Use this tag format when looking for tags of upstream versions, default is upstream/%(version)s.
When exporting patches from a patch-queue branch, gbp pq will look at the patch header for special tags it recognizes. All tags need to start at the first column and require at least one whitespace after the colon.
Ignores the commit, no patch is generated out of it.
The name to use for the patch when running
gbp pq exportIf unset, it will be formatted like git am would format it.
Moves the patch into a subdir called topic when running
gbp pq exportThis allows for some structure below debian/patches.
|<<< gbp-pull||gbp-create-remote-repo >>>|