mpb-failedconf - Man Page
generate a new configuration out of failed packages
Synopsis
mpb-failedconf [OPTION]...
Description
Let’s imagine the following use case: you are working on a new version for a package, and noticed through mpb build 89 that you had 25 failures due to a bug that you introduced. After fixing this issue, you want to give it a try, but don´t want to rebuild all the 584 packages yet, only the 25 that failed earlier.
This is where the mpb-failedconf command comes handy. This is a dedicated tool which will generate a configuration file containing the list of packages that failed from a given mpb build.
$> mpb-failedconf -b 54
Assuming the original project build is named my-first-mpb-build, the resulting configuration file will be called my-first-mpb-build.failed.config by default, and will be stored in the current directory. Explicit name and path may be given through the --output option:
$> mpb-failedconf -b 54 -o my-new-build.config
Note: mpb-failedconf generates a new configuration file. Which means it won’t help to solve cyclic build dependencies issues. In order to rebuild packages that failed in a given build, while still using the same project, you should give a try to the mpb --rebuild command.
Options
- -h, --help
- Show the help message and exit. 
- --verbose, -V
- Increase output verbosity. This option may be provided multiple times to modify the amount of information provided (e.g. -VV). Other options are affected by the verbosity level, and may provide different information depending on it. 
- --version, -v
- Show the program version and exit. 
- --buildid, -b BUILDID
- This option is to be used in order to specify which mpb build needs to be work on. 
- --output, -o OUTPUT
- Where to store the new configuration 
- --status, -s STATUS
- The kind of status to list packages for. Can be any of: failed, unconfirmed, check_needed and all 
Resources
More information about the mass-prebuilder can be found at https://gitlab.com/fedora/packager-tools/mass-prebuild.