Selecting the patch, the conflict is resolved by updating all installed and affected/vulnerable packages to a version providing the fix. When updating the packages zypper always aims for the latest available version. Resolved patches are classified as either applied or not needed, depending on whether they refer to actually installed packages.

So installation, update or removal of packages may change the classification of patches referring to these packages. Since libyzpp-17.23.0 the /var/log/zypp/history remembers if a committed transaction changes a patchs classification. If history data are available, patch tables show a column telling since when the patch is in it’s current state.

Depending on the kind of defect, patches are classified by category and severity. Commonly used values for category are security, recommended, optional, feature, document or yast. Commonly used values for severity are critical, important, moderate, low or unspecified.

Note that the patch command does not apply optional patches (category optional or feature) by default. If you actually want to consider all optional patches as being needed, say patch --with-optional. Specific patches can be applied using the install command (e.g. zypper install patch:openSUSE-2014-7).

If the issuer decides to retract a released patch, the patch status will be shown as retracted. The packages provided by the retracted patch are still visible but also tagged as having been retracted (R). The resolver will avoid selecting retracted packages automatically. If you are sure that a retracted package should be installed on your system, you must explicitly select it.

If invoked with a command name argument, zypper displays help for the specified command, if such command exists. Long as well as short variants of the command names can be used.

For your convenience, zypper help can also be invoked in any of the following ways:

The shell support is not complete so expect bugs there. However, there’s no urgent need to use the shell since libzypp became so fast thanks to the SAT solver and its tools (openSUSE 11.0), but still, you’re welcome to experiment with it.

For each specified package, zypper finds the best available version in defined repositories and shows information for this package.

-r, --repo alias|name|#|URI

-t, --type type

--provides

--requires

--conflicts

--obsoletes

--recommends

--suggests

--supplements

Examples:

The packages can be selected by their name or by a capability they provide.

A capability is formed by "NAME[.ARCH][ OP EDITION]", where ARCH is an architecture code, OP is one of <, <=, =, >=, or > and EDITION is "VERSION[-RELEASE]". For example: zypper=0.8.8-2.

Zypper is also able to install plain RPM files while trying to satisfy their dependencies using packages from defined repositories. You can install a plain RPM file by specifying its location in the install command arguments either as a local path or an URI. E.g.:

In the install command, you can also specify packages you wish to remove by prepending their names by a - or ! character. For example:

-r, --repo alias|name|#|URI

-t, --type type

-n, --name

-f, --force

--oldpackage

--from alias|name|#|URI

-C, --capability

-l, --auto-agree-with-licenses

--auto-agree-with-product-licenses

--replacefiles

-D, --dry-run

--details

-y, --no-confirm

--allow-unsigned-rpm

Solver related options:

--debug-solver

--force-resolution

-R, --no-force-resolution

--solver-focus MODE

--recommends

--no-recommends

Download-and-install mode options:

-d, --download-only

--download-in-advance

--download-in-heaps

--download-as-needed

--download mode

Expert Options:

--allow-downgrade, --no-allow-downgrade

--allow-name-change, --no-allow-name-change

--allow-arch-change, --no-allow-arch-change

--allow-vendor-change, --no-allow-vendor-change

Examples:

This command will try to find the newest available versions of the source packages and uses rpm -i to install them, optionally together with all the packages that are required to build the source package. The default location where rpm installs source packages to is /usr/src/packages/{SPECS,SOURCES}, but the values can be changed in your local rpm configuration. In case of doubt try executing rpm --eval "%{_specdir} and %{_sourcedir}".

Note that the source packages must be available in repositories you are using. You can check whether a repository contains any source packages using the following command:

-d, --build-deps-only

-D, --no-build-deps

-r, --repo alias|name|#|URI

--download-only

Examples:

In case that any dependency problems are found, zypper suggests packages to install or remove to fix them.

-D, --dry-run

--details

-r, --repo alias|name|#|URI

-y, --no-confirm

Solver related options:

--debug-solver

--force-resolution

-R, --no-force-resolution

--solver-focus MODE

--recommends

--no-recommends

Expert Options:

--allow-downgrade, --no-allow-downgrade

--allow-name-change, --no-allow-name-change

--allow-arch-change, --no-allow-arch-change

--allow-vendor-change, --no-allow-vendor-change

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

