MPB-FAILEDCONF(1)
π MPB-FAILEDCONF π
okay bestie, gather round, because mpb-failedconf is here to save your whole entire weekend. it lives in section 1 of the manual (iykyk), and it does one thing and it does it gorgeously.
β¨ NAME β¨
mpb-failedconf β generate a new configuration out of failed packages π«Ά
πΈ SYNOPSIS πΈ
mpb-failedconf [OPTION]...
that's it. that's the whole vibe. just options, no positional nonsense. slay.
π¦ DESCRIPTION π¦
okay so picture this, bestie. you're working on a new version for a package, right? and you run mpb build 89 and it comes back with 25 failures β all because of a bug you introduced π (not me, not me, it was me).
so you fix the bug. iconic. and now you wanna give it another try... but the thought of rebuilding all 584 packages again? absolutely not. no. we're not doing that. that's giving "let me waste my entire afternoon" energy and we are simply not participating.
this is where mpb-failedconf shows up like the main character she is. she's a dedicated tool that generates a configuration file containing the list of packages that failed from a given mpb build. that's it. that's the job. and she ate. π
$> mpb-failedconf -b 54
so say your 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 it gets stored in the current directory. cute, predictable, we love her.
but what if you want a different name and path? no problem bestie, just say so with the --output option:
$> mpb-failedconf -b 54 -o my-new-build.config
note:mpb-failedconfgenerates a new configuration file. which means it won't help you solve cyclic build dependencies issues. that's just not the assignment, okay? if you wanna rebuild packages that failed in a given build while still using the same project, you should give thempb --rebuildcommand a try instead. different tool, different vibe. π§
β OPTIONS β
-h,--helpβ show the help message and exit. the classic. the icon. the "hello yes I would like to know things" option.--verbose,-Vβ increase output verbosity. and the way that you can pass this multiple times to modify the amount of information provided (e.g.-VV)... obsessed. other options are affected by the verbosity level too, and may give you different information depending on it. so it's not just noise, it's context. π--version,-vβ show the program version and exit. lowercasevbestie, don't get it twisted with the capitalVup there. π--buildid,-bBUILDID β use this one to specify whichmpbbuild needs to be worked on. this is the whole point of the tool, so like, probably don't skip it.--output,-oOUTPUT β where to store the new configuration. your file, your rules. π--status,-sSTATUS β the kind of status to list packages for. can be any of:failed,unconfirmed,check_neededandall. pick your fighter. π
π₯ RESOURCES π₯
more information about the mass-prebuilder can be found at https://gitlab.com/fedora/packager-tools/mass-prebuild. go read it, it's giving documentation excellence.
π SEE ALSO π
and that's the whole page bestie!! this manual entry is from the mpb-failedconf source, dated 2026-08-27 β so yeah, it's a whole year's worth of fresh. now go forth, regenerate only the packages that actually failed, and live your best efficient life. πβ¨ππ
π¦
π¦ where this page comes from
- fedora 44: mass-prebuild 1.8.0-5.fc44 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms