Documentation

Upgrading KUHBS Itself

Review a newer KUHBS source checkout, rerun the direct dom0 installer, and verify the installed configuration before managing VMs again.

KUHBS does not currently have a built-in self-upgrade command. Upgrade it from a newer source checkout only after reviewing the exact code and installer changes you intend to trust.

Before upgrading KUHBS

  1. back up the application data you need;
  2. record the currently installed KUHBS version or commit;
  3. obtain the newer kuhbs-for-qubes checkout in dom0;
  4. review the complete change from the installed version to the new commit; and
  5. review install/install.sh again because it makes system-wide dom0 changes.

Do not replace the reviewed checkout with an unreviewed branch tip immediately before installation.

Run the reviewed installer

From the newer reviewed checkout in dom0:

cd /home/user/kuhbs-for-qubes
bash install/install.sh

The installer updates KUHBS-owned Python code, schemas, defaults, icons, GUI, CLI, shell completion, and desktop settings. It can replace KUHBS-owned Gedit and XFCE Terminal settings and apply the other system-wide choices described in Installing KUHBS .

After installation, run kuhbs check, reopen the graphical interface, and verify the expected repositories and enabled KUHBs before performing another lifecycle action.

Upgrading KUHBS itself does not update external repositories or apply upgrades to existing managed VMs. Review and perform those changes separately.

Next: Running AI Audits Before Adding External Repositories .