ebranch(1)

📦
version 0.27.0 · 5 versions
, in fedora 43, fedora 44

👑 ebranch — straight outta the Sandogasa Manual 💅

okay bestie, sit DOWN, we're doing cross-branch porting and it's gonna be iconic 🦋

✨ NAME ✨

ebranch — cross-branch porting: build order, branch requests, update checks, Bodhi karma. that's the whole vibe, no cap 🎀

🌸 SYNOPSIS 🌸

ebranch [-h|--help] [-V|--version] <subcommands>

💜 DESCRIPTION 💜

Cross-branch porting: build order, branch requests, update checks, Bodhi karma. yes it's the same sentence twice, that's the assignment, don't @ me 🙈

💅 OPTIONS 💅

  • -h, --help — print help 🫶
  • -V, --version — print version ⭐

🔥 COMMANDS 🔥

ebranch check-crate

ebranch check-crate [--from] [-b|--branch] [-r|--repo] [-t|--transitive]
[--exclude-dev] [--include-optional] [--features]
[--no-default-features] [--in-tree] [--copr] [--package]
[--exclude-unmet] [--exclude] [--copr-script] [--dot] [--json] [--koji]
[--toml] [--refresh] [-v|--verbose] [-j|--jobs] [-h|--help] [NAME]
[VERSION]

