MINI-BUI...BUG-BUILD(8)

💅 MINI-BUI...BUG-BUILD(8)

okay so bestie, welcome to mini-buildd-debug-build — she lives in the System Administration Utilities corner of your mini-buildd install and she's here for exactly one thing: letting you manually crawl into an sbuild environment for a given buildrequest changes file so you can debug those failed builds yourself. no cap. 🫶

---

✨ NAME ✨

mini-buildd-debug-build — enter the sbuild environment for a given buildrequest changes file (i.e. manually debug failed builds). it's giving "let me in, I can fix her." 😭

---

🌸 DESCRIPTION 🌸

So like, the usage line is literally this, verbatim, don't come for me:

usage: mini-buildd-debug-build [-h] [--version] [-l LOG_LEVEL]
                               [-U DEDICATED_USER]
                               [-s {chroot-setup,chroot-update-failed,build-deps-failed,starting-build,build-failed,finished-build,chroot-cleanup}]
                               [-u USER] [-p EXTRA_PACKAGE]
                               BUILDREQUEST

And what does she do? She enters the sbuild environment for the given buildrequest changes file, so you can manually debug failed builds. that's the whole vibe. iconic behaviour honestly. 💖

---

🎀 positional arguments

• BUILDREQUEST — the path to your buildrequest changes file. the main character of this whole operation, fr fr. 👑

---

✨ options

• -h, --help — shows this help message and then dips. exit stage left. 💅
• --version — shows the program's version number and exits. quick lil flex. ⭐
• -l, --log-level LOG_LEVEL — sets the log level. if you don't give one, ['WARNING', 'mini_buildd.INFO'] gets applied by default. You can also write it as `<logger>.<level>` to only affect individual loggers, and you can pass it multiple times — go check your existing logs for the actual logger names, bestie, they're in there. (default: None) 🔥
• -U, --dedicated-user DEDICATED_USER — forces a custom dedicated user name, so you can run as a different user than 'mini-buildd'. (default: mini-buildd) 🦋
• -s, --sbuild-hook {chroot-setup,chroot-update-failed,build-deps-failed,starting-build,build-failed,finished-build,chroot-cleanup} — which sbuild hook to drop to the shell at. like, man sbuild if you wanna know more about hooks, I'm not your dad. (default: starting-build) 🌈
• -u, --user USER — the user to use for the post-build shell. (default: mini-buildd) 🍓
• -p, --extra-package EXTRA_PACKAGE — an extra package to install. you can pass this multiple times, go wild, collect them all. (default: []) 💜

---

⚠️ lowkey important: this is a debug tool, so you're literally dropping into a shell inside the build environment. that's the point. that's the assignment. don't be weird about it. 🧚

---

🌟 SEE ALSO

okay there's genuinely nothing else listed here, bestie — she stands on her own. main character energy only. 👑

---

and that's the whole page!! brought to you by mini-buildd-debug-build version 2.4.8..., dated February 2026, hanging out in the MINI-BUI...BUG-BUILD(8) section of your friendly neighbourhood System Administration Utilities. stay slay, debug responsibly, and remember: the build failed but you didn't. 💖✨🎀