Release Upgrade Whonix 17 to Whonix 18

From Whonix
Jump to navigation Jump to search

How to Release Upgrade from Whonix 17 to Whonix 18

Notices

[edit]

Developers only! Warning: This is for developers-only!

Once available it will be announced in the usual places. See Stay Tuned.

Release Upgrade Whonix Notices
Notice Description
Difficulty
Release Upgrade vs Re-Installation

To use Whonix 18, users can either:

Standard Updates
Automated Release Upgrade vs Manual Release Upgrade
  • Automated Release Upgrade is the newer method that has been implemented. It does not ask for user input and is therefore easier to use.
  • The former Manual Release Upgrade effectively did the same, but it offered more control over system customization. It is now deprecated. [1]
Configuration Files Resets Since this is an automated release upgrade, user modified configuration files (if any) in folder /etc will be reset, overwritten with the Debian or Whonix package version. The user is free to restore the configuration after the release upgrade.

High Level Overview

[edit]
  1. Backup all data - ideally have a copy of the VM(s) so it is possible to try again (if necessary).
  2. Perform the usual standard ("everyday") update instructions.
  3. Release Upgrade Whonix-Workstation (whonix-workstation-17).
  4. Power off Whonix-Workstation (whonix-workstation-17).
  5. Release Upgrade Whonix-Gateway (whonix-gateway-17).
  6. Restart Whonix-Gateway (whonix-gateway-17).
  7. Restart Whonix-Workstation (whonix-ws-workstation).

Platform Specific Notices

[edit]

Release Upgrade

[edit]
  1. Backup all data, ideally have a clone of the VM(s) so it is possible to try again (if necessary).
  2. Perform the usual standard ("everyday") update instructions.
  3. Consider running the optional sanity tests.
  4. Run Kicksecure logo systemcheckOnion network Logo.
  5. View release-upgrade command version: cat /usr/sbin/release-upgrade | grep version=
  6. Check release-upgrade command version. It should be a minimum of 3.3, and display version="3.3".
  7. Consider keeping the full release upgrade log output. It will be required for Support in case there are issues.
  8. Perform the automated release upgrade using the release-upgrade command: sudo release-upgrade
  9. Re-run the repository-dist utility to update your derivative APT sources list from the old .list to the new .sources format. [3] This is a very minor issue if forgotten. It can be done at any later time. systemcheck will point this out if it has not been done yet.
  10. Done. If everything went well, at the end it will show:

    INFO: OK. (release-upgrade version: 3.3) Release upgrade success.

  11. Reboot.
  12. Optional, recommended: Re-install Meta Packages and Safely Run Autoremove

Support the Future of Whonix

[edit]

Whonix is made possible thanks to the donation of people like you.

Please support the Whonix development with a donation.

Donate to Whonix

Footnotes

[edit]
  1. This method is still possible. All the automated release-upgradeGitHub Logo script does is perform actions which the user could perform manually. If a manual release upgrade is desired, emulate what the release-upgrade script is doing. The manual release upgrading procedure is undocumented due to the size of the instructions and duplication involved.
  2. sudo release-upgrade --force might work for Qubes R4.2, but this is unsupported.
  3. https://forums.kicksecure.com/t/apt-sources-list-one-line-format-versus-deb822-style-format/267archive.org iconarchive.today icon
Notification image

We believe security software like Whonix needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 13 year success story and maybe DONATE!