DEBIAN-SVP(1)

💖 DEBIAN-SVP 💖

okay bestie, welcome to debian-svp — it's a User Command and it's literally the Debian-flavoured glow-up of svp(1). ✨

---

🌸 NAME 🌸

debian-svp — create and manage changes against Debian packaging branches 🫶

---

🎀 SYNOPSIS 🎀

debian-svp [-h] [--version] {run,new-upstream,upload-pending,lintian-brush} ...

---

✨ DESCRIPTION ✨

so debian-svp is a specialized version of svp(1) — like, same energy, but with a Debian twist 💅. The main character move: it automatically resolves Debian package names to the URLs of packaging branches. No more hunting for the URL yourself, queen. It also provides support for a couple of Debian-specific operations, because of course it does. 👑

💅 COMMAND OVERVIEW 💅

okay so here's the whole menu, and I am obsessed with how much it does:

• debian-svp run [-h] [--refresh] [--label LABEL] [--name NAME] [--mode {push,attempt-push,propose}] [--dry-run] [--commit-pending {auto,yes,no}] package script — make a change by running a script 🏃♀️. The URL should be the URL of a repository to make changes to. The script gets run in a checkout of the URL, with the opportunity to make changes (go off, script). Depending on the specified mode, the changes will be committed and pushed back to the repository at the original URL, or proposed as a change to the repository at the original URL. pick your vibe. ✨
• debian-svp new-upstream [-h] [--snapshot] [--no-build-verify] [--pre-check PRE_CHECK] [--dry-run] [--mode {push,attempt-push,propose}] packages [packages ...] — create a merge proposal merging a new upstream version 🦋. The location of the upstream repository is retrieved from the debian/upstream/metadata file, and the tarball is fetched using uscan(1). yes, it goes and gets it for you, no cap.
• debian-svp upload-pending — upload pending commits in a packaging branch 📦. that's it. that's the whole thing. iconic.
• debian-svp lintian-brush [--fixers FIXERS] [--dry-run] [--propose-addon-only PROPOSE_ADDON_ONLY] [--pre-check PRE_CHECK] [--post-check POST_CHECK] [--build-verify] [--refresh] [--committer COMMITTER] [--mode {push,attempt-push,propose}] [--no-update-changelog] [--update-changelog] [packages [packages ...]] — create a merge proposal fixing lintian issues 🧹✨. the glow-up your package deserved.

🍓 optional arguments: 🍓

• -h, --help — show this help message and exit. classic. we love a supportive flag 🫶
• --version — show program's version number and exit. who are you? what are you? found out here 💅

---

🌈 EXAMPLES 🌈

1. run lintian-brush(1) on the dulwich package and create a merge proposal with the resulting changes — but with the whole URL, because you're being extra specific:

debian-svp lintian-brush https://salsa.debian.org/python-team/packages/dulwich

2. same quest, shorter route — just the package name, bestie:

debian-svp lintian-brush dulwich

3. create a new merge proposal merging the latest upstream version of dulwich into the packaging branch 🦋:

debian-svp new-upstream dulwich

---

👀 SEE ALSO 👀

svp(1), git(1), brz(1), lintian-brush(1)

(go read them, iykyk 📚)

---

📜 LICENSE 📜

GNU General Public License, version 2 or later. ⭐

---

👑 AUTHORS 👑

Jelmer Vernooij <jelmer@jelmer.uk> 💜

---

ok that's the whole page, you ate that 💅

debian-svp 0.0.1 🌸 February 2019 — mwah, love u, go fix some packaging bugs 🎀✨