Otto Liljalaakso
f43c57ca89
Previously, `fedrq` was only mentioned in the Utilities page. On the other hand, Package Update Guide did not have anything about checking for affected dependents. Move `fedrq` usage instructions to that page, so it is part of a document describing a full workflow, rather than just in a list of random tools. The new _Finding dependents_ section in Package Update Guide is quite short for such a complicated topic. It can be extended later. The purpose of this change is not to exhaustively cover that topic. The purpose is just to move the existing coverage of `fedrq` abd checking for affected packages.
1.6 KiB
A number of utilities are available to support package maintainers in maintaining their packages. This page attempts to list them, but is not a complete list.
Testing new builds with pull requests and CI
See Pull Request Guide.
Running fedora-review on review tickets using fedora-review service
The Fedora Review Service automatically runs fedora-review on new package review tickets.
One can add a comment with [fedora-review-service-build] to re-run the review service.
Automating package updates: Packit
Packit is a service that enables automated pull request creation for new upstream releases. More information on configuring dist-git repositories to use Packit can be found in the documentation.
Please remember to run impact checks before pushing updates.
fbrnch: an advanced packager tool
If you maintain larger package sets or want additional features/checks over fedpkg and other tools (like fedora-review), you can install fbrnch (pronounced f-branch). The readme file has an overview of its features, but some of the main highlights are:
-
automated parallel builds in dependency order in a sidetag
-
easy scratch, mock builds, waitrepo, and merging for a package branch
-
listing, creating and updating package reviews
-
requesting new package repos and importing directly from package reviews
-
updating sources and much more