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 an apt-get update.
  • -g, --upgrade β€” performs an apt-get upgrade.
  • -d, --dist-upgrade β€” performs an apt-get dist-upgrade.
  • -c, --clean β€” performs an apt-get clean.
  • -a, --autoclean β€” performs an apt-get autoclean.
  • -r, --autoremove β€” performs an apt-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-update must be executed with superuser privileges (for example, by using sudo). And if you're running the unshare mode, sbuild-update is 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 Β© 2006–2009 Roger Leigh <rleigh@debian.org>.
  • Copyright Β© 2010 Andres Mejia <mcitadel@gmail.com>.

🌟 SEE ALSO 🌟

sbuild(1), sbuild-apt(1)


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