Called as zypper inr --no-recommends, it restricts the command to just look for packages supporting available hardware, languages or filesystems. Useful after having added e.g. new hardware or driver repos. This is also the default behavior if you have set [zypp.conf:solver.onlyRequires].

-r, --repo alias|name|#|URI

-D, --dry-run

--details

Solver related options:

--debug-solver

--force-resolution

-R, --no-force-resolution

--solver-focus MODE

--recommends

--no-recommends

Expert Options:

--allow-downgrade, --no-allow-downgrade

--allow-name-change, --no-allow-name-change

--allow-arch-change, --no-allow-arch-change

--allow-vendor-change, --no-allow-vendor-change

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

The remove command will uninstall the selected and their dependent packages. It will not try to install alternatives in order to keep dependent packages installed. If you want this, use zypper install !name.

The packages can be selected by their name or by a capability they provide. For details on package selection see the install command description.

-r, --repo alias|name|#|URI

-t, --type type

-n, --name

-C, --capability

-D, --dry-run

--details

-y, --no-confirm

Solver related options:

--debug-solver

--force-resolution

-R, --no-force-resolution

--solver-focus MODE

-u, --clean-deps

-U, --no-clean-deps

Automatically cleans up installed kernels according to the rules defined in [zypp.conf:multiversion.kernels] which can be given as <version>, latest[-N], running, oldest[+N].

--details

-D, --dry-run

This command will list only installable updates, i.e. updates which have no dependency problems, or which do not change package vendor. This list is what the update command will propose to install. To list all packages for which newer version are available, use --all option.

-t, --type type

-r, --repo alias|name|#|URI

-a, --all

--best-effort

Expert Options:

--allow-downgrade, --no-allow-downgrade

--allow-name-change, --no-allow-name-change

--allow-arch-change, --no-allow-arch-change

--allow-vendor-change, --no-allow-vendor-change

This command will not update packages which would require change of package vendor unless the vendor is specified in /etc/zypp/vendors.d, or which would require manual resolution of problems with dependencies. Such non-installable updates will then be listed in separate section of the summary as "The following package updates will NOT be installed:".

To update individual packages, specify one or more package names. You can use the * and ? wildcard characters in the package names to specify multiple packages matching the pattern.

-t, --type type

-r, --repo alias|name|#|URI

--skip-interactive

--with-interactive

-l, --auto-agree-with-licenses

--auto-agree-with-product-licenses

--replacefiles

-D, --dry-run

--details

--best-effort

-y, --no-confirm

Solver related options:

--debug-solver

--force-resolution

-R, --no-force-resolution

--solver-focus MODE

--recommends

--no-recommends

Expert Options:

--allow-downgrade, --no-allow-downgrade

--allow-name-change, --no-allow-name-change

--allow-arch-change, --no-allow-arch-change

--allow-vendor-change, --no-allow-vendor-change

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

This command is similar to zypper list-updates -t patch.

Note that optional arguments of some of the following options must be specified using = instead of a space.

