PACKIT-PREPARE-SOURCES(1)

💖 PACKIT-PREPARE-SOURCES(1) 💖

okay bestie, welcome to the packit prepare-sources manual page — this is the packit prepare-sources bit of the packit fam, and honestly? it's giving ✨build pipeline main character✨. no cap.

---

🌸 NAME 🌸

packit-prepare-sources — get those sources ready for a brand new SRPM build, like the little pre-game ritual it is 💅

---

🦋 SYNOPSIS 🦋

packit prepare-sources [OPTIONS] [PATH_OR_URL]

---

✨ DESCRIPTION ✨

so here's the vibe: you're prepping sources for a fresh SRPM build, and you're doing it using the content of the upstream repository. that's the whole thing. she does a lot tho:

• figures out the version (determine version, slay)
• creates an archive, or downloads upstream
• creates patches for sourcegit
• fixes/updates the specfile so it points at the right archive
• downloads the remote sources

and if you wanna customize any of that? you can, bestie — behaviour can be tweaked by specifying actions in the configuration: post-upstream-clone, get-current-version, create-archive, create-patches, fix-spec-file. that's your little control panel 🎀

about the PATH_OR_URL argument: it's either a local path or a URL pointing at the upstream git repository. and if you just... don't say anything? it defaults to the current working directory. she's lowkey self-sufficient like that 🫶

---

👑 OPTIONS 👑

• --result-dir DIR — copy the sources into DIR. if you don't say anything, packit makes a prepare_sources_result directory in your current working directory. cute, right? 💖
• --upstream-ref TEXT — the git ref of the last upstream commit in the current branch, aka where packit should start generating patches from. heads up tho: this option implies the repository is source-git. iykyk 🌈
• --merged-ref TEXT — git ref used to identify the correct most recent tag. yes, correct, she's picky and we love that for her ⭐
• --update-release / --no-update-release — do we update Release or not? defaults to whatever's set in the configuration, and that config default is yes. periodt 💅
• --preserve-spec — don't touch the spec file during SRPM creation. iconic if you're a control freak about your spec file. ⚠️ it implies --no-update-release. by default, the spec file does get updated.
• --bump / --no-bump — 🚨 deprecated, bestie. use --[no-]update-release instead. no cap, she's old news.
• --release-suffix TEXT — set your own release suffix. lets you override the default generated:{current_time}.{sanitized_current_branch}{git_desc_suffix}. go off, custom queen 👑
• --default-release-suffix — lets you use the default, packit-generated release suffix when some release_suffix is specified in the configuration. the "actually, never mind, do it your way" option 🙈
• --job-config-index INTEGER — an internal option, fr fr. it overrides the package config found in the repository with a job config with the given index. needed for the packit service, so like... probably not for you unless you're the service 🫡
• --ref TEXT — git reference to checkout. simple as that, bestie ✨
• --pr-id TEXT — specifies which PR to checkout. yes, the PR. that one 🎀
• --merge-pr / --no-merge-pr — should packit merge the PR into the base branch, in case pr-id is specified? your call 💜
• --target-branch TEXT — specifies the target branch that the PR should be merged into. giving very much "where are we landing this" energy 🦋
• --create-symlinks / --no-create-symlinks — should Packit create symlinks, or copy the files (e.g. an archive outside the specfile dir)? choose your fighter 💀
• -p, --package TEXT — which package to prepare, in case there's more than one available — like in a monorepo configuration. use it multiple times to select multiple packages. defaults to all the packages listed inside the config. 🌈

---

and that's the whole page, bestie!! go forth and prepare those sources 💖✨🎀

this was packit prepare-sources, version 1.16.3, dated 2026-09-04 — from the packit prepare-sources manual. mwah, stan her, bye 🫶💅