Differences between revisions 36 and 38 (spanning 2 versions)
Revision 36 as of 2021-03-09 20:58:47
Size: 2560
Editor: ThiagoPezzo
Comment: fix pt_BR in translation header
Revision 38 as of 2021-03-30 01:51:41
Size: 3470
Editor: ?CalumMcConnell
Comment: Really drive home that bit about backups, and add some more details.
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
Upgrading from one stable release to the next (e.g. <<DebianCodename(oldstable)>> to <<DebianCodename(stable)>>) is done by following the [[http://www.debian.org/releases/stable/releasenotes|release notes]] for your [[http://www.debian.org/ports/|architecture]]. For most people with 32 bit systems that means the [[http://www.debian.org/releases/stable/i386/release-notes/|Release Notes for Intel x86]]. For most with 64 bit systems that means the [[http://www.debian.org/releases/stable/amd64/release-notes/|Release Notes for AMD64]]. Upgrading from one stable release to the next (e.g. <<DebianCodename(oldstable)>> to <<DebianCodename(stable)>>) is done by following the [[http://www.debian.org/releases/stable/releasenotes|release notes]] for your [[http://www.debian.org/ports/|architecture]]. For most users, that means the [[http://www.debian.org/releases/stable/amd64/release-notes/|Release Notes for AMD64]].
Line 13: Line 13:
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. {{{#!wiki caution
'''Back up your data'''

Performing a release upgrade is never without risk. The upgrade may fail, leaving the system in a non-functioning state. USERS SHOULD BACKUP ALL DATA before attempting a release upgrade. DebianStability contains more information on these steps.
}}}

Upgrading a system can take several hours, depending on the number of installed packages and the speed of the system, especially its hard disks. While the download portion of the upgrade can be done separately, the actual install portion should be done in a single pass. Most of the upgrade process is quite hands-off, but some administrator action is needed towards the end of the process if the system has a custom configuration.
Line 19: Line 25:
 * Run the following:  * Run the following, by entering lines beginning with $ into the shell:
Line 22: Line 28:
# in a text editor, replace the codename of your release with the next release (eg. buster with bullseye) in APT sources # First, ensure your system is up-to-date in it's current release.
$ sudo apt update
$ sudo apt upgrade

# If you haven't already, ensure all backups are up-to-date.

# In a text editor, replace the codename of your release with that of the next release in APT's package sources
# For instance, the line
# deb https://deb.debian.org/debian/ buster main
# should be replaced with
# deb https://deb.debian.org/debian/ bullseye main
Line 25: Line 41:
# clean and update package lists # Clean and update package lists
Line 29: Line 45:
# perform regular/minor upgrades
$ sudo apt upgrade
# perform major release upgrade, removing packages if necessary
# Perform the major release upgrade, removing packages if required
# Interrupting this step after downloading has completed is an excellent way to stress-test your backups
Line 34: Line 49:
# remove packages that are not required anymore # Remove packages that are not required anymore
# Be sure to review this list: you may want to keep some of them
Line 37: Line 53:
# reboot to make changes effective (optional)
$ /sbin/shutdown -r now
# Reboot to make changes effective (optional, but recommended)
$ sudo shutdown -r now

Translation(s): English - Español - Français - Italiano - Português (Brasil) - Русский - 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 users, that means the Release Notes for AMD64.

Back up your data

Performing a release upgrade is never without risk. The upgrade may fail, leaving the system in a non-functioning state. USERS SHOULD BACKUP ALL DATA before attempting a release upgrade. DebianStability contains more information on these steps.

Upgrading a system can take several hours, depending on the number of installed packages and the speed of the system, especially its hard disks. While the download portion of the upgrade can be done separately, the actual install portion should be done in a single pass. Most of the upgrade process is quite hands-off, but some administrator action is needed towards the end of the process if the system has a custom configuration.

Upgrades are done with package management tools, root or sudo access, and generally involve the following steps.

  • Obtain a text shell.
    • On desktop machines, switch to console tty via Ctrl+Alt+F3 (the upgrade should be done on a text console, because your desktop environment could freeze during post-install/service restarts, leaving the system in a broken state.)
  • Run the following, by entering lines beginning with $ into the shell:

# First, ensure your system is up-to-date in it's current release.
$ sudo apt update
$ sudo apt upgrade

# If you haven't already, ensure all backups are up-to-date.  

# In a text editor, replace the codename of your release with that of the next release in APT's package sources
# For instance, the line
#    deb https://deb.debian.org/debian/ buster main
# should be replaced with
#    deb https://deb.debian.org/debian/ bullseye main
$ sudo nano /etc/apt/sources.list /etc/apt/sources.list.d/*

# Clean and update package lists
$ sudo apt clean
$ sudo apt update

# Perform the major release upgrade, removing packages if required
# Interrupting this step after downloading has completed is an excellent way to stress-test your backups
$ sudo apt full-upgrade

# Remove packages that are not required anymore
# Be sure to review this list: you may want to keep some of them
$ sudo apt autoremove

# Reboot to make changes effective (optional, but recommended)
$ sudo shutdown -r now

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


CategoryPackageManagement