&rpm-email;
&rpm-firstname; &rpm-surname;
gbp-buildpackage-rpm &dhsection; gbp-buildpackage-rpm Build RPM packages from a Git repository &gbp-buildpackage-rpm; [auto|on|off] COLOR_SCHEME [auto|on|off] =DIRECTORY =VENDOR [auto|on|off] TREEISH BRANCH_NAME BUILD_CMD CLEAN_CMD GPG-KEYID COMMAND COMMAND COMMAND COMMAND TAG-FORMAT TAG-FORMAT [TAG|BRANCH|TREEISH] DIRECTORY LEVEL DIRECTORY TREEISH DIRECTORY FILEPATH =DIRECTORY =DIRECTORY =DISTRIBUTION =ARCHITECTURE =OPTIONS =ROOT =TAG_FORMAT DESCRIPTION &gbp-buildpackage-rpm; is used to build RPM packages from a &git; repository. It is an RPM counterpart for the &gbp-buildpackage; tool that is designed for building Debian packages. &gbp-buildpackage-rpm; will, in order: Verify that it is being executed from the proper location. Verify that the repository doesn't contain any uncommitted source changes. Verify that it is being executed from the correct branch. Export packaging files to a separate build area. Create an orig source tarball if it doesn't exist. Call rpmbuild(1) (or the application specified via ), passing along all command line arguments that don't start with --git-. (Optionally) tag the tree after a successful build. (Optionally) call a post build hook - e.g. to run rpmlint. (Optionally) call a post tag hook - e.g. to push the results to a remote repository after creating the tag. OPTIONS Don't abort if there are uncommitted changes in the source tree or the current branch doesn't match the PACKAGING-BRANCH. Add a git tag after a successful build. Use BUILD_CMD instead of rpmbuild -ba. Use CLEAN_CMD. Verbose execution [auto|on|off] Whether to use colored output. 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). [auto|on|off] Whether to send a desktop notification after the build. =DIRECTORY Base directory under which temporary directories are created. =VENDOR Distribution vendor name. [auto|on|off] Define the 'nativity' of a package. The default value auto makes &gbp-buildpackage-rpm; to guess. Guessing is based on the existence of upstream branch. =BRANCH_NAME Branch to build the orig tarball from if is set to BRANCH. Default is upstream. =BRANCH_NAME 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 . Don't check if the current branch matches PACKAGING-BRANCH. Include git submodules in the orig tarball. GPG sign all created tags. GPG-KEYID Use this keyid for gpg signing tags. COMMAND 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). COMMAND 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). COMMAND 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). COMMAND Execute COMMAND from the build directory before calling rpmbuild or the application specified via . Exported environment variables are: GBP_GIT_DIR (the repository the package is being built from), GBP_BUILD_DIR (the build dir). Enable builder. Note: causes the postbuild hook to be disabled, too. Enable running all (cleaner, postexport, prebuild, postbuild, and posttag) hooks. Note: the command is not affected by this option. TAG-FORMAT Use this tag format when tagging released versions of the package. TAG-FORMAT 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. DIRECTORY Export the packaging files from the current branch head (or the treeish object given via to DIRECTORY before building. =DIRECTORY =DIRECTORY Subdirectories under export directory where packaging files are exported. The default build options of rpmbuild builder are also adjusted accordingly. TREEISH Instead of exporting the current branch head, export the treeish object TREEISH. The special name INDEX exports the current index, WC) exports all files in the current working directory. DIRECTORY Subdirectory that contains the RPM packaging files. FILEPATH Relative path to the spec file to use. Special value auto causes &gbp-buildpackage-rpm; to search and guess. Other values cause the option to be ignored: the directory of the spec file is used, instead. [TAG|BRANCH|TREEISH] 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 option. Other values are interpreted as treeishs. This doesn't have any effect if is being used. DIRECTORY Search for original tarballs in DIRECTORY instead of generating them. LEVEL Specifies the upstream tarball compression level if an upstream tarball needs to be built. 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. Use &mock; to build the rpms by invoking &gbp-builder-mock;. Build for this distribution when using &mock; (e.g.: epel-6). Build for this architecture when using mock, default is to build for the current host architecture. The mock root to use. Defaults to DIST-ARCH from above. Additional options to pass to mock. Default is to pass no additional options. =TAG_FORMAT &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. EXAMPLES Only build a source RPM with &rpmbuild; &gbp-buildpackage-rpm; -bs Build an RPM package with &rpmbuild; on a custom branch with the uncommitted changes included. &gbp-buildpackage-rpm; --git-ignore-branch --git-export=WC &man.gbp.config-files; All options in the config files are specified without the 'git-' prefix. SEE ALSO , , , rpmbuild 8 , mock 1 , , &man.seealso.common; AUTHOR &rpm-username; &rpm-email;