-b, --bugzilla[=#[,...]]

--cve[=#[,...]]

--date YYYY-MM-DD[,...]

-g, --category category[,...]

--severity severity[,...]

--issue[=string[,...]]

-a, *--all

--with-optional, --without-optional

-r, --repo alias|name|#|URI

See also the EXIT CODES section for details on exit status of 0, 100, and 101 returned by this command.

--updatestack-only

--with-optional, --without-optional

-r, --repo alias|name|#|URI

If there are patches that affect the package management itself, those will be installed first and you will be asked to run the patch command again.

This command is similar to zypper update -t patch.

--updatestack-only

--with-update

--with-optional, --without-optional

-b, --bugzilla #[,...]

--cve #[,...]

--date YYYY-MM-DD[,...]

-g, --category category[,...]

--severity severity[,...]

-r, --repo alias|name|#|URI

--skip-interactive

--with-interactive

-l, --auto-agree-with-licenses

--auto-agree-with-product-licenses

--replacefiles

-D, --dry-run

--details

-y, --no-confirm

Solver related options:

--debug-solver

--force-resolution

-R, --no-force-resolution

--solver-focus MODE

--recommends

--no-recommends

Expert Options:

--allow-downgrade, --no-allow-downgrade

--allow-name-change, --no-allow-name-change

--allow-arch-change, --no-allow-arch-change

--allow-vendor-change, --no-allow-vendor-change

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

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. This can be a problem if the system contains conflicting repositories, like repositories for two different distribution releases. This often happens if one forgets to remove an older release repository after adding a new one, say openSUSE 13.1 and openSUSE 13.2.

For all repositories which have the distribution version within their URL (like https://download.opensuse.org/distribution/13.1/repo/oss) using the $releasever variable instead may be helpful (https://download.opensuse.org/distribution/$releasever/repo/oss). The variable is per default substituted by the current distributions version (13.1).

This value can be temporarily overwritten in the current zypper command by using the --releasever global option. Calling zypper --releasever 13.2... will cause these repos to use the new location (https://download.opensuse.org/distribution/13.2/repo/oss) without the need to add/remove anything. But you’ll need to use --releasever 13.2 with every zypper command until the distribution upgrade was actually performed. Once the dup is done, $releasever will default to the new distribution version 13.2 and --releasever is no longer needed.

It might be less tedious to persistently set $releasever to the target distribution value, so --releasever is not needed at all. See section Repository Management for more info about variable substitution and the definition of custom variables.

Note: Performing a distribution upgrade will automatically create a solver test case at /var/log/updateTestcase-YYYY-MM-DD-hh-mm-ss (the date and time the command was executed).

Note: distribution upgrades in openSUSE are currently only supported between consecutive releases. To upgrade multiple releases, upgrade each consecutive release one at a time. For more details see <http://en.opensuse.org/SDB:System_upgrade> and the openSUSE release notes at <http://doc.opensuse.org/release-notes/>.

--from alias|name|#|URI

-r, --repo alias|name|#|URI

-l, --auto-agree-with-licenses

--auto-agree-with-product-licenses

--replacefiles

-D, --dry-run

-y, --no-confirm

--details

Solver related options:

--debug-solver

--force-resolution

-R, --no-force-resolution

--solver-focus MODE

--recommends

--no-recommends

Expert Options:

--allow-downgrade, --no-allow-downgrade

--allow-name-change, --no-allow-name-change

--allow-arch-change, --no-allow-arch-change

--allow-vendor-change, --no-allow-vendor-change

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

Examples:

Results of the search are printed in a table with columns Status, Name, Summary and Type of package.

In the detailed view (se -s) all available instances of matching packages are shown; each version in each repository on a separate line, with columns Status, Name, Type, Version, Architecture and Repository. For installed packages Repository shows either a repository that provides exactly the installed version of the package, or, if the exact version is not provided by any known repo, (System Packages) (or @System). Those installed packages not provided by any repo are often denoted as being unwanted, orphaned or dropped.

The Status column can contain the following values:

This command accepts the following options:

--match-substrings

--match-words

-x, --match-exact

--provides

--requires

--recommends

--suggests

--conflicts

--obsoletes

--supplements

--provides-pkg

--requires-pkg

--recommends-pkg

--supplements-pkg

--conflicts-pkg

--obsoletes-pkg

--suggests-pkg

-n, --name

-f, --file-list

-d, --search-descriptions

-C, --case-sensitive

-i, --installed-only

-u, --not-installed-only

-t, --type type

-r, --repo alias|name|#|URI

--sort-by-name

--sort-by-repo

-s, --details

-v, --verbose

Examples:

-r, --repo alias|name|#|URI

-i, --installed-only

-u, --not-installed-only

--orphaned

--suggested

--recommended

--unneeded

-r, --repo alias|name_|#|URI

-r, --repo alias|name|#|URI

-i, --installed-only

-u, --not-installed-only

-r, --repo alias|name|#|URI

-i, --installed-only

-u, --not-installed-only

--xmlfwd tag

Examples:

The command line is automatically transformed into the corresponding search command:

This is useful for related repositories like packman (http://ftp.gwdg.de/pub/linux/packman/suse/$releasever), which shall always fit the installed distribution, even after a distribution upgrade.

To help performing a distribution upgrade, the value of $releasever can be persistently set to a user defined value by creating a custom variable with that name (see below). This way you can easily switch all repositories using $releasever to the new version (provided the server layouts did not change and new repos are already available).

For a single zypper command the value of $releasever can be temporarily overwritten by using the --releasever global option.

In addition $releasever_major will be set to the leading portion up to (but not including) the 1st dot; $releasever_minor to the trailing portion after the 1st dot. If there’s no dot in $releasever, $releasever_major is the same as $releasever and $releasever_minor is empty.

Explicit proxy settings may be passed via optional parameters proxy, proxyport, proxyuser and proxypass.

HTTP authentication methods to use can be defined as comma separated list via optional parameter auth. Valid methods are e.g. basic, digest, ntlm, negotiate. Note, that this list depends on the list of methods supported by the curl library.

SSL verification behavior can be changed using the ssl_verify option (this should be used with care). Valid values are yes (the secure default), host, peer or no. Host just checks that the "Common Name" field or a "Subject Alternate Name" field in the servers certificate matches the host name in the URL. Peer just verifies whether the certificate provided by the server is authentic against the chain of digital signatures found in ssl_capath. No performs no checks at all. Yes is the secure default, performing host and peer check.

For SSL client certificate authentication use the options ssl_clientcert to define the path to the ssl client certificate and ssl_clientkey to define the path to the SSL client key. Use ssl_capath to change the directory holding the CA certificates (default is /etc/ssl/certs).

Optional workgroup or domain parameter set the name of the workgroup. As alternative to passing username:password in the URI authority the parameters user and pass can be used.

If platform is omitted, openSUSE_$releasever is used unless a value for obs.platform is defined in zypper.conf. If you are following openSUSE_Factory or openSUSE_Tumbleweed you may need to set these as your default platform. But we can only guess, how the directory containing the repository that fits your distribution is named on the server. In case of doubt you need to look up the right URL in a browser.

Newly added repositories have auto-refresh disabled by default (except for repositories imported from a .repo, having the auto-refresh enabled). To enable auto-refresh use addrepo -f, or the --refresh option of the modifyrepo command.

Also, this command does not automatically refresh the newly added repositories. The repositories will get refreshed when used for the first time, or you can use the refresh command after finishing your modifications with *repo commands.

-r, --repo file.repo

-c, --check

-C, --no-check

-n, --name name

-e, --enable

-d, --disable

-f, --refresh

-F, --no-refresh

-p, --priority positive-integer

-k, --keep-packages

-K, --no-keep-packages

-g, --gpgcheck

--gpgcheck-strict

--gpgcheck-allow-unsigned

--gpgcheck-allow-unsigned-repo

--gpgcheck-allow-unsigned-package

-G, --no-gpgcheck

--default-gpgcheck

Examples:

--loose-auth

--loose-query

-a, --all

-l, --local

-t, --remote

-m, --medium-type type

The following data can be printed for each repository found on the system: # (repository number), Alias (unique identifier), Name, Enabled (whether the repository is enabled), GPG Check (whether GPG check for repository metadata (r) and/or downloaded rpm packages (p) is enabled), Refresh (whether auto-refresh is enabled for the repository), Priority, Type (repository meta-data type: rpm-md, yast2, plaindir). Which of the data is shown is determined by command line options listed below and the main.repoListColumns setting from zypper.conf. By default, #, Alias, Name, Enabled, GPG Check and Refresh is shown.

Repository number is a unique identifier of the repository in current set of repositories. If you add, remove or change a repository, the numbers may change. Keep that in mind when using the numbers with the repository handling commands. On the other hand, using the alias instead of the number is always safe.

To show detailed information about specific repositories, specify them as arguments, either by alias, name, number from simple zypper lr, or by URI; e.g. fB zypper lr factory, or zypper lr 2.

-e, --export FILE.repo|-

-a, --alias

-n, --name

-u, --uri

-p, --priority

-r, --refresh

-d, --details

-E, --show-enabled-only

-U, --sort-by-uri

-P, --sort-by-priority

-A, --sort-by-alias

-N, --sort-by-name

Examples:

Examples:

-n, --name name

-e, --enable

-d, --disable

-f, --refresh (legacy: -r)

-F, --no-refresh (legacy: -R)

-p, --priority positive-integer

-k, --keep-packages

-K, --no-keep-packages

-g, --gpgcheck

--gpgcheck-strict

--gpgcheck-allow-unsigned

--gpgcheck-allow-unsigned-repo

--gpgcheck-allow-unsigned-package

-G, --no-gpgcheck

--default-gpgcheck

-a, --all

-l, --local

-t, --remote

-m, --medium-type type

Examples:

-f, --force

-b, --force-build

-d, --force-download

-B, --build-only

-D, --download-only

-s, --services

-m, --metadata

-M, --raw-metadata

-a, --all

Newly added services are not refreshed automatically. Use the refresh-services command to refresh them. Zypper does not access the service URI when adding the service, so the type of the services is unknown until it is refreshed.

-n, --name name

-e, --enable

-d, --disable

-f, --refresh

-F, --no-refresh

--loose-auth

--loose-query

Common Options

-n, --name name

-e, --enable

-d, --disable

-f, --refresh (legacy: -r)

-F, --no-refresh (legacy: -R)

-a, --all

-l, --local

-t, --remote

-m, --medium-type type

RIS Service Specific Options

-i, --ar-to-enable alias

-I, --ar-to-disable alias

-j, --rr-to-enable alias

-J, --rr-to-disable alias

-k, --cl-to-enable

-K, --cl-to-disable

-u, --uri

-p, --priority

-d, --details

-r, --with-repos

-P, --sort-by-priority

-E, --show-enabled-only

-U, --sort-by-uri

-N, --sort-by-name

RIS services add, remove, or modify repositories on your system based on current content of the repository index. A differing enabled/disabled state caused by manually calling modify-repo on a service repository however will not be reverted unless the --restore-status option is used, or the repository index explicitly requests the change.

Services only manage defined repositories, they do not refresh them. To refresh also repositories, use --with-repos option or the refresh command.

-f, --force

-r, --with-repos

-R, --restore-status

-m, --matches

-s, --solvables

-r, --repo alias|name|#|URI

-t, --type type

-r, --repo alias|name|#|URI

-t, --type type

This command looks for locks that do not currently (with regard to repositories used) lock any package and for each such lock it asks user whether to remove it.

-a, --all

-p, --packages

-n, --no-packages

-n, --no-packages

$ zypper locales

$ zypper locales --packages de en

$ zypper locales en_

$ zypper locales en*

$ zypper aloc --packages de_CH

The default output is in human-friendly form. If --terse global option is used, the result is an integer number, negative/positive if version1 is older/newer than version2, zero if they match.

-m, --match

First, a list of all packages and their licenses and/or EULAs is shown. This is followed by a summary, including the total number of installed packages, the number of installed packages with EULAs that required a confirmation from the user. Since the EULAs are not stored on the system and can only be read from repository metadata, the summary includes also the number of installed packages that have their counterpart in repositories. The report ends with a list of all licenses uses by the installed packages.

This command can be useful for companies redistributing a custom distribution (like appliances) to figure out what licenses they are bound by.

Per default packages are downloaded to the libzypp package cache (/var/cache/zypp/packages; for non-root users $XDG_CACHE_HOME/zypp/packages), but this can be changed by using the global --pkg-cache-dir option.

Parsable XML-output produced by zypper --xmlout will include a <download-result> node for each package zypper tried to download. Upon success the location of the downloaded package is found in the path attribute of the <localfile> subnode (xpath: download-result/localpath@path):

        <download-result>


          <solvable>


            <kind>package</kind>


            <name>zypper</name>


            <edition epoch="0" version="1.9.17" release="26.1"/>


            <arch>x86_64</arch>


            <repository name="repo-oss-update (13.1)" alias="openSUSE:repo-oss-update"/>


          </solvable>


          <localfile path="/var/cache/zypp/pac.../zypper-1.9.17-26.1.x86_64.rpm"/>


        </download-result>

--all-matches

--dry-run

-r, --repo alias|name|#|URI

--from alias|name|#|URI

-d, --directory dir

--delete

--no-delete

--status

PID

PPID

UID

Login

Command

Service

Files

-s, --short

--print format

-d, --debugFile filename

Examples:

The reboot-needed flag is set if a package that provides installhint(reboot-needed) is updated or installed. Additionally there is a predefined list (/etc/zypp/needreboot) of well-known packages which cause the reboot-needed flag being set unconditionally. Exit code ZYPPER_EXIT_INF_REBOOT_NEEDED indicates that a reboot is needed, otherwise the exit code is set to ZYPPER_EXIT_OK.