A tool to help Fedora Packagers build package branches.
Fedora developers use a lot of time building packages across releases
and workflow for adding new packages, etc.
fbrnch was made to help (semi-)automate common workflows to save time
and effort, and avoid common some mistakes.
fbrnch is distributed under the GPL license version 2 or later.
fbrnch is a Fedora Packager client which tries to automate some common tasks
- merging and building a package across release branches
- automated parallel builds of sets of packages in dependency order
- easy scratch and mock builds
- progressive copr builds
- creating, updating and listing package reviews
- requesting new repos and branches
- importing new packages and updating packages
- rename master branches to rawhide
Cloning and switching branch
Clone one or more packages:
$ fbrnch clone package ...
There are also options to clone all one's packages or another user's packages.
One can change the branch of one or more packages:
$ fbrnch switch f38 [package] ...
You can also git pull over packages:
$ fbrnch pull [package] ...
List packages and branches
You can list packages in dist-git pagure with
$ fbrnch list PATTERN
Branches of a package can be listed:
$ fbrnch branches -B [package] ...
You can use the
--remote option if you don't have the package checked out.
$ fbrnch status -B [package]
outputs information about the status of each branch.
The status command can also be used with
to check the build status of new packages.
You can output package's nvr's from local git:
$ fbrnch nvr -B [package]
and list package bugs:
$ fbrnch bugs [package]
Commit, Merging and Building in Koji
The update-version command helps with updating a package
after editing the spec file to a newer version:
$ fbrnch update-version
which will download the new tarball and upload it, etc.
bump command can be used to increase the release field for packages.
You can commit to the current branch:
$ fbrnch commit
It uses any rpm changelog for the commit message,
or you can pass
-m "..." or amend with
You can merge branches with:
$ fbrnch merge f37 package
which will offer to merge f38 (or up to a git hash you choose) into f37.
Merging can also be done together with building:
$ fbrnch build f38 package
will ask if you want to merge newer commits from a newer branch,
then push and build it.
If the branch is also already pushed and NVR built it will be skipped.
If the NVR is currently building it will be picked up by
Completed branch builds can be pushed to Bodhi.
You can also build all active branches:
$ fbrnch build -B package
or only all fedora branches:
$ fbrnch build -F package
or only all epel branches:
$ fbrnch build -E package
Scratch builds can also be done:
$ fbrnch scratch rawhide
optionally a different koji
--target can be given.
There are arch short-cut aliases:
You can sort packages by build dependency order:
$ fbrnch sort rawhide package1 package2 package3 package4 ...
$ fbrnch prep rawhide package
$ fbrnch local
this works in the current package dir like other commands,
installing any missing dependencies with
sudo dnf builddep.
(It also works for a non-git package dir.)
Or one can specify the path to the package.
Locally build and install:
$ fbrnch install package1 package2 package3 ...
You can use:
$ fbrnch install-deps [package]
to only install the dependencies of a package.
$ fbrnch rename-rawhide [package]
to rename an old master branch locally to rawhide.
fbrnch can sort packages automatically and build them in parallel
in Koji in dependency layers (using low-priority background builds
to avoid grabbing too many Koji resources).
$ fbrnch parallel --sidetag rawhide pkg-x pkg-y pkg-z pkg-xy pkg-xy-z
builds a list of packages in a sidetag (generating it if needed)
in parallel ordered by build dependencies.
When building for a branch, merging from newer branch will be offered
(though you may prefer to run
fbrnch merge <branch> ... first instead).
Except for rawhide using a --sidetag or --target is required.
If you have more than one active sidetag for a branch,
you can select one using
After parallel building you can create a Bodhi update from the sidetag.
It is also possible to build a package in parallel across branches
and push them to Bodhi.
Creating new packages/branches
Creating a new package
$ fbrnch create-review [my-new-package]
This will create (or update) an srpm, run rpmlint,
then upload it to fedorapeople, perform a scratch build,
and open a Review Request in Bugzilla (similar to fedora-create-review).
Update a package review
$ fbrnch update-review [my-new-package]
Similar to create-review: it uploads the updated files to fedorapeople
and posts the updated package urls to the open package review.
List open package reviews
To list one's open package reviews:
$ fbrnch reviews
They can be filtered by status with various options like
--created (or another bugzilla
One can also search for the review(s) of a specific package with:
$ fbrnch find-review package-name
Once a review has been approved
$ fbrnch request-repos
will request repo(s) for approved package(s) and offer to request branches.
Import a new package
After the repo has been created
$ fbrnch import
will clone the repo(s) and offer to import the srpm
directly from the latest url in the approved package review(s),
which can then be built directly into Koji Rawhide
and the package review(s) updated.
If you prefer you can request branches after the repo is created
(or package is imported) with
$ fbrnch request-branches
which will be prompt for which branches you want, unless already given.
Optionally a mock build per branch can be done first.
There are a lot more commands, like eg
Here is an "extreme" example of a script using
fbrnch copr to do multiple staggered builds.
$ fbrnch --version
$ fbrnch --help
Fedora branch building tool
Usage: fbrnch [--version] COMMAND
A tool to help with updating and building package branches
-h,--help Show this help text
--version Show version
clone Clone packages
switch Switch branch
nvr Print name-version-release
status Status package/branch status
merge Merge from newer branch
unpushed Show unpushed commits
build Build package(s) in Koji
list List packages in pagure
list-local List packages in branch
branches List package branches
parallel Parallel build packages in Koji
sidetags List user's side-tags
override Tag builds into buildroot override in Koji
waitrepo Wait for build to appear in Koji buildroot
scratch Scratch build package in Koji
scratch-aarch64 Koji aarch64 scratch build of package
scratch-x86_64 Koji x86_64 scratch build of package
update-version Update package in dist-git to newer version
sort Sort packages in build dependency order
prep Prep sources
local Build locally
srpm Build srpm
srpm-spec Show the spec file in an srpm
diff Diff local changes
compare Show commits between branches
src-deps List source package dependencies
mock Local mock build
install-deps Install package build dependencies
install Build locally and install package(s)
not-installed Packages not installed locally
bugs List package bugs
bump Bump release for package
commit Git commit packages
pull Git pull packages
fetch Git fetch packages
push Git push packages
owner List package owner(s)
bzusers Search bugzilla users
create-review Create a Package Review request
update-review Update a Package Review
review-package Run fedora-review on a package Review Request bug
reviews List package reviews
request-repos Request dist git repo for new approved packages
import Import new approved created packages from bugzilla
request-branches Request branches for approved created packages
find-review Find package review bug
command Run shell command in package dirs ($p)
copr Build package(s) in Fedora Copr
rename-rawhide Rename local 'master' branch to 'rawhide'
count Count number of living packages
graph Output dependency graph
ftbfs Check FTBFS status
autospec Convert package to use rpmautospec
move-artifacts Move old rpm artifacts into rpmbuild dirs
fbrnch is packaged in Fedora:
sudo dnf install fbrnch.
Build from source
Clone the git repo.
a) using stack (probably 2.3 or later):
b) with cabal-install (probably 2.4 or later) and cabal-rpm:
$ cabal-rpm builddep
$ cabal new-install --installdir=~/bin
fbrnch currently uses these fedora cli tools:
for pushing packages.
It also makes use of:
- rpmbuild & rpmspec
- klist and fkinit
- ssh & scp (for uploading package reviews)
- bugzilla API key
You may want to set
~/.rpmmacros to use particular directories,
since unlike fedpkg, fbrnch follows the local rpmbuild directory macros:
rpmbuild defaults to directories under
but this can be overridden by the user in
~/.rpmmacros as follows.
Two common alternative configurations in
~/.rpmmacros might be either:
- use the package directory for everything (like fedpkg does):
%__pwd %(echo $PWD)
These are easy to find, but do create a lot of clutter.
- Lately I just set _topdir to pwd
%__pwd %(echo $PWD)
With this rpmbuild creates a bunch of dirs in each package dir
(like the ones in ~/rpmbuild/), which can hide srpms and build trees, etc.
Bugzilla API key
fbrnch can share the API of the python-bugzilla CLI tool,
placed either in
api_key = PASTE_YOUR_APIKEY_HERE
You can create your key at
- parallel builds will push local package commits without asking
- currently it only checks if already built by NVR not githash
- authentication is not implemented yet natively for Koji, Bodhi, Pagure
(and source upload)
- so python clients are used for "writing"
(specifically koji, bodhi-client, fedpkg),
but all queries are done directly by Web APIs for speed and control.
- https checkouts are currently treated as anonymous git checkouts
- parallel and sort, etc do not take pkgconfig() and other meta() deps into
account yet (this will be fixed in rpmbuild-order)
Motivation, history, talks
This project started off as a simple tool to build a package across branches
(ie for current releases). Then bugzilla and Bodhi integration was added,
and gradually more features, including some generic commands across packages
inspired by the older fedora-haskell-tools project.
I have given a couple of short talks about fbrnch:
Bug reports, feedback, and pull requests are all highly appreciated.
Do report any unsupported or inconsistent workflow steps.
See the TODO list and also the FIXME comments scattered across the source.
Authors of the code: