This wiki was updated to MediaWiki 1.37. If you notice any issues, please report them to admin[at]

SDB:Upgrade Tumbleweed

Jump to: navigation, search


You want to upgrade Tumbleweed to the latest snapshot.


It's recommended that you become familiar with using snapper to rollback.

It's generally safer to logout of your desktop environment (DE) and upgrade from a virtual terminal: This avoids anything related to the DE freezing or dying in the middle of the upgrade. However, you can safely download all the changed packages from within the DE without installing. This can be done from a DE terminal with:

 su - -c 'zypper dup -d'

This can be more convenient if you need to ask about conflicts on the forum.

Either way, the following will complete the upgrade:

  1. Log out of your desktop environment and press Ctrl+Alt+F1 at the login manager.
  2. Log in as root.
  3. Enter the command:
# zypper dup
  1. Deal with any conflicts and then agree to the upgrade.
  2. When the upgrade is complete, enter the command:
# reboot

A reboot isn't always required: Zypper will tell you when it is. To return to the DE enter the exit command, and press CTRL+ALT+F7.

Theoretically, the safest way to upgrade when a reboot isn't required is to isolate the, because the fewest things are loaded in this state, which means that most things will be reloaded when switching back to the DE. The idea is to avoid having outdated processes running that the upgraded packages might try to interact with. You can isolate the with one of the following commands:

 # systemctl isolate


 # telinit 1


The following (truncated) information is from SDB:Zypper_manual. See the zypper repository for the list of authors.

dist−upgrade (dup) [options]

Perform a distribution upgrade. This command applies the state of (specified) repositories onto the system; upgrades (or even downgrades) installed packages to versions found in repositories, removes packages that are no longer in the repositories and pose a dependency problem for the upgrade, handles package splits and renames, etc.

If no repositories are specified via the −−from option, zypper will do a global upgrade with all defined repositories. This global form of dup will also consider unchanged installed packages and re−evaluate their dependencies.

−−from alias|name|#|URI

The option can be used multiple times and restricts the upgrade to the specified repositories only. Nevertheless all enabled repositories are visible to the resolver and will be considered to satisfy dependency problems.

−l, −−auto−agree−with−licenses

Automatically say yes to third party license confirmation prompt. By using this option, you choose to agree with licenses of all third−party software this command will install. This option is particularly useful for administrators installing the same set of packages on multiple machines (by an automated process) and have the licenses confirmed before.


Automatically accept product licenses only. This is used by tools like SUSEconnect, which ask for confirmation before the product gets registered. So there’s no need to confirm the product license again at install time.


Install the packages even if they replace files from other, already installed, packages. Default is to treat file conflicts as an error. −−download−as−needed disables the fileconflict check because access to all packages filelists is needed in advance in order to perform the check.

−D, −−dry−run

Test the upgrade, do not actually install or update any package. This option will add the −−test option to the rpm commands run by the dist−upgrade command.

−y, −−no−confirm

Don’t require user interaction. Alias for the −−non−interactive global option.


Show the detailed installation summary.

Solver related options:


Create solver test case for debugging. Use this option, if you think the dependencies were not solved all right and attach the resulting /var/log/zypper.solverTestCase directory to your bug report. To use this option, simply add it to the problematic install or remove command.


Force the solver to find a solution by allowing to remove packages with unfulfilled requirements. This is the default when removing packages (zypper remove). This option overrides −−no−force−resolution in case both are specified on the command line.

−R, −−no−force−resolution

Do not force the solver to find a solution. Instead, report dependency problems and prompt the user to resolve them manually. This is the default except when removing packages (zypper remove).


Install also recommended packages in addition to the required ones. The default behavior is determined by [zypp.conf:solver.onlyRequires].


Do not install recommended packages, but only required ones. The default behavior is determined by [zypp.conf:solver.onlyRequires].

Expert Options:

Don’t use them unless you know you need them.


Whether to allow downgrading installed resolvables [zypp.conf:solver.dupAllowDowngrade].


Whether to allow changing the names of installed resolvables [zypp.conf:solver.dupAllowNameChange]. Setting this to no will not replace packages which have been renamed.


Whether to allow changing the architecture of installed resolvables [zypp.conf:solver.dupAllowArchChange].


Whether to allow changing the vendor of installed resolvables [zypp.conf:solver.dupAllowVendorChange]. Setting this to no might be useful if you do not want packages from foreign repos being dup’ed to the distributions version (or vice versa).

This command also accepts the Download−and−install mode options described in the install command description.


$ zypper dup −−from factory −−from packman

Upgrade the system to the latest versions provided by the factory and packman repositories.