table of contents
ZYPPER(8) | ZYPPER | ZYPPER(8) |
NAME¶
zypper - Command-line interface to ZYpp system management library (libzypp)
SYNOPSIS¶
zypper [--global-opts] command [--command-opts] [command-arguments]
zypper subcommand [--command-opts] [command-arguments]
zypper help command
DESCRIPTION¶
zypper is a command-line interface to ZYpp system management library (libzypp). It can be used to install, update, remove software, manage repositories, perform various queries, and more.
CONCEPTS¶
Most of the following concepts are common for all applications based on the libzypp package management library, but there are some zypper specifics.
System Packages¶
The set of installed packages on a system is sometimes denoted as repository @System or System Packages. In contrast to available repositories providing packages which can be installed, @System provides packages which can only be deleted. Installed packages which are not provided by at least one of the available repositories (neither in different version or as renamed package) are often denoted as being unwanted, orphaned or dropped.
Note: If you install packages which are not shipped within a repository - manually built or downloaded ones -, collect them within a local directory and add this directory as a plaindir repository to your system. This way the packages will not be seen as being orphaned and are protected during a dist-upgrade.
Creating such a plaindir repo is quite easy:
$ mkdir /LocalRepo
$ zypper addrepo --refresh /LocalRepo LocalRepo
If you need to make sure the package to install is taken from
LocalRepo, simply use a REPO:PACKAGE style argument:
$ cp example.rpm /LocalRepo
$ zypper install LocalRepo:example
Depending on the kind of packages you keep in a local repo you may want to adjust the way GPG signature checks are performed. See section GPG checks for details.
Repositories¶
Libzypp works with repository metadata, this is information about packages and their relations extracted from RPM packages and other data like patch information, pattern definitions, etc. These data are stored together with the RPM files in folders called repositories. Repositories can be placed on various media like an HTTP or FTP server, DVD, or a folder on a local disc.
There is a special set of commands in zypper intended to manipulate repositories. Also many commands and options take a repository as an argument. See section COMMANDS, subsection Repository Management for more details.
GPG checks¶
Disabling GPG checks is not recommended. Signing data enables the recipient to verify that no modifications occurred after the data were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system and in extreme cases even to a system compromise.
Zypp verifies the authenticity of repository metadata by checking their GPG signature. If the repository metadata are signed with a trusted key and successfully verified, packages from this repository are accepted for installation if they match the checksum provided in the metadata. Using unsigned repositories needs to be confirmed.
If the repository metadata are not signed, the GPG signature of each downloaded rpm package is checked before accepting it for installation. Packages from unsigned repositories need a valid GPG signature. Using unsigned packages needs to be confirmed.
The above is the default behavior defined by settings in /etc/zypp/zypp.conf.
The addrepo and modifyrepo commands provide further options to tune the behavior per repository. It is for example possible to relax the need to confirm installing unsigned packages for a specific repository. But if you do so, you should be very certain that an attacker can hardly modify the package data within the repository or on the way to your machine. See section COMMANDS for details about the command options.
Resource Identifiers (URI)¶
To specify locations of repositories or other resources (RPM files, .repo files) you can use any type of URI supported by libzypp. In addition Zypper accepts a special URI identifying openSUSE Build Service (OBS) repositories in the addrepo command. These URIs have the form of obs://project/[platform].
See section COMMANDS, subsection Repository Management for a complete list and examples of supported URI formats.
Refresh¶
Refreshing a repository means downloading metadata of packages from the medium (if needed), storing it in local cache (typically under /var/cache/zypp/raw/alias directory) and preparsing the metadata into .solv files (building the solv cache), typically under /var/cache/zypp/solv/alias.
The metadata get refreshed either automatically or on user request. An automatic refresh takes place right before reading metadata from the database if the auto-refresh is enabled for the repository and the metadata is reported to be out of date. If the auto-refresh is disabled, the repository will only be refreshed on user request. You can request a refresh by calling zypper refresh (see the documentation of the refresh command for details).
The repository metadata are checked for changes before actually doing the refresh. A change is detected by downloading one or two metadata index files (small files) and comparing the checksums of the cached ones and the remote ones. If the files differ, the repository is out of date and will be refreshed.
To delay the up-to-date check (and thus the automatic refresh) for a certain number of minutes, edit the value of the repo.refresh.delay attribute of ZYpp config file (/etc/zypp/zypp.conf). This means, zypper will not even try to download and check the index files, and you will be able to use zypper for operations like search or info without internet access or root privileges.
Services¶
Services are one level above repositories and serve to manage repositories or to do some special tasks. Libzypp currently supports Repository Index Service (RIS) and Plugin Service.
Repository Index Service (RIS) is a special type of repository which contains a list of other repositories. This list can be generated dynamically by the server according to some URI parameters or user name, or can be static. Once such service is added to your system, zypper takes care of adding, modifying, or removing these repositories on your system to reflect the current list. See section Service Management and <https://en.opensuse.org/openSUSE:Standards_Repository_Index_Service> for more details.
Package Types¶
Zypper works with several types of resource objects, called resolvables. A resolvable might be a package, patch, pattern, product; basically any kind of object with dependencies to other objects.
package
patch
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, bugfix), (optional, feature, enhancement) document or yast. Commonly used values for severity are critical, important, moderate, low or unspecified. Names listed in parentheses are used synonymously.
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.
pattern
product
srcpackage
application
Throughout this manual we will often refer to resolvables simply as packages and to resolvable types as package type or kind. These type names can be used as arguments of --type option in several commands like install, info, or search. Commands should also allow one to specify resolvables as KIND:NAME (e.g. patch:openSUSE-2014-7).
Package Dependencies¶
Software packages depend on each other in various ways. Packages usually require or recommend other packages, but they can also conflict with them. Packages may support specific hardware or language settings. Zypper uses a dependency solver to find out which packages need to be installed to satisfy the user’s request.
If you do not request a specific version of a package the solver will pick a reasonable one. The solvers general attitude when resolving a job is to focus on installing the best version of the requested package and to add or update dependencies as they are needed. Aside from this Focus on Job, which is the default, two other focus modes are available:
In Focus on Installed mode the solver focuses on applying as little changes to the installed packages as needed. Choosing an older version of a requested package is valid if it’s dependencies require less changes to the system. The solver will try to avoid updating already installed packages.
In Focus on Update mode the solver focuses on updating the requested package and all its dependencies as much as possible. Beware, installing a single package in this mode may easily lead to a mini system update.
For a single command the focus mode can be set using the --solver-focus MODE switch. Valid modes are Job, Installed or Update. If you want to change the default mode for your system, set [/etc/zypp/zypp.conf:solver.focus] to the desired value.
Automatically installed packages¶
Packages added by the dependency solver in order to resolve a user’s request are remembered as having been automatically installed. They may later be removed, if no more user installed packages depend on them (e.g. by zypper remove --clean-deps).
In the Status column the search command distinguishes between user installed packages (i+) and automatically installed packages (i).
Package File Conflicts¶
File conflicts happen when two packages attempt to install files with the same name but different contents. This may happen if you are installing a newer version of a package without erasing the older version, of if two unrelated packages each install a file with the same name.
As checking for file conflicts requires access to the full filelist of each package being installed, zypper will be able to check for file conflicts only if all packages are downloaded in advance (see --download-in-advance). If you are doing a --dry-run no packages are downloaded, so the file conflict check will skip packages not available in the packages cache. To get a meaningful file conflict check use --dry-run together with --download-only.
As the reason for file conflicts usually is a poor package design or lack of coordination between the people building the packages, they are not easy to resolve. By using the --replacefiles option you can force zypper to replace the conflicting files. Nevertheless this may damage the package whose file gets replaced.
COMMANDS¶
zypper provides a number of commands. Each command accepts the options listed in the GLOBAL OPTIONS section. These options must be specified before the command name. In addition, many commands have specific options, which are listed in this section. These command-specific options must be specified after the name of the command and before any of the command arguments.
Zypper also provides limited support for writing extensions/subcommands in any language. See section SUBCOMMANDS for details.
General Commands¶
help [command]
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:
shell (sh)
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.
Package Management Commands¶
info (if) [options] name...
For each specified package, zypper finds the best available version in defined repositories and shows information for this package. In case the query result is empty zypper returns ZYPPER_EXIT_INF_CAP_NOT_FOUND, unless the --ignore-unknown global option is set.
-r, --repo alias|name|#|URI
-t, --type type
--provides
--requires
--conflicts
--obsoletes
--recommends
--suggests
--supplements
Examples:
$ zypper info workrave
$ zypper info -t patch libzypp
$ zypper info -t pattern lamp_server
install (in) [options] name|capability|rpm_file_uri...
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.
The NAME component of a capability is not only a package name but any symbol provided by packages: /bin/vi, libcurl.so.3, perl(Time::ParseDate). Just remember to quote to protect the special characters from the shell, for example: zypper\>0.8.10 or 'zypper>0.8.10'.
If EDITION is not specified, the newest installable version will be installed. This also means that if the package is already installed and newer versions are available, it will get upgraded to the newest installable version.
If ARCH is not specified, or the last dot of the capability name string is not followed by known architecture, the solver will treat the whole string as a capability name. If the ARCH is known, the solver will select a package matching that architecture and complain if such package cannot be found.
If you want to make sure a package from a specific REPOSITORY is picked, use REPOSITORY:PACKAGENAME as argument.
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.:
$ zypper install ~/rpms/foo.rpm http://some.site/bar.rpm
Zypper will report packages that it cannot find. Further, in interactive mode, zypper proceeds with installation of the rest of requested packages, and it will abort immediately in non-interactive mode. In both cases zypper returns ZYPPER_EXIT_INF_CAP_NOT_FOUND after finishing the operation.
Zypper will collect the files in a temporary plaindir repository and mark the respective packages for installation. If --download-only is used, the downloaded packages will be available in /var/cache/zypper/RPMS until you actually install them or call zypper clean to clear the package caches. They will not become part of the global package cache at /var/cache/zypp/packages (see also the global --pkg-cache-dir option).
In the install command, you can also specify packages you wish to remove by prepending their names by a - or ! character. For example:
$ zypper install \!Firefox
In contrast to zypper remove Firefox which removes Firefox and its dependent packages, the install command will try to keep dependent packages installed by looking for Firefox alternatives.
Note that if you choose to use - with the first package you specify, you need to write -- before it to prevent its interpretation as a command option:
$ zypper install -- -boring-game great-game great-game-manual
-r, --repo alias|name|#|URI
Using --repo is discouraged as it currently hides unmentioned repositories from the resolver, leading to inexpertly decisions. In the future --repo will become an alias for --from.
If you want to install a package from a specific repository, use REPOSITORY:PACKAGENAME as argument.
-t, --type type
If patch is specified, zypper will install and/or remove packages to satisfy specified patch. This is a way to ensure that specific bug fix is installed. Use zypper list-patches to look for applicable patches.
If product or pattern are specified, zypper ensures that all required (and optionally recommended) packages are installed.
-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
In order to perform the requested job the solver is allowed to violate any otherwise active policy. This includes the allowance to remove packages but also not to respect even explicitly set policies (by --no-allow-policy or in config files). It is not recommended to use this option in unattended environments.
The allowance to remove dependent packages is the default when removing packages (zypper remove).
-R, --no-force-resolution
--solver-focus MODE
--recommends
--no-recommends
Download-and-install mode options:
-d, --download-only
If used together with --dry-run a meaningful file conflict check can be performed (see section Package File Conflicts).
--download-in-advance
--download-in-heaps
Note
While the resolver is not capable of building heaps, this behaves the same as --download-in-advance.
--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:
$ zypper install -t pattern lamp_server
$ zypper install --no-recommends gv
$ zypper install virtualbox-ose-2.0.6
$ zypper install virtualbox-ose=2.0.6
$ zypper install virtualbox-ose = 2.0.6
source-install (si) name...
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:
$ zypper si -d dbus-1
verify (ve) [options]
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
In order to perform the requested job the solver is allowed to violate any otherwise active policy. This includes the allowance to remove packages but also not to respect even explicitly set policies (by --no-allow-policy or in config files). It is not recommended to use this option in unattended environments.
The allowance to remove dependent packages is the default when removing packages (zypper remove).
-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.
install-new-recommends (inr) [options]
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
In order to perform the requested job the solver is allowed to violate any otherwise active policy. This includes the allowance to remove packages but also not to respect even explicitly set policies (by --no-allow-policy or in config files). It is not recommended to use this option in unattended environments.
The allowance to remove dependent packages is the default when removing packages (zypper remove).
-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.
remove (rm) [options] name...
remove (rm) [options] --capability capability...
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
Since patches are not installed in sense of copying files or recording a database entry, they cannot be uninstalled, even though zypper shows them as installed. The installed status is determined solely based on the installed status of its required dependencies. If these dependencies are satisfied, the patch is rendered installed.
-n, --name
-C, --capability
-D, --dry-run
--details
-y, --no-confirm
Solver related options:
--debug-solver
--force-resolution
In order to perform the requested job the solver is allowed to violate any otherwise active policy. This includes the allowance to remove packages but also not to respect even explicitly set policies (by --no-allow-policy or in config files). It is not recommended to use this option in unattended environments.
The allowance to remove dependent packages is the default when removing packages (zypper remove).
-R, --no-force-resolution
--solver-focus MODE
-u, --clean-deps
-U, --no-clean-deps
removeptf (rmptf) [options] <PTF|CAPABILITY> ...
A remove command which prefers replacing dependant packages to removing them as well. In fact this is a full featured install command with the remove modifier (-) applied to its plain arguments. So removeptf foo is the same as install — -foo. This is why the command accepts the same options as the install command. It is the recommended way to remove a PTF (Program Temporary Fix).
A PTF is typically removed as soon as the fix it provides is applied to the latest official update of the dependant packages. But you don’t want the dependant packages to be removed together with the PTF, which is what the remove command would do. The removeptf command however will aim to replace the dependant packages by their official update versions.
supports every option the install command supports
purge-kernels [options]
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
Update Management Commands¶
list-updates (lu) [options]
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
If patch is specified, zypper acts as if the list-patches command was executed.
-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
update (up) [options] [packagename]...
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
If patch is specified, zypper acts as if the patches command was executed.
-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
In order to perform the requested job the solver is allowed to violate any otherwise active policy. This includes the allowance to remove packages but also not to respect even explicitly set policies (by --no-allow-policy or in config files). It is not recommended to use this option in unattended environments.
The allowance to remove dependent packages is the default when removing packages (zypper remove).
-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.
list-patches (lp) [options]
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
patch-check (pchk)
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
patch [options]
When updating the affected/vulnerable packages described by a patch, zypper always aims for the latest available version. See section Package Types for more details about how patches operate.
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
--skip-not-applicable-patches
In scripted and unattended environments it may be desired to try to apply at least as many patches as possible so the system is not left completely without updates. It is highly recommended to run zypper patch-check afterwards in order to see whether needed patches are still waiting to be resolved interactively.
--with-update
The option is ignored, if the patch command must update the update stack first, thus it can not be combined with the --updatestack-only option.
--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
In order to perform the requested job the solver is allowed to violate any otherwise active policy. This includes the allowance to remove packages but also not to respect even explicitly set policies (by --no-allow-policy or in config files). It is not recommended to use this option in unattended environments.
The allowance to remove dependent packages is the default when removing packages (zypper remove).
-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.
dist-upgrade (dup) [options]
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
--remove-orphaned
'Note:' Packages which are not shipped within a repository - manually built or downloaded ones -, can be collected in a plaindir repository to prevent them from being treated as orphaned. See section *System Packages* for details.
-r, --repo alias|name|#|URI
Using --repo is discouraged as it currently hides unmentioned repositories from the resolver, leading to inexpertly decisions. This is because packages originally installed from the hidden repos will now be treated as orphaned or dropped. They can be silently removed if involved in a dependency conflict. In the future --repo will become an alias for --from.
-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
In order to perform the requested job the solver is allowed to violate any otherwise active policy. This includes the allowance to remove packages but also not to respect even explicitly set policies (by --no-allow-policy or in config files). It is not recommended to use this option in unattended environments.
The allowance to remove dependent packages is the default when removing packages (zypper remove).
-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:
$ zypper dup --from factory --from packman
Query Commands¶
search (se) [options] [querystring|capability]...
Results of the search are printed in a table with columns Status, Name, Summary and Type of package. In case the query result is empty zypper returns ZYPPER_EXIT_INF_CAP_NOT_FOUND, unless the --ignore-unknown global option is set.
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:
i+
i
v
empty
!
.l
.P
.R
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
The old option name --uninstalled-only is still acceptable, but should be considered deprecated.
-t, --type type
See also the type-specific query commands like packages, patterns, etc.
-r, --repo alias|name|#|URI
--sort-by-name
--sort-by-repo
-s, --details
-v, --verbose
Examples:
$ zypper se 'yast*'
$ zypper se -s --match-exact kernel-default
$ zypper se -dC --match-words RSI
packages (pa) [options] [repository]...
-r, --repo alias|name|#|URI
-i, --installed-only
-u, --not-installed-only
The old option name --uninstalled-only is still acceptable, but should be considered deprecated.
*--autoinstalled
--userinstalled
--system
--orphaned
--suggested
--recommended
--unneeded
patches (pch) [options] [repository]...
-r, --repo alias|name_|#|URI
patterns (pt) [options] [repository]...
-r, --repo alias|name|#|URI
-i, --installed-only
-u, --not-installed-only
The old option name --uninstalled-only is still acceptable, but should be considered deprecated.
products (pd) [options] [repository]...
-r, --repo alias|name|#|URI
-i, --installed-only
-u, --not-installed-only
The old option name --uninstalled-only is still acceptable, but should be considered deprecated.
--xmlfwd tag
Using this option, for each installed product an <xmlfwd> node will be created inside the <product> output node of the product.
Tag defines the name (or /-separated path) of a xml-tag inside an installed products .prod-file. If the tag is present inside the products .prod-file, the tag and it’s content is literally forwarded into the products <xmlfwd> output node.
The option may be specified multiple times.
Examples:
$ zypper -x pd --xmlfwd name --xmlfwd register/target
what-provides (wp) capability
The command line is automatically transformed into the corresponding search command:
$ zypper what-provides 'zypper>1.6'
For a case-sensitive search call
Repository Management¶
Zypper is able to work with YaST, RPM-MD (yum) software repositories, and plain directories containing .rpm files (no symlinks).
Repositories are primarily identified using their URI or alias. Alias serves as a shorthand for the long URI or name of the repository. The name of the repository should briefly describe the repository and is shown to the user in tables and messages. The name is not required, and if not known, the alias is shown instead. The alias is required and uniquely identifies the repository on the system.
The alias, name, URI, or the number from zypper repos list can be used to specify a repository as an argument of various zypper commands and options like refresh, --repo, or --from.
Apart from the above, repositories have several other properties which can be set using the commands described in this section below, or by manually editing the repository definition files (.repo files, see section FILES).
Variable substitution:¶
You can use the following variables within a .repo or .service files name and URI values:
$arch
$basearch
$releasever, $releasever_major, $releasever_minor
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.
Custom Variables
This is how you can set a custom variable, e.g. $releasever to a value of 99.0:
To remove the custom variable, simply delete its file in /etc/zypp/vars.d:
To check where you already use $releasever call:
Remember to protect the $ when using these variables on a shell command line:
If a variable is followed by an alphanumeric character or underscore it needs to be enclosed in {}:
Bash style definition of default ${variable:-word} and alternate ${variable:+word} values:
NOTE:
Supported URI formats:¶
scheme:@]host[:port]]/path[?query][#fragment]
CD or DVD drive
dvd:/subdir?devices=/dev/sr0,/dev/sr1
FTP/HTTP/HTTPS directory tree
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).
ftp://user:pass@server/%2fhome/user/path/to/media/dir
http://user:pass@server/path
https://user:pass@server/path?proxy=foo&proxyuser=me&proxypass=pw
https://server/path?ssl_clientcert=/entitlement/1234.pem&ssl_clientkey=/entitlement/1234-key.pem
Disk volume (partition)
Local directory tree
Media in an ISO image (loopback mounted)
iso:/?iso=CD1.iso&url=hd:/?device=/dev/hda
iso:/subdir?iso=DVD1.iso&url=nfs://nfs-server/directory&mnt=/nfs/attach/point&filesystem=udf
NFS exported directory tree
nfs://nfs-server/exported/path?mountoptions=ro&type=nfs4
nfs4://nfs-server/exported/path?mountoptions=ro
CIFS/SMB directory tree
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.
cifs://usern:passw@servername/share/path/on/the/share?mountoptions=ro,noguest
cifs://usern:passw@servername/share/path/on/the/share?workgroup=mygroup
cifs://servername/share/path/on/the/share?user=usern&pass=passw
OpenSUSE Build Build Service (OBS) repositories
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.
obs://zypp:Head/openSUSE_Factory
obs://zypp:Head/openSUSE_Factory_Staging_Gcc49_standard
Commands:¶
addrepo (ar) [options] URI alias
addrepo (ar) [options] FILE*.repo*
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 [1-2147483647]|0
-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
Disabling GPG checks is not recommended. Signing data enables the recipient to verify that no modifications occurred after the data were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system and in extreme cases even to a system compromise.
--default-gpgcheck
Unless you have modified your zypp.conf settings, this is the same as --gpgcheck, the behavior as described in section GPG checks.
Examples:
$ zypper ar -c -n 'Packman 11.1 repo' http://packman.iu-bremen.de/suse/11.1 packman
$ zypper ar https://download.opensuse.org/repositories/zypp:/svn/openSUSE_Factory/zypp:svn.repo
$ zypper ar myreposbackup.repo
removerepo (rr) [options] alias|name|#|URI...
--loose-auth
--loose-query
-a, --all
-l, --local
-t, --remote
-m, --medium-type type
repos (lr) [options] [repo]...
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:
$ zypper repos -e myreposbackup.repo
$ zypper lr -pu
renamerepo (nr) alias|name|#|URI new-alias
Examples:
$ zypper nr 8 myrepo
modifyrepo (mr) options alias|name|#|URI...
modifyrepo (mr) options --all|--remote|--local|--medium-type
-n, --name name
-e, --enable
-d, --disable
-f, --refresh (legacy: -r)
-F, --no-refresh (legacy: -R)
-p, --priority [1-2147483647]|0
-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
Disabling GPG checks is not recommended. Signing data enables the recipient to verify that no modifications occurred after the data were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system and in extreme cases even to a system compromise.
--default-gpgcheck
Unless you have modified your zypp.conf settings, this is the same as --gpgcheck, the behavior as described in section GPG checks.
-a, --all
-l, --local
-t, --remote
-m, --medium-type type
Examples:
$ zypper mr -kt
$ zypper mr -er updates
$ zypper mr -da
refresh (ref) [alias|name|#|URI]...
-f, --force
-b, --force-build
-d, --force-download
-B, --build-only
-D, --download-only
-s, --services
clean (cc) [options] [alias|name|#|URI]...
-m, --metadata
-M, --raw-metadata
-a, --all
Service Management¶
The services, addservice, removeservice, modifyservice, and refresh-services commands serve for manipulating services. A service is specified by its URI and needs to have a unique alias defined (among both services and repositories).
Standalone repositories (not belonging to any service) are treated like services, too. The ls command will list them, ms command will modify them, etc. Repository specific options, like --keep-packages are not available here, though. You can use repository handling commands to manipulate them.
addservice (as) [options] URI alias
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
removeservice (rs) [options] alias|name|#|URI...
--loose-auth
--loose-query
modifyservice (ms) options alias|name|#|URI
modifyservice (ms) options --all|--remote|--local|--medium-type
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
services (ls) [options]
-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
refresh-services (refs) [options] alias|name|#|URI...
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
Package Locks Management¶
Package locks serve the purpose of preventing changes to the set of installed packages on the system. Locks are stored as queries in /etc/zypp/locks file (see also locks(5)). Packages matching a query are then forbidden to change their installed status; an installed package can’t be removed or upgraded, not installed package can’t be installed. When requesting to install, upgrade or remove such locked package, you will get a dependency problem dialog.
A lock-spec is formed by "NAME [OP EDITION]", where NAME may also be a glob pattern using * and ? wildcard characters. Non-package types may to have their kind-string prepended (e.g. patch:foo or product:baa) or use the commands --type option.
The basic form will lock all editions of the matching items. You can optionally restrict the lock to match a specific edition or edition range using =, <, <=, >, >= or != followed by the edition.
Note
If you use blanks around the operator you need to quote the string or escape the blanks according to the rules of the shell you are using.
locks (ll)
-m, --matches
-s, --solvables
addlock (al) [options] lock-spec...
-r, --repo alias|name|#|URI
-t, --type type
-m, --comment comment
removelock (rl) [options] lock-number|lock-spec...
-r, --repo alias|name|#|URI
-t, --type type
cleanlocks (cl)
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.
Locale Management¶
These commands give information about requested locales and the possibility to manage those. A locale is defined by a language code. For many packages there are locale dependent packages available which provide translations or dictionaries. To get these installed, the locale for the desired language must be marked as requested by the package manager library.
locales (lloc) [OPTIONS] [LOCALE] ...
-a, --all
-p, --packages
addlocale (aloc) [OPTIONS] <LOCALE> ...
-n, --no-packages
removelocale (rloc) [OPTIONS] <LOCALE> ...
-n, --no-packages
Examples:
$ zypper locales
$ zypper locales --packages de en
$ zypper locales en_
$ zypper locales en*
$ zypper aloc --packages de_CH
Other Commands¶
versioncmp (vcmp) version1 version2
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
For example:
$ zypper vcmp -m 0.15.3 0.15.3-2
$ zypper vcmp 0.15.3 0.15.3-2
targetos (tos)
If the baseproduct does not provide this entry, or if no baseproduct is installed at all, the value is empty if the --terse global option is used.
In not-terse mode the distribution label is shown instead of an empty value, if a baseproduct is installed.
-l, --label
licenses
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.
download [OPTIONS]
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
source-download [OPTIONS]
-d, --directory dir
--delete
--no-delete
--status
ps [OPTIONS]
PID
PPID
UID
Login
Command
Service
Files
-s, --short
--print format
-d, --debugFile filename
Examples:
$ zypper ps -ss
$ zypper ps -sss
$ zypper ps --print "systemctl status %s"
needs-rebooting
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. The exit code ZYPPER_EXIT_INF_REBOOT_NEEDED indicates that a reboot is suggested, otherwise the exit code is set to ZYPPER_EXIT_OK.
It is recommended for scripts to use this command to test whether a system reboot is suggested. Use --quiet to suppress the normal output.
Subcommands¶
subcommand
GLOBAL OPTIONS¶
-h, --help
-V, --version
-c, --config file
The order of preference with --config is as follows:
Note
Use and location of the system-wide /etc/zypp/zypp.conf can not be changed this way. It’s mentioned here just because some zypper command line options allow one to overwrite system-wide defaults defined in zypp.conf.
See also FILES section for more information.
-v, --verbose
-q, --quiet
--color, --no-color
-A, --no-abbrev
-t, --terse
-s, --table-style integer
-n, --non-interactive
--non-interactive-include-reboot-patches
-x, --xmlout
-i, --ignore-unknown
For search and info commands the option makes zypper return ZYPPER_EXIT_OK rather than ZYPPER_EXIT_INF_CAP_NOT_FOUND if the query did not produce at least one match.
-D, --reposd-dir dir
-C, --cache-dir dir
--raw-cache-dir dir
--solv-cache-dir dir
--pkg-cache-dir dir
--userdata string
Repository Options:
--no-gpg-checks
--gpg-auto-import-keys
-p, --plus-repo URI
--plus-content tag
If a disabled repositories metadata are not available in the local cache, they will be downloaded to scan for matching keywords. Otherwise the keyword scan will use the metadata available in the local cache. Only if used together with the refresh command, a keyword scan will refresh all disabled repositories.
To refresh all disabled repositories metadata:
To include a disabled repository repo-debug in a search:
To search only in a disabled repository repo-debug:
To enable all repos providing the debug keyword:
--disable-repositories
--no-refresh
--no-cd
--no-remote
--releasever version
To check where you already use $releasever call:
Target Options:
-R, --root dir
--installroot dir
--disable-system-resolvables
SUBCOMMANDS¶
Zypper subcommands are inspired by git(1). Subcommands are standalone executables that live in the zypper_execdir (/usr/lib/zypper/commands). For subcommands zypper provides a wrapper that knows where the subcommands live, and runs them by passing command options and arguments to them. If a subcommand is not found in the zypper_execdir, the wrapper will look in the rest of your $PATH for it. Thus, it’s possible to write local zypper extensions that don’t live in system space. This can be disabled by setting "subcommand.seachSubcommandInPath" to "no" in the zypper.conf.
This is how to add your own subcommand zypper mytask:
You can use the built-in zypper subcommand command to get a list of all subcommands in zypper_execdir and from elsewhere on your $PATH.
Using zypper global-options together with subcommands, as well as executing subcommands in zypper shell is currently not supported.
FILES¶
/etc/zypp/zypper.conf, $HOME/.zypper.conf
User’s settings are preferred over global settings. Similarly, command line options override the settings in either of these files. To sum it up, the order of preference is as follows (from highest to lowest):
See the comments in /etc/zypp/zypper.conf for a list and description of available options.
Note
The system-wide /etc/zypp/zypp.conf is mentioned here just because some zypper command line options allow one to overwrite system-wide defaults defined there. zypp.conf and zypper.conf have different content and serve different purpose.
/etc/zypp/zypp.conf
/etc/zypp/locks
This file is used by all ZYpp-based applications.
/etc/zypp/repos.d
You can use the --reposd-dir global option to use an alternative directory for this purpose or the --root option to make this directory relative to the specified root directory.
This directory is used by all ZYpp-based applications.
/etc/zypp/services.d
This directory is used by all ZYpp-based applications.
/usr/lib/zypper/commands
/var/cache/zypp/raw
This directory is used by all ZYpp-based applications.
/var/cache/zypp/solv
This directory is used by all ZYpp-based applications.
/var/cache/zypp/packages
This directory is used by all ZYpp-based applications.
/var/log/zypper.log
/var/log/zypper.solverTestCase
/var/log/updateTestcase-YYYY-MM-DD-hh-mm-ss
/var/log/zypp/history
~/.zypper_history
/etc/zypp/needreboot
/etc/zypp/needreboot.d
EXIT CODES¶
There are several exit codes defined for zypper built-in commands for use e.g. within scripts. These codes are defined in header file src/zypper-main.h found in zypper source package. Codes below 100 denote an error, codes above 100 provide a specific information, 0 represents a normal successful run. Following is a list of these codes with descriptions:
0 - ZYPPER_EXIT_OK
1 - ZYPPER_EXIT_ERR_BUG
2 - ZYPPER_EXIT_ERR_SYNTAX
3 - ZYPPER_EXIT_ERR_INVALID_ARGS
4 - ZYPPER_EXIT_ERR_ZYPP
5 - ZYPPER_EXIT_ERR_PRIVILEGES
6 - ZYPPER_EXIT_NO_REPOS
7 - ZYPPER_EXIT_ZYPP_LOCKED
8 - ZYPPER_EXIT_ERR_COMMIT
100 - ZYPPER_EXIT_INF_UPDATE_NEEDED
101 - ZYPPER_EXIT_INF_SEC_UPDATE_NEEDED
102 - ZYPPER_EXIT_INF_REBOOT_NEEDED
Legacy: Returned after the successful installation of a patch which requires reboot of computer. This legacy behavior is kept, but it’s drawback is that it covers patches only, no packages. The new needs-rebooting command is the recommended way to test whether a system reboot is suggested.
103 - ZYPPER_EXIT_INF_RESTART_NEEDED
104 - ZYPPER_EXIT_INF_CAP_NOT_FOUND
105 - ZYPPER_EXIT_ON_SIGNAL
106 - ZYPPER_EXIT_INF_REPOS_SKIPPED
107 - ZYPPER_EXIT_INF_RPM_SCRIPT_FAILED
Zypper subcommands (see section SUBCOMMANDS) may return different codes which should be described in the commands man page. Call zypper help subcommand to see the subcommands man page if one is provided.
HOMEPAGE¶
AUTHORS¶
The zypper project was started by Martin Vidner, Jan Kupec, Michael Andres, Duncan Mac-Vicar Prett, Josef Reidinger and Stanislav Visnovsky. Many people have later contributed to it.
SEE ALSO¶
locks(5), zypper-log(8), YaST2(8)
2024-09-10 | SUSE Linux |