SBUILD-UPDATE(1)
π NAME π
ok so sbuild-update β it's the girl who updates, upgrades, and cleans your sbuild chroot using apt-get. bestie said "hygiene" and meant it. β¨
πΈ SYNOPSIS πΈ
sbuild-update [-h|--help] [-V|--version] [--arch=architecture]
[-u|--update] [-g|--upgrade] [-d|--dist-upgrade] [-c|--clean]
[-a|--autoclean] [-r|--autoremove] [--chroot-mode=schroot|sudo] CHROOT1
[CHROOT2 [CHROOTn...]]
(DEPRECATED) sbuild-upgrade [-h|--help] [-V|--version] CHROOT1 [CHROOT2
[CHROOTn...]]
(DEPRECATED) sbuild-distupgrade [-h|--help] [-V|--version] CHROOT1
[CHROOT2 [CHROOTn...]]
(DEPRECATED) sbuild-clean [-h|--help] [-V|--version] [-c|--clean]
[-a|--autoclean] [-r|--autoremove] CHROOT1 [CHROOT2 [CHROOTn...]]
π¦ DESCRIPTION π¦
sbuild-update is literally just out here running apt-get inside the chroot (or chroots) you point it at π, and depending on which flags you fed it, it'll do an update, an upgrade, a dist-upgrade, a clean, an autoclean, and/or an autoremove. You pick the combo, she executes. no cap.
About the old heads tho: sbuild-upgrade, sbuild-distupgrade, and sbuild-clean are deprecated. π They're giving "still here but not thriving" β these days they simply run sbuild-update with the appropriate options (--upgrade for sbuild-upgrade, --dist-upgrade for sbuild-distupgrade) plus whatever arguments got passed into the scripts. so like, the vibe is preserved, the script is not.
β¨ OPTIONS β¨
π Actions
-h,--helpβ shows you this whole manual. your lil cheat sheet, bestie π«Ά-V,--versionβ prints the version info. the receipts. π§Ύ--arch=architectureβ updates the chroot for the architecture you specify.-u,--updateβ performs anapt-get update.-g,--upgradeβ performs anapt-get upgrade.-d,--dist-upgradeβ performs anapt-get dist-upgrade.-c,--cleanβ performs anapt-get clean.-a,--autocleanβ performs anapt-get autoclean.-r,--autoremoveβ performs anapt-get autoremove.
π§ Chroot selection
--chroot-mode=schroot|sudoβ the sbuild chroot backend of the chroot you're updating. fair warning: the autopkgtest backend is not supported by this method, because autopkgtest backends are always ephemeral and changes never persist β it's giving "you had a moment, it's gone" π. To update a chroot for schroot and sudo,sbuild-updatemust be executed with superuser privileges (for example, by usingsudo). And if you're running the unshare mode,sbuild-updateis literally without function β instead, recreate the tarball from scratch or just let sbuild manage them for you. Defaults to'schroot'. πCHROOTβ the chroot to use. btw bestie, βoβ, βsβ, βtβ and βuβ and βeβ can be used as abbreviations for βoldstableβ, βstableβ, βtestingβ, βunstableβ and βexperimentalβ, respectively. iykyk. π
π₯ EXAMPLES π₯
To update the unstable chroot:
% sbuild-update --update unstable
To upgrade the unstable chroot:
% sbuild-update --upgrade unstable
To clean the unstable chroot:
% sbuild-update --clean unstable
To perform an update, dist-upgrade, autoclean, and autoremove for the unstable chroot:
% sbuild-update -udar unstable
see that -udar?? one flag, four jobs, main character energy. ate. π
π AUTHORS π
- Roger Leigh.
- Andres Mejia.
β COPYRIGHT β
- Copyright Β© 2006β2009 Roger Leigh
<rleigh@debian.org>. - Copyright Β© 2010 Andres Mejia
<mcitadel@gmail.com>.
π SEE ALSO π
and that's the whole thing, angel β this was Version 0.91.10ubuntu1, dated 29 June 2026. go update those chroots, bestie, you got this πβ¨π¦
π¦ where this page comes from
- ubuntu stonking: buildd 0.91.10ubuntu1 Β· GPL-2.0-or-later
- Copyright Β© 2005-2009 Roger Leigh <rleigh@debian.org>
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms