Differences between revisions 30 and 31
Revision 30 as of 2019-08-13 20:14:48
Size: 1920
Editor: nodiscc
Comment: add CategoryPackageManagement
Revision 31 as of 2019-09-03 14:25:48
Size: 2108
Editor: ?JasonQuinn
Comment: we must mention backing up data here... I think I've only ever had ONE release upgrade out of about 5 go off without a hitch
Deletions are marked like this. Additions are marked like this.
Line 12: Line 12:

Performing a release upgrade is not without risk. The upgrade may fail, leaving the system in a non-functioning state. USERS SHOULD BACKUP ALL DATA before attempting a release upgrade.

Translation(s): Brasileiro - English - Español - Français - Italiano- Русский - Svenska

(!) ?Discussion


This page gives directions on how to upgrade your Debian distribution.

How to release upgrade your distribution

Upgrading from one stable release to the next (e.g. bullseye to bookworm) is done by following the release notes for your architecture. For most people with 32 bit systems that means the Release Notes for Intel x86. For most with 64 bit systems that means the Release Notes for AMD64.

Performing a release upgrade is not without risk. The upgrade may fail, leaving the system in a non-functioning state. USERS SHOULD BACKUP ALL DATA before attempting a release upgrade.

Upgrades are done with the package management tool apt-get or apt, and generally involve the following steps.

  • Switch to tty via Ctrl+Alt+F3. Otherwise, your desktop environment can freeze up during post-install and service restart period, leaving the system in a broken state.
  • Execute the following

$ sudo apt clean
$ sudo apt update
$ sudo apt upgrade       # For regular/minor upgrades
$ sudo apt dist-upgrade  # For major release upgrades only
$ sudo apt autoremove
$ /sbin/shutdown -r now  # Reboot to make changes effective (optional)

Now check the output of  uname -a  and you should see info about the upgraded system.


CategoryPackageManagement