Analyze a crates.io crate's dependencies. it's giving detective 🔍

  • --from <PATH> — render a report you saved earlier with --toml instead of querying crates.io and the repo all over again. recycling era ♻️
  • -b, --branch <BRANCH> — the target branch, bestie (like epel9, rawhide)
  • -r, --repo <REPO> — repository class for that branch (fedrq -r)
  • -t, --transitive — expand those missing deps transitively, go deep 🌊
  • --exclude-dev — keep dev dependencies out of the transitive expansion, we don't need that energy
  • --include-optional — for an application root, also count optional dependencies that its default features don't enable. but library roots and every transitive crate count all features, because that's how Fedora builds them, periodt
  • --features <FEATURE,...> — non-default features the Fedora build enables for an application root, exactly like %cargo_generate_buildrequires -f would (CSV or repeated, pick your fighter). default: read from the package's rawhide spec when it already exists 👑
  • --no-default-features — build without default features (-n)
  • --in-tree <GLOB,...> — crates built in-tree from the root's own source (you know, a workspace's members, like uu_*,uucore*): they get hidden as dependencies, and their own dependencies get checked as the workspace's. globs, CSV or repeated; @repository also grabs every crate published from the root's repository. this merges with the config file's [check-crate.in-tree] entry for the crate 🧚
  • --copr <OWNER/PROJECT> — a staging COPR (owner/project, @group/project) layered over the branch: dependencies the branch is missing get looked up there too, and they're reported as staged — built, still in flight — instead of missing. the branch picks the chroot (rawhide → fedora-rawhide). default: the config file's [check-crate.copr] entry for the crate. (and btw the build-script generator is --copr-script, don't get it twisted 🙈)
  • --package <NAME> — the Fedora package name, for when it's not rust-<crate> (classic example: the coreutils crate is uutils-coreutils). used for the spec lookup and as the report's package name
  • --exclude-unmet — kick unmet-version dependencies (packaged, but too old for the requirement) out of the transitive expansion. they're included by default, because omitting them silently under-reports what needs (re)building — and lying in a report is not the move 💀
  • --exclude <CRATE,...> — ignore these crates entirely, direct or transitive, as dependencies Fedora won't package (CSV or repeated). added to the config file's [check-crate] exclude, or, when no config sets one, added to the built-in benchmark set (criterion, codspeed-*, divan, iai, count_instructions)
  • --copr-script — generate a shell script for Copr batch builds (heads up: check-crate's --copr names the staging COPR a check reads from, totally different thing).

the script accepts the Copr repo as its first argument, followed by any extra flags to pass to copr build-package. slay 🎀

  • --dot — output dependency graph in Graphviz DOT format
  • --json — machine-readable JSON output
  • --koji — output build-order as a Koji chain build string
  • --toml <PATH> — write analysis to a TOML file
  • --refresh — clear fedrq + libdnf5 repo metadata caches before querying. fresh start energy ✨
  • -v, --verbose — print progress to stderr
  • -j, --jobs <JOBS> — parallel fedrq queries (0 = CPUs)
  • -h, --help — print help (see a summary with -h)
  • [NAME] — crate name on crates.io
  • [VERSION] — crate version (default: latest)

ebranch check-pkg-reviews

ebranch check-pkg-reviews [--bugzilla-url] [--api-key] [--dry-run]
[-v|--verbose] [-h|--help] <TOML>

Find and link Bugzilla package review requests 🦋

  • --bugzilla-url <BUGZILLA_URL> [default: https://bugzilla.redhat.com] — Bugzilla base URL
  • --api-key <API_KEY> — Bugzilla API key (or set the BUGZILLA_API_KEY env var). it may also be specified with the BUGZILLA_API_KEY environment variable 🔑
  • --dry-run — show changes without applying them. window shopping only 🛍️
  • -v, --verbose — print progress to stderr
  • -h, --help — print help
  • <TOML> — path to a TOML analysis file from check-crate --toml

ebranch check-update

ebranch check-update [-b|--branch] [-r|--repo] [--testing-branch]
[--koji-profile] [--json] [--detailed] [-v|--verbose] [--refresh]
[-j|--jobs] [--give-karma] [--comment] [-y|--yes] [--submit] [--notes]
[--notes-file] [--type] [--severity] [--bug] [--stable-karma]
[--unstable-karma] [--disable-autokarma] [--rpmfusion-inventory]
[--rpmfusion-renames] [--rpmfusion-dry-run] [--rpmfusion-file]
[-h|--help] <INPUT>

Check if an update would break reverse dependencies. the group project nobody wants but everybody needs 😭

  • -b, --branch <BRANCH> — branch to check against (e.g. epel9).

auto-detected from the input: the Bodhi release for an update alias, or the name of a side tag (f43-build-side-* uses f43, epel9-build-side-* uses epel9). a plain EPEL branch, whether inferred or given, is checked against its base distro plus -r @epel: epel8 → al8, epel9 → al9, epel10 → c10s, and it says so on stderr. minor releases (epel10.1) have no assumed base: pass -b and -r yourself — which you can do to override anyway, e.g. -b c9s -r @epel 💅

  • -r, --repo <REPO> — repository class for the branch (fedrq -r).

defaults to the branch's stable base repos, which is the correct comparison baseline, and to @epel for a plain EPEL branch (see -b). passing -r turns that mapping off: pair it with a base branch, e.g. -b c9s -r @epel

  • --testing-branch <TESTING_BRANCH> — override the branch for the new-provides queries: @testing for Bodhi updates, and the chroot selection for COPR input (epel9 → epel-9-*).

it's kept as the EPEL branch when -b is mapped to its base (epel9 → al9 queries epel9 here); auto-detected for EPEL side tags (epel9-build-side-* uses epel9). otherwise it defaults to --branch 🌈

  • --koji-profile <KOJI_PROFILE> — Koji CLI profile (e.g. cbs for CentOS)
  • --json — machine-readable JSON output
  • --detailed — show full lists (every package, Provide, and reverse dep) instead of counts plus the actionable problems. lore dump mode 📚
  • -v, --verbose — print progress to stderr
  • --refresh — clear fedrq + libdnf5 repo metadata caches before querying
  • -j, --jobs <JOBS> — parallel fedrq queries (0 = CPUs)
  • --give-karma — cast karma on the Bodhi update. the check result suggests the value (+1 when no issues are found, -1 when reverse deps break or the updated packages have unsatisfied deps, 0 when the analysis was incomplete); you get prompted with that suggestion as the default. requires a Bodhi update alias or URL as input. reuses the bodhi CLI's login session, and starts an interactive login first if there's none 🫶

listed bugs get per-bug feedback: update-request bugs (<pkg>-<version> is available) are auto-voted +1 when the update delivers at least the requested version and -1 otherwise; for other bugs you get prompted. the full plan is shown for confirmation before posting. no surprises here, bestie ✅

  • --comment <COMMENT> — reviewer notes added as a section near the top of the posted report (with --give-karma, or the review comment --submit posts after creating the update). prompted for interactively when omitted; --yes skips the prompt 💬
  • -y, --yes — skip vote/submit confirmations; non-update bugs get 0
  • --submit — submit the side tag as a Bodhi update once the check passes: it creates the update from the tag (the API behind bodhi updates new --from-tag) after showing the plan — packages, type, bugs, karma thresholds, notes — for confirmation, so an accidentally missing package is caught before anything gets published. requires a Koji side tag as input and update notes via --notes or --notes-file. reuses the bodhi CLI's login session, starting an interactive login first if there is none 🚀

after submitting, the check report is posted on the new update as a review comment with per-bug feedback (whether each listed bug is addressed by the delivered versions) — that's the --give-karma flow; Bodhi zeroes the submitter's own overall karma, but per-bug feedback still counts ✨

when the check does NOT pass cleanly you can curate the findings (keep/explain/remove) like --give-karma; if findings are kept you get asked whether to submit anyway (default no).

non-interactive runs and --yes never submit a failing update. the safety rails are ON 💀
  • --notes <NOTES> — update notes/description (inline)
  • --notes-file <PATH> — read the update notes from a file
  • --type <TYPE> [default: bugfix] — type: bugfix, enhancement, security, newpackage
  • --severity <LEVEL> — update severity: unspecified (default), low, medium, high, or urgent. Bodhi requires a real severity for --type security, so don't skimp 🎯
  • --bug <ID> — bug ID(s) to associate and close (repeated or CSV)
  • --stable-karma <N> [default: 3] — karma needed to push stable (default 3)
  • --unstable-karma <N> [default: -3] — negative karma that unpushes (default -3)
  • --disable-autokarma — don't auto-push at the karma thresholds 🛑
  • --rpmfusion-inventory [<PATH>] — RPM Fusion inventory (poi-tracker sync-rpmfusion). a package with a counterpart there never auto-pushes. without a path, it uses the inventory you generated, or the one your packages shipped 📦
  • --rpmfusion-renames <PATH> — Fedora-to-RPM-Fusion renames for counterparts the naming doesn't make guessable (configs/rpmfusion/renames.toml). found beside the inventory when not given
  • --rpmfusion-dry-run — do everything except send: show the RPM Fusion bug or comment that would be written, and where 👀
  • --rpmfusion-file — go file the RPM Fusion rebuild request for an update that's already been submitted. ✨ Yeah bestie, --submit files these automatically for the update it makes — this flag is for the ones it can't reach: an update submitted through Bodhi's web UI, one that predates this flag, or one whose earlier run stopped somewhere between the submit and the filing. 🙈

Give every alias for the same change in one run, so they all become one bug listing all of them — exactly like a batch of side tags would. 👑

  • -h, --help — Print help (see a summary with -h). 💅
  • <INPUT> — the update(s) to check, each one of:
    • a Koji side tag (f45-build-side-143123)
    • a Bodhi update alias or URL (FEDORA-EPEL-2026-f9eaa11e18)
    • a COPR project: owner/project spec (@rust/uutils-and-nushell) or its URL. COPR input requires -b (-b epel9 also picks the chroot, epel-9-*).

Several may be given, comma-separated or repeated, to carry one change across releases in a single run:

ebranch check-update f45-build-side-1,f44-build-side-2 --submit

They are checked and submitted in order, and every input is validated before any of them is submitted. RPM Fusion is told once per package afterwards, with every update linked — which is why a fan-out belongs in one run: three EPEL minors are one rebuild for them, not three. 💅

🦋 ebranch check-wip

ebranch check-wip [--copr] [--target] [--offline] [--no-offline]
[--prune] [--rescan-reviews] [--side-tag] [--add] [--forget] [--set]
[--package] [--json] [-h|--help] <LEDGER>

Track packages on their way into the distro 🛤️✨

  • --copr <COPR> — COPR staging it (owner/project or URL) 🎀
  • --target <BRANCH,...> — releases targeted (repeated or CSV) 🎯
  • --offline — report from the ledger, contacting absolutely nothing 🙈
  • --no-offline — refresh, overriding a config default 🔄
  • --prune [<WHAT>...] — forget what is gone: packages (default), side-tags 🧹

Possible values:

  • packages: Packages no longer staged in any COPR the ledger follows
  • side-tags: Side tags Koji says no longer exist
  • --rescan-reviews — search for review requests again 🔍
  • --side-tag <TAG,...> — Koji side tags built into (repeated or CSV) 🏷️
  • --add <NAME,...> — track packages no COPR staged (repeated or CSV) ➕
  • --forget <NAME,...> — drop packages and stop tracking them (repeated or CSV) 💀
  • --set <PKG=ROUTE> — set a route: review:BUG, pr:ID, or direct 🧭
  • --package <NAME,...> — limit to these packages (repeated or CSV) 📦
  • --json — machine-readable JSON output 🤖
  • -h, --help — Print help (see a summary with -h). 💅
  • <LEDGER> — ledger file tracking the effort (created if absent) 📓

💖 ebranch close

ebranch close [--claim] [--bugzilla-url] [--api-key] [--fas] [--sig]
[--base-branch] [--dry-run] [-y|--yes] [-v|--verbose] [-h|--help] <TOML>
<BRANCH>

Close branch requests whose package has landed 🛬✅

  • --claim — also take the bugs being closed (assigned_to = your Bugzilla account), without asking 😤
  • --bugzilla-url <BUGZILLA_URL> [default: https://bugzilla.redhat.com] — Bugzilla base URL 🌐
  • --api-key <API_KEY> — Bugzilla API key (defaults to BUGZILLA_API_KEY env var or the key from ebranch config) May also be specified with the BUGZILLA_API_KEY environment variable. 🔑
  • --fas [<FAS>] — volunteer as co-maintainer of the package. 🫶
    • (omitted) — file without volunteering
    • --fas — the FAS from ebranch config
    • --fas NAME — that FAS

A bare --fas takes the next word as the name, so put it last or separate the positionals with --:

ebranch file-requests --fas -- pkgs.toml epel10
  • --sig <SIG> — Packaging SIG to offer as co-maintainer (requires --fas) 🧚
  • --base-branch <BRANCH> — base-distro branch behind the EPEL branch, checked before filing: a package present in the base distro is skipped (EPEL must not replace it; the request would be CANTFIX). ⚠️

Inferred from the branch: epel10 uses c10s, epel9 uses al9. Pass this to override the mapping or to enable the check for branches it can't infer (e.g. epel8).

  • --dry-run — show what would happen without contacting Bugzilla 😇
  • -y, --yes — file releng tickets without confirming each one 🙈
  • -v, --verbose — print progress to stderr 📢
  • -h, --help — Print help (see a summary with -h). 💅
  • <TOML> — check-crate or resolve report TOML with recorded branch requests 📄
  • <BRANCH> — EPEL branch to request (e.g. epel9, epel10) 🌿

🎀 ebranch config

ebranch config [-h|--help]

Set up Bugzilla API key and other settings ⚙️✨

  • -h, --help — Print help 💅

🧹 ebranch copr-prune

ebranch copr-prune [-y|--yes] [--json] [-v|--verbose] [-h|--help] <COPR>

Prune a staging COPR of what its target releases caught up on ✂️📦

  • -y, --yes — delete every caught-up package without asking 😈
  • --json — Print the plan as JSON (never deletes) 🤖
  • -v, --verbose — print progress to stderr 📢
  • -h, --help — Print help 💅
  • <COPR> — COPR project: owner/project, @group/project, or its URL 🌈

🔥 ebranch escalate

ebranch escalate [--bugzilla-url] [--api-key] [--fas] [--sig]
[--base-branch] [--dry-run] [-y|--yes] [-v|--verbose] [-h|--help] <TOML>
<BRANCH>

Escalate (needinfo) stale branch requests in a report 📣😤

  • --bugzilla-url <BUGZILLA_URL> [default: https://bugzilla.redhat.com] — Bugzilla base URL 🌐
  • --api-key <API_KEY> — Bugzilla API key (defaults to BUGZILLA_API_KEY env var or the key from ebranch config) May also be specified with the BUGZILLA_API_KEY environment variable. 🔑
  • --fas [<FAS>] — volunteer as co-maintainer of the package. 🫶
    • (omitted) — file without volunteering
    • --fas — the FAS from ebranch config
    • --fas NAME — that FAS

A bare --fas takes the next word as the name, so put it last or separate the positionals with --:

ebranch file-requests --fas -- pkgs.toml epel10
  • --sig <SIG> — Packaging SIG to offer as co-maintainer (requires --fas) 🧚
  • --base-branch <BRANCH> — base-distro branch behind the EPEL branch, checked before filing: a package present in the base distro is skipped (EPEL must not replace it; the request would be CANTFIX). ⚠️

Inferred from the branch: epel10 uses c10s, epel9 uses al9. Pass this to override the mapping or to enable the check for branches it can't infer (e.g. epel8).

  • --dry-run — show what would happen without contacting Bugzilla 😇
  • -y, --yes — file releng tickets without confirming each one 🙈
  • -v, --verbose — print progress to stderr 📢
  • -h, --help — Print help (see a summary with -h). 💅
  • <TOML> — check-crate or resolve report TOML with recorded branch requests 📄
  • <BRANCH> — EPEL branch to request (e.g. epel9, epel10) 🌿

🌸 ebranch file-request

ebranch file-request [--bugzilla-url] [--api-key] [--fas] [--sig]
[--base-branch] [--dry-run] [-y|--yes] [-v|--verbose] [--blocked]
[--dependson] [--toml] [-h|--help] <PACKAGE> <BRANCH>

File a branch request for one package 📮🎀

  • --bugzilla-url <BUGZILLA_URL> [default: https://bugzilla.redhat.com] — Bugzilla base URL 🌐
  • --api-key <API_KEY> — Bugzilla API key (defaults to BUGZILLA_API_KEY env var or the key from ebranch config) May also be specified with the BUGZILLA_API_KEY environment variable. 🔑
  • --fas [<FAS>] — volunteer as co-maintainer of the package. 🫶
    • (omitted) — file without volunteering
    • --fas — the FAS from ebranch config
    • --fas NAME — that FAS

A bare --fas takes the next word as the name, so put it last or separate the positionals with --:

ebranch file-requests --fas -- pkgs.toml epel10
  • --sig <SIG> — Packaging SIG to offer as co-maintainer (requires --fas) 🧚
  • --base-branch <BRANCH> — base-distro branch behind the EPEL branch, checked before filing: a package present in the base distro is skipped (EPEL must not replace it; the request would be CANTFIX). ⚠️

Inferred from the branch: epel10 uses c10s, epel9 uses al9. Pass this to override the mapping or to enable the check for branches it can't infer (e.g. epel8).

  • --dry-run — show what would happen without contacting Bugzilla 😇
  • -y, --yes — file releng tickets without confirming each one 🙈
  • -v, --verbose — print progress to stderr 📢
  • --blocked <BLOCKED> — CSV of bugs/aliases this request blocks 🚧
  • --dependson <DEPENDSON> — CSV of bugs/aliases this request depends on 🔗
  • --toml <TOML> — check-crate or resolve report TOML to record the new bug ID in 📝
  • -h, --help — Print help (see a summary with -h). 💅
  • <PACKAGE> — source package to request a branch for 📦
  • <BRANCH> — EPEL branch to request (e.g. epel9, epel10) 🌿

🌈 ebranch file-requests

ebranch file-requests [--bugzilla-url] [--api-key] [--fas] [--sig]
[--base-branch] [--dry-run] [-y|--yes] [-v|--verbose] [--blocked]
[-h|--help] <TOML> <BRANCH>

File branch requests for all missing packages in a report 📬📬📬

  • --bugzilla-url <BUGZILLA_URL> [default: https://bugzilla.redhat.com] — Bugzilla base URL 🌐
  • --api-key <API_KEY> — Bugzilla API key (defaults to BUGZILLA_API_KEY env var or the key from ebranch config) May also be specified with the BUGZILLA_API_KEY environment variable. 🔑
  • --fas [<FAS>] — volunteer as co-maintainer of the package. 🫶
    • (omitted) — file without volunteering
    • --fas — the FAS from ebranch config
    • --fas NAME — that FAS

A bare --fas takes the next word as the name, so put it last or separate the positionals with --:

ebranch file-requests --fas -- pkgs.toml epel10
  • --sig <SIG> — Packaging SIG to offer as co-maintainer (requires --fas) 🧚
  • --base-branch <BRANCH> — base-distro branch behind the EPEL branch, checked before filing: a package present in the base distro is skipped (EPEL must not replace it; the request would be CANTFIX). ⚠️

Inferred from the branch: epel10 uses c10s, epel9 uses al9. Pass this to override the mapping or to enable the check for branches it can't infer (e.g. epel8).

  • --dry-run — show what would happen without contacting Bugzilla 😇
  • -y, --yes — just file the releng tickets, no confirmation per ticket, we trust you bestie 💅
  • -v, --verbose — spill the progress to stderr so you can watch it cook 🔥
  • --blocked <BLOCKED> — a CSV of bugs/aliases that every single filed request blocks 🚧
  • -h, --help — print help (peep the summary with -h)
  • <TOML> — a check-crate or resolve report TOML that lists the missing packages. like, the receipts, basically 🧾
  • <BRANCH> — the EPEL branch you're requesting, e.g. epel9, epel10 🌿

✨ ebranch find-cycles ✨

ebranch find-cycles [-s|--source] [--source-repo] [-t|--target]
[--target-repo] [--json] [--report] [--koji] [--copr-script]
[--check-install] [--exclude] [--exclude-install] [--override]
[--base-branch] [--max-depth] [-v|--verbose] [-j|--jobs] [--refresh]
[--graph] [-h|--help] [PACKAGES]

Detect dependency cycles in the build graph 🔄😭 the circular-dependency jump-scare is real and this is how you catch it.

OPTIONS

  • -s, --source <SOURCE> — branch you're pulling packages from (e.g. rawhide) 📥
  • --source-repo <REPO> — repository class for the source branch, that's the fedrq -r thing
  • -t, --target <TARGET> — branch you're porting those packages to (e.g. epel10) 🎯
  • --target-repo <REPO> — repository class for the target branch (fedrq -r)
  • --json — output as JSON instead of the human-readable text, for when a script is the main character 🤖
  • --report <FILE> — write a TOML report (package list + dependency edges) so the branch-request subcommands can snack on it 📝
  • --koji — output the build-order as a Koji chain build string 👑
  • --copr-script — generate a shell script for Copr batch builds 🐍

Heads up: check-crate's --copr is what names the staging COPR a check reads from.

The script takes the Copr repo as its first argument, then any extra flags you wanna hand to copr build-package.

  • --check-install — check that the subpackages are actually installable, no cap 🧐

It verifies that the Requires of every subpackage in the closure can be satisfied by the target repo or by other packages inside the closure.

  • --exclude <PKG,...> — exclude source packages from the closure ✂️

Comma-separated list of source packages you're treating as already available on the target. Their BuildRequires won't get resolved and they won't show up in the closure. Chef's kiss for packages you plan to excise from the build requirements.

May be passed multiple times. 🔁

  • --exclude-install <PKG,...> — exclude packages from the installability checks 🙈

Comma-separated list of source packages. Deps provided by these packages get treated as satisfied and they won't be pulled into the closure. Super useful for things like glibc where a version mismatch between Rawhide and older releases is just... expected, bestie.

May be passed multiple times. 🔁

  • --override <PKG,...> — base-distro packages to treat as deliberate overrides (the alternate, non-conflicting EPEL packages) 💫

Normally, a dependency whose provider already exists in the base distro (RHEL / CentOS Stream) but at a too-old version is blocked: EPEL packages must not replace base-distro packages, so the closure gets pruned right there and the report explains your options. Listing a package here is you confirming you intend to introduce an alternate package instead — and the analysis then descends into it. Note: an alternate package needs a NEW package review, not a branch request. 📋

  • --base-branch <BRANCH> — base-distro branch sitting behind the target, probed to detect deps whose provider exists in the base at a too-old version (because EPEL must not replace base packages) 🛡️

It's inferred for EPEL targets: epel10 uses c10s, epel9 uses al9 (fun fact: fedrq's c9s layers epel9 + epel9-next, and UBI is incomplete, so AlmaLinux stands in for RHEL 9). Pass this to override the mapping or to turn the guard on for targets it can't infer (e.g. epel8).

  • --max-depth <MAX_DEPTH> [default: 0] — max recursion depth (0 = unlimited) 🕳️
  • -v, --verbose — print progress to stderr
  • -j, --jobs <JOBS> [default: 0] — number of parallel fedrq queries (0 = CPUs) ⚡
  • --refresh — clear the fedrq + libdnf5 repo metadata caches before querying 🧼
  • --graph <PATH> — a saved dependency graph of the source branch (a poi-tracker deps graph JSON). Source-side lookups it can answer get served offline; only the frontier, the target and the base actually go to fedrq. slay 🦋
  • -h, --help — print help (see a summary with -h)
  • [PACKAGES] — source RPM names to analyze 🔍

✨ ebranch resolve ✨

ebranch resolve [-s|--source] [--source-repo] [-t|--target]
[--target-repo] [--json] [--report] [--koji] [--copr-script]
[--check-install] [--exclude] [--exclude-install] [--override]
[--base-branch] [--max-depth] [-v|--verbose] [-j|--jobs] [--refresh]
[--graph] [-h|--help] [PACKAGES]

Resolve the full dependency closure for porting 🌈 the whole web, every dep, traced out so you know exactly what has to come along for the ride.

OPTIONS

  • -s, --source <SOURCE> — branch to take packages from (e.g. rawhide) 📥
  • --source-repo <REPO> — repository class for the source branch (fedrq -r)
  • -t, --target <TARGET> — branch to port packages to (e.g. epel10) 🎯
  • --target-repo <REPO> — repository class for the target branch (fedrq -r)
  • --json — output as JSON instead of human-readable text 🤖
  • --report <FILE> — write a TOML report (package list + dependency edges) for the branch-request subcommands to consume 📝
  • --koji — output build-order as a Koji chain build string 👑
  • --copr-script — generate a shell script for Copr batch builds 🐍

Reminder: check-crate's --copr names the staging COPR a check reads from.

The script accepts the Copr repo as its first argument, followed by any extra flags to pass to copr build-package.

  • --check-install — check that subpackages are installable 🧐

Verifies that the Requires of every subpackage in the closure can be satisfied by the target repo or by other packages in the closure.

  • --exclude <PKG,...> — exclude source packages from the closure ✂️

Comma-separated list of source packages to treat as already available on the target. Their BuildRequires will not be resolved and they will not appear in the closure. Useful for packages you plan to excise from the build requirements.

May be passed multiple times. 🔁

  • --exclude-install <PKG,...> — exclude packages from installability checks 🙈

Comma-separated list of source packages. Deps provided by these packages are treated as satisfied and they will not be pulled into the closure. Useful for packages like glibc whose version mismatch between Rawhide and older releases is expected.

May be passed multiple times. 🔁

  • --override <PKG,...> — base-distro packages to treat as deliberate overrides (alternate, non-conflicting EPEL packages) 💫

Normally a dependency whose provider exists in the base distro (RHEL / CentOS Stream) at a too-old version is blocked: EPEL packages must not replace base-distro packages, so the closure is pruned there and the report explains the options. Listing a package here confirms you intend to introduce an alternate package instead — the analysis then descends into it. Note an alternate package needs a NEW package review, not a branch request. 📋

  • --base-branch <BRANCH> — base-distro branch behind the target, probed to detect deps whose provider exists in the base at a too-old version (EPEL must not replace base packages) 🛡️

Inferred for EPEL targets: epel10 uses c10s, epel9 uses al9 (fedrq's c9s layers epel9 + epel9-next, and UBI is incomplete, so AlmaLinux stands in for RHEL 9). Pass this to override the mapping or to enable the guard for targets it can't infer (e.g. epel8).

  • --max-depth <MAX_DEPTH> [default: 0] — max recursion depth (0 = unlimited) 🕳️
  • -v, --verbose — print progress to stderr
  • -j, --jobs <JOBS> [default: 0] — number of parallel fedrq queries (0 = CPUs) ⚡
  • --refresh — clear fedrq + libdnf5 repo metadata caches before querying 🧼
  • --graph <PATH> — saved dependency graph of the source branch (a poi-tracker deps graph JSON): source-side lookups it can answer are served offline; only the frontier, the target and the base go to fedrq 🦋
  • -h, --help — print help (see a summary with -h)
  • [PACKAGES] — source RPM names to analyze 🔍

okay that's the whole page bestie, you made it to the end 🎀💖 this was sandogasa version 0.27.0, dated 2026-10-21, and it's the ebranch(1) manual page. go forth and port those packages, you're literally the main character of EPEL now 👑✨

📦 where this page comes from
  • fedora 43: sandogasa 0.27.0-2.fc43 · (Apache-2.0 OR MIT) AND LicenseRef-Fedora-Public-Domain AND Unicode-3.0 AND Apache-2.0 AND ISC AND MIT AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR ISC OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND BSD-3-Clause AND MPL-2.0 AND (Unlicense OR MIT) AND Zlib
  • fedora 44: sandogasa 0.27.0-2.fc44 · (Apache-2.0 OR MIT) AND LicenseRef-Fedora-Public-Domain AND Unicode-3.0 AND Apache-2.0 AND ISC AND MIT AND (Apache-2.0 OR BSL-1.0) AND (Apache-2.0 OR ISC OR MIT) AND (Apache-2.0 WITH LLVM-exception OR Apache-2.0 OR MIT) AND BSD-3-Clause AND MPL-2.0 AND (Unlicense OR MIT) AND Zlib
  • 💖 girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms