1ZYPPER(8)                           ZYPPER                           ZYPPER(8)
2
3
4

NAME

6       zypper - Command-line interface to ZYpp system management library
7       (libzypp)
8

SYNOPSIS

10       zypper [--global-opts] command [--command-opts] [command-arguments]
11
12       zypper subcommand [--command-opts] [command-arguments]
13
14       zypper help command
15

DESCRIPTION

17       zypper is a command-line interface to ZYpp system management library
18       (libzypp). It can be used to install, update, remove software, manage
19       repositories, perform various queries, and more.
20

CONCEPTS

22       Most of the following concepts are common for all applications based on
23       the libzypp package management library, but there are some zypper
24       specifics.
25
26   System Packages
27       The set of installed packages on a system is sometimes denoted as
28       repository @System or System Packages. In contrast to available
29       repositories providing packages which can be installed, @System
30       provides packages which can only be deleted. Installed packages which
31       are not also provided by at least one of the available repositories are
32       often denoted as being unwanted, orphaned or dropped.
33
34   Repositories
35       Libzypp works with repository metadata, this is information about
36       packages and their relations extracted from RPM packages and other data
37       like patch information, pattern definitions, etc. These data are stored
38       together with the RPM files in folders called repositories.
39       Repositories can be placed on various media like an HTTP or FTP server,
40       DVD, or a folder on a local disc.
41
42       There is a special set of commands in zypper intended to manipulate
43       repositories. Also many commands and options take a repository as an
44       argument. See section COMMANDS, subsection Repository Management for
45       more details.
46
47   GPG checks
48       Disabling GPG checks is not recommended. Signing data enables the
49       recipient to verify that no modifications occurred after the data were
50       signed. Accepting data with no, wrong or unknown signature can lead to
51       a corrupted system and in extreme cases even to a system compromise.
52
53       Zypp verifies the authenticity of repository metadata by checking their
54       GPG signature. If the repository metadata are signed with a trusted key
55       and successfully verified, packages from this repository are accepted
56       for installation if they match the checksum provided in the metadata.
57       Using unsigned repositories needs to be confirmed.
58
59       If the repository metadata are not signed, the GPG signature of each
60       downloaded rpm package is checked before accepting it for installation.
61       Packages from unsigned repositories need a valid GPG signature. Using
62       unsigned packages needs to be confirmed.
63
64       The above is the default behavior defined by settings in
65       /etc/zypp/zypp.conf.
66
67       The addrepo and modifyrepo commands provide further options to tune the
68       behavior per repository. It is for example possible to relax the need
69       to confirm installing unsigned packages for a specific repository. But
70       if you do so, you should be very certain that an attacker can hardly
71       modify the package data within the repository or on the way to your
72       machine. See section COMMANDS for details about the command options.
73
74   Resource Identifiers (URI)
75       To specify locations of repositories or other resources (RPM files,
76       .repo files) you can use any type of URI supported by libzypp. In
77       addition Zypper accepts a special URI identifying openSUSE Build
78       Service (OBS) repositories in the addrepo command. These URIs have the
79       form of obs://’project'/[platform].
80
81       See section COMMANDS, subsection Repository Management for a complete
82       list and examples of supported URI formats.
83
84   Refresh
85       Refreshing a repository means downloading metadata of packages from the
86       medium (if needed), storing it in local cache (typically under
87       /var/cache/zypp/raw/’alias' directory) and preparsing the metadata into
88       .solv files (building the solv cache), typically under
89       /var/cache/zypp/solv/’alias'.
90
91       The metadata get refreshed either automatically or on user request. An
92       automatic refresh takes place right before reading metadata from the
93       database if the auto-refresh is enabled for the repository and the
94       metadata is reported to be out of date. If the auto-refresh is
95       disabled, the repository will only be refreshed on user request. You
96       can request a refresh by calling zypper refresh (see the documentation
97       of the refresh command for details).
98
99       The repository metadata are checked for changes before actually doing
100       the refresh. A change is detected by downloading one or two metadata
101       index files (small files) and comparing the checksums of the cached
102       ones and the remote ones. If the files differ, the repository is out of
103       date and will be refreshed.
104
105       To delay the up-to-date check (and thus the automatic refresh) for a
106       certain number of minutes, edit the value of the repo.refresh.delay
107       attribute of ZYpp config file (/etc/zypp/zypp.conf). This means, zypper
108       will not even try to download and check the index files, and you will
109       be able to use zypper for operations like search or info without
110       internet access or root privileges.
111
112   Services
113       Services are one level above repositories and serve to manage
114       repositories or to do some special tasks. Libzypp currently supports
115       Repository Index Service (RIS) and Plugin Service.
116
117       Repository Index Service (RIS) is a special type of repository which
118       contains a list of other repositories. This list can be generated
119       dynamically by the server according to some URI parameters or user
120       name, or can be static. Once such service is added to your system,
121       zypper takes care of adding, modifying, or removing these repositories
122       on your system to reflect the current list. See section Service
123       Management and <https://en.opensuse.org/
124       openSUSE:Standards_Repository_Index_Service> for more details.
125
126   Package Types
127       Zypper  works  with  several  types   of   resource   objects,   called
128       resolvables.  A resolvable might be a package, patch, pattern, product;
129       basically any kind of object with dependencies to other objects.
130
131       package
132           An ordinary RPM package.
133
134       patch
135           A released patch conflicts with the affected/vulnerable versions of
136           a   collection   of   packages.   As   long   as   any   of   these
137           affected/vulnerable versions are installed, the  conflict  triggers
138           and  the  patch is classified as needed, optional or as unwanted if
139           the patch is  locked.  +  Selecting  the  patch,  the  conflict  is
140           resolved by updating all installed and affected/vulnerable packages
141           to a version providing the fix. When updating the  packages  zypper
142           always  aims for the latest available version. Resolved patches are
143           classified as either applied or not needed,  depending  on  whether
144           they  refer to actually installed packages. + Depending on the kind
145           of  defect,  patches  are  classified  by  category  and  severity.
146           Commonly  used  values  for  category  are  security,  recommended,
147           optional, feature, document  or  yast.  Commonly  used  values  for
148           severity  are  critical, important, moderate, low or unspecified. +
149           Note that  the  patch  command  does  not  apply  optional  patches
150           (category  optional or feature) by default. If you actually want to
151           consider  all  optional  patches  as  being   needed,   say   patch
152           --with-optional.  Specific patches can be applied using the install
153           command (e.g. zypper install patch:openSUSE-2014-7).
154
155       pattern
156           A group  of  packages  required  or  recommended  to  install  some
157           functionality.
158
159       product
160           A group of packages which are necessary to install a product.
161
162       srcpackage
163           Source  code  package  (.src.rpm).  This  type  works in search and
164           install commands.
165
166       application
167           Legacy: Since libzypp-17.7.0 this type is no longer available.
168
169       Throughout this manual we will often refer  to  resolvables  simply  as
170       packages  and  to  resolvable types as package type or kind. These type
171       names can be used as arguments of --type  option  in  several  commands
172       like  install,  info,  or search. Commands should also allow to specify
173       resolvables as KIND:’NAME' (e.g. patch:openSUSE-2014-7).
174
175   Package Dependencies
176       Software packages depend  on  each  other  in  various  ways.  Packages
177       usually require or recommend other packages, but they can also conflict
178       with other packages. Packages may support specific hardware or language
179       settings.  Zypper  uses  a dependency solver to find out which packages
180       need to be installed to satisfy the user’s request. See <https://
181       en.opensuse.org/Libzypp/Dependencies> for more information.
182
183   Automatically installed packages
184       Packages  added  by  the dependency solver in order to resolve a user’s
185       request are remembered as having been 'automatically  installed'.  They
186       may later be removed, if no more user installed packages depend on them
187       (e.g. by zypper remove --clean-deps).
188
189       In the S+tatus+ column the search command  distinguishes  between  user
190       installed packages (i+) and automatically installed packages (i).
191
192   Package File Conflicts
193       File  conflicts  happen when two packages attempt to install files with
194       the same name but different  contents.  This  may  happen  if  you  are
195       installing  a  newer  version  of  a  package without erasing the older
196       version, of if two unrelated packages each install a file with the same
197       name.
198
199       As  checking for file conflicts requires access to the full filelist of
200       each package being installed, zypper will check for file conflict  only
201       if all packages are downloaded in advance (see --download-in-advance).
202
203       As  the  reason  for file conflicts usually is a poor package design or
204       lack of coordination between the people building the packages, they are
205       not  easy  to resolve. By using the --replacefiles option you can force
206       zypper to replace the conflicting files. Nevertheless this  may  damage
207       the package whose file gets replaced.
208

COMMANDS

210       zypper  provides a number of commands. Each command accepts the options
211       listed in the GLOBAL OPTIONS section. These options must  be  specified
212       before  the  command  name.  In  addition,  many commands have specific
213       options, which are  listed  in  this  section.  These  command-specific
214       options  must be specified after the name of the command and before any
215       of the command arguments.
216
217       Zypper also provides limited support for writing extensions/subcommands
218       in any language. See section SUBCOMMANDS for details.
219
220   General Commands
221       help [command]
222           Shows  help  texts. If invoked without any argument (just zypper or
223           zypper help), zypper displays global  help  text  which  lists  all
224           available  global options and commands. + If invoked with a command
225           name argument, zypper displays help for the specified  command,  if
226           such  command exists. Long as well as short variants of the command
227           names can be used. + For your convenience, zypper help can also  be
228           invoked in any of the following ways:
229
230
231           $ zypper -h|--help [command]
232
233
234           $ zypper [command] -h|--help
235
236           shell (sh)
237               Starts  a  shell for entering multiple commands in one session.
238               Exit the shell using exit, quit, or Ctrl-D. + The shell support
239               is  not  complete  so  expect  bugs  there. However, there’s no
240               urgent need to use the  shell  since  libzypp  became  so  fast
241               thanks  to  the  SAT  solver and its tools (openSUSE 11.0), but
242               still, you’re welcome to experiment with it.
243
244   Package Management Commands
245       info (if) [options] name...
246           Displays detailed information about the specified packages.  +  For
247           each  specified package, zypper finds the best available version in
248           defined repositories and shows information for this package.
249
250           -r, --repo alias|name|#|URI
251               Work only with the repository specified  by  the  alias,  name,
252               number or URI. This option can be used multiple times.
253
254           -t, --type type
255               Type  of  package (default: package). See section Package Types
256               for list of available package types.
257
258           --provides
259               Show symbols the package provides.
260
261           --requires
262               Show symbols the package requires.
263
264           --conflicts
265               Show symbols the package conflicts with.
266
267           --obsoletes
268               Show symbols the package obsoletes.
269
270           --recommends
271               Show symbols the package recommends.
272
273           --suggests
274               Show symbols the package suggests.
275
276           --supplements
277               Show symbols the package supplements.
278
279           Examples:
280
281
282               $ zypper info workrave
283                   Show information about package workrave
284
285               $ zypper info -t patch libzypp
286                   Show information about patch libzypp
287
288               $ zypper info -t pattern lamp_server
289                   Show information about pattern lamp_server
290
291       install (in) [options] name|capability|rpm_file_uri...
292           Install or update packages.
293
294           The packages can be selected by their name or by a capability  they
295           provide.
296               + A capability is formed by "NAME[.’ARCH'][ OP EDITION]", where
297               ARCH is an architecture code, OP is one of <, <=, =, >=,  or  >
298               and    EDITION    is    "VERSION[-’RELEASE']".   For   example:
299               zypper=0.8.8-2 + The NAME component of a capability is not only
300               a  package  name  but any symbol provided by packages: /bin/vi,
301               libcurl.so.3, perl(Time::ParseDate). Just remember to quote  to
302               protect  the  special  characters  from the shell, for example:
303               zypper\>0.8.10  or  'zypper>0.8.10'.  +  If  EDITION   is   not
304               specified,  the  newest  installable version will be installed.
305               This also means that if the package is  already  installed  and
306               newer  versions  are  available,  it  will  get upgraded to the
307               newest installable version. + If ARCH is not specified, or  the
308               last dot of the capability name string is not followed by known
309               architecture, the solver will  treat  the  whole  string  as  a
310               capability name. If the ARCH is known, the solver will select a
311               package matching that architecture and complain if such package
312               cannot be found.
313
314           Zypper  is  also  able  to  install plain RPM files while trying to
315           satisfy   their   dependencies   using   packages   from    defined
316           repositories.  You  can  install a plain RPM file by specifying its
317           location in the install command arguments either as a local path or
318           an URI. E.g.:
319               + $ zypper install ~/rpms/foo.rpm <http://some.site/bar.rpm>. +
320               Zypper will report packages that it cannot  find.  Further,  in
321               interactive mode, zypper proceeds with installation of the rest
322               of  requested  packages,  and  it  will  abort  immediately  in
323               non-interactive    mode.   In   both   cases   zypper   returns
324               ZYPPER_EXIT_INF_CAP_NOT_FOUND after finishing the operation.  +
325               Zypper   will   collect  the  files  in  a  temporary  plaindir
326               repository and mark the respective packages  for  installation.
327               If  --download-only  is  used,  the downloaded packages will be
328               available in /var/cache/zypper/RPMS until you actually  install
329               them or call zypper clean to clear the package caches.
330
331           In  the  install command, you can also specify packages you wish to
332           remove by prepending their  names  by  a  -  or  !  character.  For
333           example:
334               +  $  zypper  install  \!Firefox + In contrast to zypper remove
335               Firefox which removes Firefox and its dependent  packages,  the
336               install  command  will try to keep dependent packages installed
337               by looking for Firefox alternatives. + Note that if you  choose
338               to  use - with the first package you specify, you need to write
339               -- before it to prevent its interpretation as a command option:
340               +    $    zypper    install   --      -boring-game   great-game
341               great-game-manual
342
343           -r, --repo alias|name|#|URI
344               Work only with the repository specified  by  the  alias,  name,
345               number  or URI. This option can be used multiple times. + Using
346               --repo  is  discouraged  as  it  currently  hides   unmentioned
347               repositories   from   the   resolver,   leading  to  inexpertly
348               decisions. In the  future  --repo  will  become  an  alias  for
349               --from.
350
351           -t, --type type
352               Type  of  package  to  install  (default: package). See section
353               Package Types for list of available package types.  Use  zypper
354               se  -t type [name] to look for available items of this type and
355               zypper info -t type name to display more  detailed  information
356               about  the  item.  + If patch is specified, zypper will install
357               and/or remove packages to satisfy specified patch.  This  is  a
358               way  to  ensure  that specific bug fix is installed. Use zypper
359               list-patches to look for applicable patches. +  If  product  or
360               pattern  are  specified,  zypper ensures that all required (and
361               optionally recommended) packages are installed.
362
363           -n, --name
364               Select  packages  by  their  name,  don’t  try  to  select   by
365               capabilities.
366
367           -f, --force
368               Install  even  if  the  item  is already installed (reinstall),
369               downgraded or changes vendor or architecture.
370
371           --oldpackage
372               Allow to replace a newer item with an older one. Handy  if  you
373               are  doing  a  rollback.  Unlike  --force it will not enforce a
374               reinstall, if the item is already installed with the  requested
375               version.
376
377           --from alias|name|#|URI
378               Select packages from specified repository. If strings specified
379               as  arguments  to  the  install  command  match   packages   in
380               repositories  specified in this option, they will be marked for
381               installation. This option currently implies --name, but  allows
382               using wildcards for specifying packages.
383
384           -C, --capability
385               Select packages by capabilities.
386
387           -l, --auto-agree-with-licenses
388               Automatically  say  yes  to  third  party  license confirmation
389               prompt. By using this option, you choose to agree with licenses
390               of  all  third-party  software  this command will install. This
391               option is particularly useful for administrators installing the
392               same  set  of  packages  on  multiple machines (by an automated
393               process) and have the licenses confirmed before.
394
395           --auto-agree-with-product-licenses
396               Automatically accept product licenses only.  This  is  used  by
397               tools  like  SUSEconnect, which ask for confirmation before the
398               product gets registered. So there’s  no  need  to  confirm  the
399               product license again at install time.
400
401           --replacefiles
402               Install  the  packages  even  if they replace files from other,
403               already installed, packages. Default is to treat file conflicts
404               as  an  error.  --download-as-needed disables the file conflict
405               check because access to all packages file lists  is  needed  in
406               advance in order to perform the check.
407
408           -D, --dry-run
409               Test  the  installation,  do  not actually install any package.
410               This option will add the --test option to the rpm commands  run
411               by the install command.
412
413           --details
414               Show the detailed installation summary.
415
416           -y, --no-confirm
417               Don’t require user interaction. Alias for the --non-interactive
418               global option.
419
420           --allow-unsigned-rpm
421               Silently install unsigned rpm  packages  given  as  commandline
422               parameters.
423
424           Solver related options:
425
426
427           --debug-solver
428               Create  solver test case for debugging. Use this option, if you
429               think the dependencies were not solved all right and attach the
430               resulting  /var/log/zypper.solverTestCase directory to your bug
431               report. To use this option, simply add it  to  the  problematic
432               install or remove command.
433
434           --force-resolution
435               Force  the  solver  to  find  a  solution by allowing to remove
436               packages with unfulfilled requirements.  This  is  the  default
437               when  removing  packages (zypper remove). This option overrides
438               --no-force-resolution in case both are specified on the command
439               line.
440
441           -R, --no-force-resolution
442               Do  not  force  the  solver to find a solution. Instead, report
443               dependency  problems  and  prompt  the  user  to  resolve  them
444               manually.  This  is  the  default except when removing packages
445               (zypper remove).
446
447           --recommends
448               Install also recommended packages in addition to  the  required
449               ones.     The     default    behavior    is    determined    by
450               [zypp.conf:solver.onlyRequires].
451
452           --no-recommends
453               Do not install recommended packages, but  only  required  ones.
454               The       default      behavior      is      determined      by
455               [zypp.conf:solver.onlyRequires].
456
457           Download-and-install mode options:
458
459
460           -d, --download-only
461               Only download the packages for later installation.
462
463           --download-in-advance
464               First download all packages, then start installing.
465
466           --download-in-heaps
467               Download a minimal  set  of  packages  that  can  be  installed
468               without  leaving  the system in broken state, and install them.
469               Then download and install another heap until all are installed.
470               This  helps  to keep the system in consistent state without the
471               need to download all packages in advance,  which  combines  the
472               advantages  of  --download-in-advance and --download-as-needed.
473               This is the default mode. + NOTE: While  the  resolver  is  not
474               capable   of   building   heaps,   this  behaves  the  same  as
475               --download-in-advance.
476
477           --download-as-needed
478               Download one package, install it immediately, and continue with
479               the rest until all are installed.
480
481           --download mode
482               Use  the  specified  download-and-install mode. Available modes
483               are: only, in-advance, in-heaps, as-needed.  See  corresponding
484               --download-’mode' options for their description.
485
486           Expert Options:
487               Don’t use them unless you know you need them.
488
489           --[no-]allow-downgrade
490               Whether to allow downgrading installed resolvables.
491
492           --[no-]allow-name-change
493               Whether  to  allow changing the names of installed resolvables.
494               Setting this to no will not replace packages  which  have  been
495               renamed.
496
497           --[no-]allow-arch-change
498               Whether   to  allow  changing  the  architecture  of  installed
499               resolvables.
500
501           --[no-]allow-vendor-change
502               Whether to allow changing the vendor of installed  resolvables.
503               Setting  this to no might be useful if you do not want packages
504               from foreign repos being changed to the  distributions  version
505               (or vice versa).
506
507           Examples:
508
509
510               $ zypper install -t pattern lamp_server
511                   Install lamp_server pattern.
512
513               $ zypper install --no-recommends gv
514                   Install   GhostScript   viewer,   but   ignore  recommended
515                   packages.
516
517               $ zypper install virtualbox-ose-2.0.6
518
519
520               $ zypper install virtualbox-ose=2.0.6
521
522
523               $ zypper install virtualbox-ose = 2.0.6
524                   Install version 2.0.6 of virtualbox-ose package.
525
526       source-install (si) name...
527           Install specified source packages and their build dependencies.  If
528           the  name  of  a  binary package is given, the corresponding source
529           package is looked up and installed instead. + This command will try
530           to  find  the  newest available versions of the source packages and
531           uses rpm -i to install  them,  optionally  together  with  all  the
532           packages that are required to build the source package. The default
533           location   where   rpm   installs    source    packages    to    is
534           /usr/src/packages/{SPECS,SOURCES}, but the values can be changed in
535           your local rpm configuration. In case of doubt  try  executing  rpm
536           --eval  "%{_specdir}  and  %{_sourcedir}".  +  Note that the source
537           packages must be available in repositories you are using.  You  can
538           check  whether  a repository contains any source packages using the
539           following command:
540
541
542               $ zypper search -t srcpackage -r alias|name|#|URI
543
544           -d, --build-deps-only
545               Install only build dependencies of specified packages.
546
547           -D, --no-build-deps
548               Don’t install build dependencies.
549
550           -r, --repo alias|name|#|URI
551               Work only with the repository specified  by  the  alias,  name,
552               number, or URI. This option can be used multiple times.
553
554           --download-only
555               Only download the packages, do not install.
556
557           Examples:
558
559
560               $ zypper si -d dbus-1
561                   Install build dependencies of dbus-1 source package.
562
563       verify (ve) [options]
564           Check  whether  dependencies of installed packages are satisfied. +
565           In case that any dependency problems  are  found,  zypper  suggests
566           packages to install or remove to fix them.
567
568           -D, --dry-run
569               Test the repair, do not actually do anything to the system.
570
571           --details
572               Show the detailed installation summary.
573
574           -r, --repo alias|name|#|URI
575               Work  only  with  the  repository specified by the alias, name,
576               number, or URI. This option can be used multiple times.
577
578           -y, --no-confirm
579               Don’t require user interaction. Alias for the --non-interactive
580               global option.
581
582           Solver related options:
583
584
585           --debug-solver
586               Create  solver test case for debugging. Use this option, if you
587               think the dependencies were not solved all right and attach the
588               resulting  /var/log/zypper.solverTestCase directory to your bug
589               report. To use this option, simply add it  to  the  problematic
590               install or remove command.
591
592           --force-resolution
593               Force  the  solver  to  find  a  solution by allowing to remove
594               packages with unfulfilled requirements.  This  is  the  default
595               when  removing  packages (zypper remove). This option overrides
596               --no-force-resolution in case both are specified on the command
597               line.
598
599           -R, --no-force-resolution
600               Do  not  force  the  solver to find a solution. Instead, report
601               dependency  problems  and  prompt  the  user  to  resolve  them
602               manually.  This  is  the  default except when removing packages
603               (zypper remove).
604
605           --recommends
606               Install also recommended packages in addition to  the  required
607               ones.     The     default    behavior    is    determined    by
608               [zypp.conf:solver.onlyRequires].
609
610           --no-recommends
611               Do not install recommended packages, but  only  required  ones.
612               The       default      behavior      is      determined      by
613               [zypp.conf:solver.onlyRequires].
614
615           Expert Options:
616               Don’t use them unless you know you need them.
617
618           --[no-]allow-downgrade
619               Whether to allow downgrading installed resolvables.
620
621           --[no-]allow-name-change
622               Whether to allow changing the names of  installed  resolvables.
623               Setting  this  to  no will not replace packages which have been
624               renamed.
625
626           --[no-]allow-arch-change
627               Whether  to  allow  changing  the  architecture  of   installed
628               resolvables.
629
630           --[no-]allow-vendor-change
631               Whether  to allow changing the vendor of installed resolvables.
632               Setting this to no might be useful if you do not want  packages
633               from  foreign  repos being changed to the distributions version
634               (or vice versa).
635
636           This command also accepts  the  Download-and-install  mode  options
637           described in the install command.
638
639
640       install-new-recommends (inr) [options]
641           Install newly added packages recommended by already installed ones.
642           This command basically  re-evaluates  the  recommendations  of  all
643           installed  packages  and fills up the system accordingly. You don’t
644           want to call this unconditionally on small or minimal  systems,  as
645           it  may  easily  add a large number of packages. + Called as zypper
646           inr --no-recommends, it restricts the  command  to  just  look  for
647           packages  supporting  available hardware, languages or filesystems.
648           Usefull after having added e.g. new hardware or driver repos.  This
649           is    also    the    default    behavior    if    you    have   set
650           [zypp.conf:solver.onlyRequires].
651
652           -r, --repo alias|name|#|URI
653               Work only with the repository specified  by  the  alias,  name,
654               number, or URI. This option can be used multiple times.
655
656           -D, --dry-run
657               Test the installation, do not actually install anything.
658
659           --details
660               Show the detailed installation summary.
661
662           Solver related options:
663
664
665           --debug-solver
666               Create  solver test case for debugging. Use this option, if you
667               think the dependencies were not solved all right and attach the
668               resulting  /var/log/zypper.solverTestCase directory to your bug
669               report. To use this option, simply add it  to  the  problematic
670               install or remove command.
671
672           --force-resolution
673               Force  the  solver  to  find  a  solution by allowing to remove
674               packages with unfulfilled requirements.  This  is  the  default
675               when  removing  packages (zypper remove). This option overrides
676               --no-force-resolution in case both are specified on the command
677               line.
678
679           -R, --no-force-resolution
680               Do  not  force  the  solver to find a solution. Instead, report
681               dependency  problems  and  prompt  the  user  to  resolve  them
682               manually.  This  is  the  default except when removing packages
683               (zypper remove).
684
685           --recommends
686               Install also recommended packages in addition to  the  required
687               ones.     The     default    behavior    is    determined    by
688               [zypp.conf:solver.onlyRequires].
689
690           --no-recommends
691               Do not install recommended packages, but  only  required  ones.
692               The       default      behavior      is      determined      by
693               [zypp.conf:solver.onlyRequires].
694
695           Expert Options:
696               Don’t use them unless you know you need them.
697
698           --[no-]allow-downgrade
699               Whether to allow downgrading installed resolvables.
700
701           --[no-]allow-name-change
702               Whether to allow changing the names of  installed  resolvables.
703               Setting  this  to  no will not replace packages which have been
704               renamed.
705
706           --[no-]allow-arch-change
707               Whether  to  allow  changing  the  architecture  of   installed
708               resolvables.
709
710           --[no-]allow-vendor-change
711               Whether  to allow changing the vendor of installed resolvables.
712               Setting this to no might be useful if you do not want  packages
713               from  foreign  repos being changed to the distributions version
714               (or vice versa).
715
716           This command also accepts  the  Download-and-install  mode  options
717           described in the install command.
718
719
720       remove (rm) [options] name...
721
722
723       remove (rm) [options] --capability capability...
724           Remove  (uninstall)  packages.  + The remove command will uninstall
725           the selected and their dependent  packages.  It  will  not  try  to
726           install alternatives in order to keep dependent packages installed.
727           If you want this, use zypper install !name. + The packages  can  be
728           selected by their name or by a capability they provide. For details
729           on package selection see the install command description.
730
731           -r, --repo alias|name|#|URI
732               Work only with the repository specified  by  the  alias,  name,
733               number, or URI. This option can be used multiple times.
734
735           -t, --type type
736               Type  of  package (default: package). See section Package Types
737               for list of available package types. + Since  patches  are  not
738               installed  in  sense  of  copying files or recording a database
739               entry, they cannot be uninstalled,  even  though  zypper  shows
740               them  as  installed.  The installed status is determined solely
741               based on the installed status of its required dependencies.  If
742               these   dependencies  are  satisfied,  the  patch  is  rendered
743               installed.
744
745           -n, --name
746               Select packages by their name (default).
747
748           -C, --capability
749               Select packages by capabilities.
750
751           -D, --dry-run
752               Test the removal of packages, do not actually remove  anything.
753               This  option will add the --test option to the rpm commands run
754               by the remove command.
755
756           --details
757               Show the detailed installation summary.
758
759           -y, --no-confirm
760               Don’t require user interaction. Alias for the --non-interactive
761               global option.
762
763           Solver related options:
764
765
766           --debug-solver
767               Create  solver test case for debugging. Use this option, if you
768               think the dependencies were not solved all right and attach the
769               resulting  /var/log/zypper.solverTestCase directory to your bug
770               report. To use this option, simply add it  to  the  problematic
771               install or remove command.
772
773           --force-resolution
774               Force  the  solver  to  find  a  solution by allowing to remove
775               packages with unfulfilled requirements.  This  is  the  default
776               when  removing  packages (zypper remove). This option overrides
777               --no-force-resolution in case both are specified on the command
778               line.
779
780           -R, --no-force-resolution
781               Do  not  force  the  solver to find a solution. Instead, report
782               dependency  problems  and  prompt  the  user  to  resolve  them
783               manually.  This  is  the  default except when removing packages
784               (zypper remove).
785
786           -u, --clean-deps
787               Automatically remove dependencies which become  unneeded  after
788               removal of requested packages.
789
790           -U, --no-clean-deps
791               No automatic removal of unneeded dependencies.
792
793   Update Management Commands
794       list-updates (lu) [options]
795           List  available  updates. + This command will list only installable
796           updates, i.e. updates which have no dependency problems,  or  which
797           do  not change package vendor. This list is what the update command
798           will propose to install. To  list  all  packages  for  which  newer
799           version are available, use --all option.
800
801           -t, --type type
802               Type  of  package (default: package). See section Package Types
803               for list of available package types. + If patch  is  specified,
804               zypper acts as if the list-patches command was executed.
805
806           -r, --repo alias|name|#|URI
807               Work  only  with  the  repository specified by the alias, name,
808               number, or URI. This option can be used multiple times.
809
810           -a, --all
811               List all packages  for  which  newer  versions  are  available,
812               regardless whether they are installable or not.
813
814           --best-effort
815               See the update command for description.
816
817       update (up) [options] [packagename]...
818           Update  installed  packages  with newer versions, where possible. +
819           This command will not update packages which would require change of
820           package    vendor    unless    the    vendor    is   specified   in
821           /etc/zypp/vendors.d, or which would require  manual  resolution  of
822           problems  with dependencies. Such non-installable updates will then
823           be listed in separate section of  the  summary  as  "The  following
824           package  updates  will  NOT  be installed:". + To update individual
825           packages, specify one or more package names. You can use the *  and
826           ?  wildcard  characters  in  the  package names to specify multiple
827           packages matching the pattern.
828
829           -t, --type type
830               Type of package (default: package). See section  Package  Types
831               for  list  of available package types. + If patch is specified,
832               zypper acts as if the patches command was executed.
833
834           -r, --repo alias|name|#|URI
835               Work only with the repository specified  by  the  alias,  name,
836               number, or URI. This option can be used multiple times.
837
838           --skip-interactive
839               This  will  skip  interactive patches, that is, those that need
840               reboot, contain a message, or update a  package  whose  license
841               needs to be confirmed.
842
843           --with-interactive
844               Avoid  skipping  of interactive patches when in non-interactive
845               mode.
846
847           -l, --auto-agree-with-licenses
848               Automatically say  yes  to  third  party  license  confirmation
849               prompt. By using this option, you choose to agree with licenses
850               of all third-party software this  command  will  install.  This
851               option is particularly useful for administrators installing the
852               same set of packages on  multiple  machines  (by  an  automated
853               process) and have the licenses confirmed before.
854
855           --auto-agree-with-product-licenses
856               Automatically  accept  product  licenses  only. This is used by
857               tools like SUSEconnect, which ask for confirmation  before  the
858               product  gets  registered.  So  there’s  no need to confirm the
859               product license again at install time.
860
861           --replacefiles
862               Install the packages even if they  replace  files  from  other,
863               already installed, packages. Default is to treat file conflicts
864               as an error.  --download-as-needed  disables  the  fileconflict
865               check  because  access  to  all packages filelists is needed in
866               advance in order to perform the check.
867
868           -D, --dry-run
869               Test the update, do not actually install or update any package.
870               This  option will add the --test option to the rpm commands run
871               by the update command.
872
873           --details
874               Show the detailed installation summary.
875
876           --best-effort
877               Do a best effort approach  to  update.  This  method  does  not
878               explicitly  select packages with best version and architecture,
879               but instead requests installation  of  a  package  with  higher
880               version  than  the  installed  one  and  leaves the rest on the
881               dependency solver. This method is always used for packages, and
882               is  optional for products and patterns. It is not applicable to
883               patches.
884
885           -y, --no-confirm
886               Don’t require user interaction. Alias for the --non-interactive
887               global option.
888
889           Solver related options:
890
891
892           --debug-solver
893               Create  solver test case for debugging. Use this option, if you
894               think the dependencies were not solved all right and attach the
895               resulting  /var/log/zypper.solverTestCase directory to your bug
896               report. To use this option, simply add it  to  the  problematic
897               install or remove command.
898
899           --force-resolution
900               Force  the  solver  to  find  a  solution by allowing to remove
901               packages with unfulfilled requirements.  This  is  the  default
902               when  removing  packages (zypper remove). This option overrides
903               --no-force-resolution in case both are specified on the command
904               line.
905
906           -R, --no-force-resolution
907               Do  not  force  the  solver to find a solution. Instead, report
908               dependency  problems  and  prompt  the  user  to  resolve  them
909               manually.  This  is  the  default except when removing packages
910               (zypper remove).
911
912           --recommends
913               Install also recommended packages in addition to  the  required
914               ones.     The     default    behavior    is    determined    by
915               [zypp.conf:solver.onlyRequires].
916
917           --no-recommends
918               Do not install recommended packages, but  only  required  ones.
919               The       default      behavior      is      determined      by
920               [zypp.conf:solver.onlyRequires].
921
922           Expert Options:
923               Don’t use them unless you know you need them.
924
925           --[no-]allow-downgrade
926               Whether to allow downgrading installed resolvables.
927
928           --[no-]allow-name-change
929               Whether to allow changing the names of  installed  resolvables.
930               Setting  this  to  no will not replace packages which have been
931               renamed.
932
933           --[no-]allow-arch-change
934               Whether  to  allow  changing  the  architecture  of   installed
935               resolvables.
936
937           --[no-]allow-vendor-change
938               Whether  to allow changing the vendor of installed resolvables.
939               Setting this to no might be useful if you do not want  packages
940               from  foreign  repos being changed to the distributions version
941               (or vice versa).
942
943           This command also accepts  the  Download-and-install  mode  options
944           described in the install command description.
945
946
947       list-patches (lp) [options]
948           List  all  applicable  patches. + This command is similar to zypper
949           list-updates -t patch. + Note that optional arguments  of  some  of
950           the following options must be specified using = instead of a space.
951
952           -b, --bugzilla[='#[,...']]
953               List  applicable  patches  for  all  Bugzilla issues, or issues
954               whose number matches the given string.
955
956           --cve[='#[,...']]
957               List applicable patches for all CVE  issues,  or  issues  whose
958               number matches the given string.
959
960           --date YYYY-MM-DD[,...]
961               List  only  patches  issued  up  to,  but  not  including,  the
962               specified date.
963
964           -g, --category category[,...]
965               List only patches with this category. See section Package Types
966               for a list of commonly used category values.
967
968           --severity severity[,...]
969               List only patches with this severity. See section Package Types
970               for a list of commonly used severity values.
971
972           --issues[=’string'[,...]]
973               Look for issues whose number, summary, or  description  matches
974               the  specified  string.  Issues  found  by number are displayed
975               separately from those found  by  descriptions.  In  the  latter
976               case,  use zypper patch-info patchname to get information about
977               issues the patch fixes.
978
979           -a, *--all
980               By default, only patches that are applicable on your system are
981               listed. This option causes all available released patches to be
982               listed. This option can be combined with all the  rest  of  the
983               list-updates command options.
984
985           --with[out]-optional
986               Whether applicable optional patches should be treated as needed
987               or be excluded. The default is to exclude optional patches.
988
989           -r, --repo alias|name|#|URI
990               Work only with the repository specified  by  the  alias,  name,
991               number, or URI. This option can be used multiple times.
992
993       patch-check (pchk)
994           Check  for  patches. Displays a count of applicable patches and how
995           many of them have the security category. + See also the EXIT  CODES
996           section  for  details on exit status of 0, 100, and 101 returned by
997           this command.
998
999           --updatestack-only
1000               Check only for patches  which  affect  the  package  management
1001               itself.
1002
1003           --with[out]-optional
1004               Whether applicable optional patches should be treated as needed
1005               or be excluded. The default is to exclude optional patches.
1006
1007           -r, --repo alias|name|#|URI
1008               Check for patches only  in  the  repository  specified  by  the
1009               alias,  name,  number, or URI. This option can be used multiple
1010               times.
1011
1012       patch [options]
1013           Install all available needed patches. + If there are  patches  that
1014           affect the package management itself, those will be installed first
1015           and you will be asked to  run  the  patch  command  again.  +  This
1016           command is similar to zypper update -t patch.
1017
1018           --updatestack-only
1019               Install only patches which affect the package management itself
1020               and exit.
1021
1022           --with-update
1023               Additionally try to update all packages not covered by patches.
1024               This is basically the same as running zypper update afterwards.
1025               + The option is ignored, if the patch command must  update  the
1026               update  stack  first,  thus  it  can  not  be combined with the
1027               --updatestack-only option.
1028
1029           --with[out]-optional
1030               Whether applicable optional patches should be treated as needed
1031               or be excluded. The default is to exclude optional patches.
1032
1033           -b, --bugzilla #[,...]
1034               Install  patch fixing a Bugzilla issue specified by number. Use
1035               list-patches --bugzilla command to get  a  list  of  applicable
1036               patches for specific issues.
1037
1038           --cve #[,...]
1039               Install  patch  fixing a MITRE’s CVE issue specified by number.
1040               Use list-patches --cve command to  get  a  list  of  applicable
1041               patches for specific issues.
1042
1043           --date YYYY-MM-DD[,...]
1044               Install  only  patches  issued  up  to,  but not including, the
1045               specified date.
1046
1047           -g, --category category[,...]
1048               Install only  patches  with  this  category.  Use  list-patches
1049               --category  command  to  get a list of available patches with a
1050               specific category. See section Package  Types  for  a  list  of
1051               commonly used category values.
1052
1053           --severity severity[,...]
1054               Install  only  patches  with  this  severity.  Use list-patches
1055               --severity command to get a list of available  patches  with  a
1056               specific  severity.  See  section  Package  Types for a list of
1057               commonly used severity values.
1058
1059           -r, --repo alias|name|#|URI
1060               Work only with the repository specified  by  the  alias,  name,
1061               number, or URI. This option can be used multiple times.
1062
1063           --skip-interactive
1064               This  will  skip  interactive patches, that is, those that need
1065               reboot, contain a message, or update a  package  whose  license
1066               needs to be confirmed.
1067
1068           --with-interactive
1069               Avoid  skipping  of interactive patches when in non-interactive
1070               mode.
1071
1072           -l, --auto-agree-with-licenses
1073               Automatically say  yes  to  third  party  license  confirmation
1074               prompt. By using this option, you choose to agree with licenses
1075               of all third-party software this  command  will  install.  This
1076               option is particularly useful for administrators installing the
1077               same set of packages on  multiple  machines  (by  an  automated
1078               process) and have the licenses confirmed before.
1079
1080           --auto-agree-with-product-licenses
1081               Automatically  accept  product  licenses  only. This is used by
1082               tools like SUSEconnect, which ask for confirmation  before  the
1083               product  gets  registered.  So  there’s  no need to confirm the
1084               product license again at install time.
1085
1086           --replacefiles
1087               Install the packages even if they  replace  files  from  other,
1088               already installed, packages. Default is to treat file conflicts
1089               as an error.  --download-as-needed  disables  the  fileconflict
1090               check  because  access  to  all packages filelists is needed in
1091               advance in order to perform the check.
1092
1093           -D, --dry-run
1094               Test the update, do not actually update.
1095
1096           --details
1097               Show the detailed installation summary.
1098
1099           -y, --no-confirm
1100               Don’t require user interaction. Alias for the --non-interactive
1101               global option.
1102
1103           Solver related options:
1104
1105
1106           --debug-solver
1107               Create  solver test case for debugging. Use this option, if you
1108               think the dependencies were not solved all right and attach the
1109               resulting  /var/log/zypper.solverTestCase directory to your bug
1110               report. To use this option, simply add it  to  the  problematic
1111               install or remove command.
1112
1113           --force-resolution
1114               Force  the  solver  to  find  a  solution by allowing to remove
1115               packages with unfulfilled requirements.  This  is  the  default
1116               when  removing  packages (zypper remove). This option overrides
1117               --no-force-resolution in case both are specified on the command
1118               line.
1119
1120           -R, --no-force-resolution
1121               Do  not  force  the  solver to find a solution. Instead, report
1122               dependency  problems  and  prompt  the  user  to  resolve  them
1123               manually.  This  is  the  default except when removing packages
1124               (zypper remove).
1125
1126           --recommends
1127               Install also recommended packages in addition to  the  required
1128               ones.     The     default    behavior    is    determined    by
1129               [zypp.conf:solver.onlyRequires].
1130
1131           --no-recommends
1132               Do not install recommended packages, but  only  required  ones.
1133               The       default      behavior      is      determined      by
1134               [zypp.conf:solver.onlyRequires].
1135
1136           Expert Options:
1137               Don’t use them unless you know you need them.
1138
1139           --[no-]allow-downgrade
1140               Whether to allow downgrading installed resolvables.
1141
1142           --[no-]allow-name-change
1143               Whether to allow changing the names of  installed  resolvables.
1144               Setting  this  to  no will not replace packages which have been
1145               renamed.
1146
1147           --[no-]allow-arch-change
1148               Whether  to  allow  changing  the  architecture  of   installed
1149               resolvables.
1150
1151           --[no-]allow-vendor-change
1152               Whether  to allow changing the vendor of installed resolvables.
1153               Setting this to no might be useful if you do not want  packages
1154               from  foreign  repos being changed to the distributions version
1155               (or vice versa).
1156
1157           This command also accepts  the  Download-and-install  mode  options
1158           described in the install command description.
1159
1160
1161       dist-upgrade (dup) [options]
1162           Perform  a  distribution upgrade. This command applies the state of
1163           (specified)  repositories  onto  the  system;  upgrades  (or   even
1164           downgrades)  installed  packages to versions found in repositories,
1165           removes packages that are no longer in the repositories and pose  a
1166           dependency  problem  for  the  upgrade,  handles package splits and
1167           renames, etc. + If no repositories are  specified  via  the  --from
1168           option,   zypper   will  do  a  global  upgrade  with  all  defined
1169           repositories. This global form of dup will also consider  unchanged
1170           installed  packages and re-evaluate their dependencies. This can be
1171           a problem if the system  contains  conflicting  repositories,  like
1172           repositories  for  two  different distribution releases. This often
1173           happens if one forgets to remove an older release repository  after
1174           adding  a  new  one, say openSUSE 13.1 and openSUSE 13.2. + For all
1175           repositories which have the distribution version within  their  URL
1176           (like <https://download.opensuse.org/distribution/
1177           .www:lenstrwww:splitstr:nwww:splitstr:rfI>13.1/repo/oss) using  the
1178           $releasever variable instead may be helpful ( <https://
1179           download.opensuse.org/distribution/
1180           .www:lenstrwww:splitstr:nwww:splitstr:rfB>$releasever/repo/oss).
1181           The  variable  is  per   default   substituted   by   the   current
1182           distributions  version  (13.1)  This value can be overwritten using
1183           the  --releasever  global  option.  Calling   zypper   --releasever
1184           13.2'...' will cause these repos to use the new location (
1185           <https://download.opensuse.org/distribution/
1186           .www:lenstrwww:splitstr:nwww:splitstr:rfI>13.2/repo/oss)    without
1187           need to add/remove anything. Once the dup is performed, $releasever
1188           will   default   to  the  new  distribution  version.  See  section
1189           Repository Management for more info about variable substitution.  +
1190           Note:   distribution   upgrades  in  openSUSE  are  currently  only
1191           supported  between  consecutive  releases.  To   upgrade   multiple
1192           releases,  upgrade each consecutive release one at a time. For more
1193           details  see  <http://en.opensuse.org/SDB:System_upgrade>  and  the
1194           openSUSE release notes at <http://doc.opensuse.org/release-notes/>.
1195
1196           --from alias|name|#|URI
1197               The option can be used multiple times and restricts the upgrade
1198               to the specified repositories only.  Nevertheless  all  enabled
1199               repositories are visible to the resolver and will be considered
1200               to satisfy dependency problems.
1201
1202           -r, --repo alias|name|#|URI
1203               Work only with the repository specified  by  the  alias,  name,
1204               number,  or  URI. + Using --repo is discouraged as it currently
1205               hides unmentioned repositories from the  resolver,  leading  to
1206               inexpertly  decisions.  This  is  because  packages  originally
1207               installed from the hidden repos will now be treated as orphaned
1208               or  dropped.  They  can  be  silently  removed if involved in a
1209               dependency conflict. In the future --repo will become an  alias
1210               for --from.
1211
1212           -l, --auto-agree-with-licenses
1213               Automatically  say  yes  to  third  party  license confirmation
1214               prompt. By using this option, you choose to agree with licenses
1215               of  all  third-party  software  this command will install. This
1216               option is particularly useful for administrators installing the
1217               same  set  of  packages  on  multiple machines (by an automated
1218               process) and have the licenses confirmed before.
1219
1220           --auto-agree-with-product-licenses
1221               Automatically accept product licenses only.  This  is  used  by
1222               tools  like  SUSEconnect, which ask for confirmation before the
1223               product gets registered. So there’s  no  need  to  confirm  the
1224               product license again at install time.
1225
1226           --replacefiles
1227               Install  the  packages  even  if they replace files from other,
1228               already installed, packages. Default is to treat file conflicts
1229               as  an  error.  --download-as-needed  disables the fileconflict
1230               check because access to all packages  filelists  is  needed  in
1231               advance in order to perform the check.
1232
1233           -D, --dry-run
1234               Test  the  upgrade,  do  not  actually  install  or  update any
1235               package. This option will add the  --test  option  to  the  rpm
1236               commands run by the dist-upgrade command.
1237
1238           -y, --no-confirm
1239               Don’t require user interaction. Alias for the --non-interactive
1240               global option.
1241
1242           --details
1243               Show the detailed installation summary.
1244
1245           Solver related options:
1246
1247
1248           --debug-solver
1249               Create solver test case for debugging. Use this option, if  you
1250               think the dependencies were not solved all right and attach the
1251               resulting /var/log/zypper.solverTestCase directory to your  bug
1252               report.  To  use  this option, simply add it to the problematic
1253               install or remove command.
1254
1255           --force-resolution
1256               Force the solver to find  a  solution  by  allowing  to  remove
1257               packages  with  unfulfilled  requirements.  This is the default
1258               when removing packages (zypper remove). This  option  overrides
1259               --no-force-resolution in case both are specified on the command
1260               line.
1261
1262           -R, --no-force-resolution
1263               Do not force the solver to find  a  solution.  Instead,  report
1264               dependency  problems  and  prompt  the  user  to  resolve  them
1265               manually. This is the default  except  when  removing  packages
1266               (zypper remove).
1267
1268           --recommends
1269               Install  also  recommended packages in addition to the required
1270               ones.    The    default    behavior    is     determined     by
1271               [zypp.conf:solver.onlyRequires].
1272
1273           --no-recommends
1274               Do  not  install  recommended packages, but only required ones.
1275               The      default      behavior      is      determined       by
1276               [zypp.conf:solver.onlyRequires].
1277
1278           Expert Options:
1279               Don’t use them unless you know you need them.
1280
1281           --[no-]allow-downgrade
1282               Whether    to    allow    downgrading   installed   resolvables
1283               [zypp.conf:solver.dupAllowDowngrade].
1284
1285           --[no-]allow-name-change
1286               Whether to allow changing the names  of  installed  resolvables
1287               [zypp.conf:solver.dupAllowNameChange].  Setting this to no will
1288               not replace packages which have been renamed.
1289
1290           --[no-]allow-arch-change
1291               Whether  to  allow  changing  the  architecture  of   installed
1292               resolvables [zypp.conf:solver.dupAllowArchChange].
1293
1294           --[no-]allow-vendor-change
1295               Whether  to  allow changing the vendor of installed resolvables
1296               [zypp.conf:solver.dupAllowVendorChange].  Setting  this  to  no
1297               might  be useful if you do not want packages from foreign repos
1298               being dup’ed to the distributions version (or vice versa).
1299
1300           This command also accepts  the  Download-and-install  mode  options
1301           described in the install command description.
1302
1303
1304           Examples:
1305
1306
1307               $ zypper dup --from factory --from packman
1308                   Upgrade  the  system to the latest versions provided by the
1309                   factory and packman repositories.
1310
1311   Query Commands
1312       search (se) [options] [querystring|capability]...
1313           Search for packages matching any of the given search strings. * and
1314           ?  wildcard  characters  can  be used within search strings. If the
1315           search string is enclosed in /  (e.g. /^k.*e$/) it’s interpreted as
1316           a regular expression. See the install command for details about how
1317           to specify a capability. + Results of the search are printed  in  a
1318           table  with  columns S+tatus+, Name, Summary and Type of package. +
1319           In the detailed view (se -s) all available  instances  of  matching
1320           packages  are  shown; each version in each repository on a separate
1321           line, with columns S+tatus+, Name,  Type,  Version,  Arch+itecture+
1322           and  Repository.  For  installed packages Repository shows either a
1323           repository that provides  exactly  the  installed  version  of  the
1324           package,  or,  if  the  exact  version is not provided by any known
1325           repo, (System Packages) (or @System). Those installed packages  not
1326           provided  by any repo are often denoted as being unwanted, orphaned
1327           or dropped. + The S+tatus+ column can contain the following values:
1328
1329           i+
1330               installed by user request
1331
1332           i
1333               installed  automatically  (by   the   resolver,   see   section
1334               Automatically installed packages)
1335
1336           v
1337               a different version is installed
1338
1339           empty
1340               neither of the above cases
1341
1342           .l
1343               is  shown  in the 2nd column if the item is locked (see section
1344               Package Locks Management)
1345
1346
1347                   The v status is only shown if the version or the repository
1348           matters  (see  --details  or  --repo),  and  the installed instance
1349           differs from the one listed in version or repository.
1350                   +
1351                   This command accepts the following options:
1352
1353           --match-substrings
1354               Matches for search strings may be partial words (default).
1355
1356           --match-words
1357               Matches for search strings may only be whole words.
1358
1359           -x, --match-exact
1360               Searches for an exact name of the package.
1361
1362           --provides
1363               Search for packages which provide the search strings.
1364
1365           --requires
1366               Search for packages which require the search strings.
1367
1368           --recommends
1369               Search for packages which recommend the search strings.
1370
1371           --suggests
1372               Search for packages which suggest the search strings.
1373
1374           --conflicts
1375               Search for packages conflicting with the search strings.
1376
1377           --obsoletes
1378               Search for packages which obsolete the search strings.
1379
1380           --supplements
1381               Search for packages which supplement the search strings.
1382
1383           -n, --name
1384               Useful together with dependency options, otherwise searching in
1385               package name is default.
1386
1387           -f, --file-list
1388               Search  in  the  file list of packages. Note that the full file
1389               list is available  for  installed  packages  only.  For  remote
1390               packages  only  an  abstract  of  their  file list is available
1391               within the metadata (files containing /etc/, /bin/, or /sbin/).
1392
1393           -d, --search-descriptions
1394               Search also in summaries and descriptions.
1395
1396           -C, --case-sensitive
1397               Perform case-sensitive search.
1398
1399           -i, --installed-only
1400               Show only installed packages.
1401
1402           -u, --not-installed-only
1403               Show only packages which are not installed. +  The  old  option
1404               name  --uninstalled-only  is  still  acceptable,  but should be
1405               considered deprecated.
1406
1407           -t, --type type
1408               Search only for packages of specified type. See section Package
1409               Types  for  a  list of available package types. Multiple --type
1410               options  are  allowed.  +  See  also  the  type-specific  query
1411               commands like packages, patterns, etc.
1412
1413           -r, --repo alias|name|#|URI
1414               Work  only  with  the  repository specified by the alias, name,
1415               number, or URI. This option can be used multiple times.
1416
1417           --sort-by-name
1418               Sort packages by name (default).
1419
1420           --sort-by-repo
1421               Sort packages by repository, not by name.
1422
1423           -s, --details
1424               Show all available versions of matching packages, each  version
1425               in each repository on a separate line.
1426
1427           -v, --verbose
1428               Like --details with additional information where the search has
1429               matched  (useful  when   searching   for   dependencies,   e.g.
1430               --provides).
1431
1432           Examples:
1433
1434
1435               $ zypper se 'yast*'
1436                   Search  for  YaST packages (quote the string to prevent the
1437                   shell from expanding the wildcard).
1438
1439               $ zypper se -s --match-exact kernel-default
1440                   Show all available versions of package kernel-default
1441
1442               $ zypper se -dC --match-words RSI
1443                   Look for RSI acronym (case-sensitively), also in  summaries
1444                   and descriptions.
1445
1446       packages (pa) [options] [repository]...
1447           List   all  available  packages  or  all  packages  from  specified
1448           repositories. Similar to zypper search -s -t package.
1449
1450           -r, --repo alias|name|#|URI
1451               Just another means to specify repositories.
1452
1453           -i, --installed-only
1454               Show only installed packages.
1455
1456           -u, --not-installed-only
1457               Show only packages which are not installed. +  The  old  option
1458               name  --uninstalled-only  is  still  acceptable,  but should be
1459               considered deprecated.
1460
1461           --orphaned
1462               Show packages which are orphaned (without repository).
1463
1464           --suggested
1465               Show packages which are suggested.
1466
1467           --recommended
1468               Show packages which are recommended.
1469
1470           --unneeded
1471               Show packages which are unneeded.
1472
1473       patches (pch) [options] [repository]...
1474           List all available patches from specified  repositories,  including
1475           those not needed. Short for zypper lp -a.
1476
1477           -r, --repo alias|name'|#|URI
1478               Just another means to specify repositories.
1479
1480       patterns (pt) [options] [repository]...
1481           List   all  available  patterns  or  all  patterns  from  specified
1482           repositories. Similar to zypper search -s -t pattern.
1483
1484           -r, --repo alias|name|#|URI
1485               Just another means to specify repositories.
1486
1487           -i, --installed-only
1488               Show only installed patterns.
1489
1490           -u, --not-installed-only
1491               Show only patterns which are not installed. +  The  old  option
1492               name  --uninstalled-only  is  still  acceptable,  but should be
1493               considered deprecated.
1494
1495       products (pd) [options] [repository]...
1496           List  all  available  products  or  all  products  from   specified
1497           repositories.  Similar  to  zypper  search -s -t product, but shows
1498           also the type of the product (base, add-on).
1499
1500           -r, --repo 'alias|name|#|URI
1501               Just another means to specify repositories.
1502
1503           -i, --installed-only
1504               Show only installed products.
1505
1506           -u, --not-installed-only
1507               Show only products which are not installed. +  The  old  option
1508               name  --uninstalled-only  is  still  acceptable,  but should be
1509               considered deprecated.
1510
1511           --xmlfwd tag
1512               XML output only: Literally forward the XML tag, if it is  found
1513               in  an  installed  products  .prod-file (in /etc/products.d). +
1514               Using this option, for each installed product an <xmlfwd>  node
1515               will  be  created  inside  the  <product>  output  node  of the
1516               product. + Tag defines the name  (or  /-separated  path)  of  a
1517               xml-tag  inside an installed products .prod-file. If the tag is
1518               present inside  the  products  .prod-file,  the  tag  and  it’s
1519               content  is  literally  forwarded  into  the  products <xmlfwd>
1520               output node. + The option may be specified multiple times.
1521
1522           Examples:
1523
1524
1525               $ zypper -x pd --xmlfwd name --xmlfwd register/target
1526
1527
1528       what-provides (wp) capability
1529           List all packages providing the specified capability. See also  the
1530           install command for info about specifying capabilities.
1531
1532           The  command line is automatically transformed into the appropriate
1533           search command, e.g.:
1534
1535
1536               $ zypper what-provides 'zypper>1.6'
1537
1538
1539               $ zypper se --provides --match-exact 'zypper>1.6'
1540
1541
1542   Repository Management
1543       Zypper is able to work with YaST, RPM-MD (yum)  software  repositories,
1544       and plain directories containing .rpm files.
1545
1546       Repositories  are  primarily identified using their URI or alias. Alias
1547       serves as a shorthand for the long URI or name of the  repository.  The
1548       name  of  the  repository should briefly describe the repository and is
1549       shown to the user in tables and messages. The name is not required, and
1550       if  not  known,  the  alias is shown instead. The alias is required and
1551       uniquely identifies the repository on the system.
1552
1553       The alias, name, URI, or the number from zypper repos list can be  used
1554       to  specify  a repository as an argument of various zypper commands and
1555       options like refresh, --repo, or --from.
1556
1557       Apart from the above, repositories have several other properties  which
1558       can  be  set  using the commands described in this section below, or by
1559       manually editing the repository  definition  files  (.repo  files,  see
1560       section FILES).
1561
1562   Variable substitution:
1563       You  can  use  the following variables within a .repo or .service files
1564       name and URI values:
1565
1566       $arch
1567           Use this variable to refer to the system’s CPU architecture.
1568
1569       $basearch
1570           Use this variable to refer to the base architecture of the  system.
1571           For  example, iX86 machines have a base architecture of i386, while
1572           AMD64 and Intel64 have x86_64.
1573
1574       $releasever, $releasever_major, $releasever_minor
1575           Use this variable to refer to the version of your openSUSE or  SUSE
1576           Linux.  The value is obtained from the /product/version XML-node in
1577           /etc/products.d/baseproduct.  +  This   is   useful   for   related
1578           repositories like packman (<http://ftp.gwdg.de/pub/linux/packman/
1579           suse/$releasever>),  which   shall   always   fit   the   installed
1580           distribution, even after a distribution upgrade. To help performing
1581           a distribution upgrade, the value of $releasever can be overwritten
1582           using  the  --releasever  global  option.  This  way you can easily
1583           switch all  repositories  using  $releasever  to  the  new  version
1584           (provided  the  server  layouts  did  not  change and new repos are
1585           already available). + In addition $releasever_major will be set  to
1586           the  leading  portion  up  to  (but  not  including)  the  1st dot;
1587           $releasever_minor to the trailing portion after  the  1st  dot.  If
1588           there’s  no  dot  in  $releasever, $releasever_major is the same as
1589           $releasever and $releasever_minor is empty.
1590
1591       Custom Variables
1592           A custom repository variable is  defined  by  creating  a  file  in
1593           /etc/zypp/vars.d. The variable name equals the file name. The files
1594           first line (up to but not including the newline character)  defines
1595           the   variables   value.  Valid  variable(file)  names  consist  of
1596           alphanumeric chars and underscore only.
1597
1598       Remember to protect the $ when using these variables on a shell command
1599       line:
1600           zypper ar -f <http://ftp.gwdg.de/pub/linux/packman/suse/
1601           .www:lenstrwww:splitstr:nwww:splitstr:rfB>\$releasever packman
1602
1603       If a variable is followed by an alphanumeric character or underscore it
1604       needs to be enclosed in {}:
1605           zypper ar -f <http://ftp.gwdg.de/pub/linux/packman/suse/
1606           .www:lenstrwww:splitstr:nwww:splitstr:rfB>\${’releasever'}_packman
1607
1608       Bash style definition of default  ${’variable':-’word'}  and  alternate
1609       ${’variable':+’word'} values:
1610           SLE-${’releasever_major'}${’releasever_minor':+-SP-$releasever_minor}
1611
1612       To check where you already use $releasever call:
1613           zypper --releasever @--HERE--@ lr -u
1614
1615       NOTE:
1616           Variable substitution within an URIs authority is limited  to  host
1617           and  port. Bash style definition of default and alternate values is
1618           not supported. No variables can be used in an URIs scheme, user and
1619           password.
1620
1621   Supported URI formats:
1622       scheme: @]host[:’port']] /’path' [?’query'] [#’fragment']
1623           Special  characters  occurring  in  URI  components  (like a @ in a
1624           password) must be %-encoded (%40).
1625
1626       CD or DVD drive
1627           Optionally with devices list for probing.
1628
1629
1630           cd:///
1631
1632
1633           dvd:/subdir'?devices=/dev/sr0,/dev/sr1'
1634
1635           FTP/HTTP/HTTPS directory tree
1636               The ftp URL scheme supports absolute and relative paths to  the
1637               default  ftp  server directory (RFC1738, Section 3.2.2). To use
1638               an absolute  path,  you  have  to  prepend  the  path  with  an
1639               additional  slash, what results in a /%2f combination (second /
1640               encoded to  %2f)  at  the  begin  of  the  URL  path.  This  is
1641               important,  especially  in  user  authenticated  ftp, where the
1642               users home is usually  the  default  directory  of  the  server
1643               (except when the server chroots into the users home directory).
1644               + Explicit proxy settings may be passed via optional parameters
1645               proxy,    proxyport,    proxyuser   and   proxypass.   +   HTTP
1646               authentication methods to use can be defined as comma separated
1647               list via optional parameter auth. Valid methods are e.g. basic,
1648               digest, ntlm, negotiate. Note, that this list  depends  on  the
1649               list   of   methods  supported  by  the  curl  library.  +  SSL
1650               verification behavior  can  be  changed  using  the  ssl_verify
1651               option  (this  should  be used with care). Valid values are yes
1652               (the secure default), host, peer or no. Host just  checks  that
1653               the  "Common Name" field or a "Subject Alternate Name" field in
1654               the servers certificate matches the host name in the URL.  Peer
1655               just verifies whether the certificate provided by the server is
1656               authentic against the chain  of  digital  signatures  found  in
1657               ssl_capath.  No  performs  no  checks at all. Yes is the secure
1658               default, performing host and  peer  check.  +  For  SSL  client
1659               certificate  authentication  use  the options ssl_clientcert to
1660               define the path to the ssl client certificate and ssl_clientkey
1661               to  define  the  path  to the SSL client key. Use ssl_capath to
1662               change the directory holding the CA  certificates  (default  is
1663               /etc/ssl/certs).
1664
1665
1666           <ftp://user:pass@server/path/to/media/dir>
1667
1668
1669           <ftp://user:pass@server/%2fhome/user/path/to/media/dir>
1670
1671
1672           <http://user:pass@server/path>
1673
1674
1675           <https://
1676           user:pass@server/path>'?proxy=foo&amp;proxyuser=me&amp;proxypass=pw'
1677
1678
1679           <https://
1680           server/path>'?ssl_clientcert=/entitlement/1234.pem&amp;ssl_clientkey=/entitlement/1234-key.pem'
1681
1682           Disk volume (partition)
1683               Mandatory  device  parameter  specifying  the name of the block
1684               device to mount. The name of the optional  filesystem  defaults
1685               to "auto".
1686
1687
1688           hd:/subdir?device=/dev/sda1'&amp;filesystem=reiserfs'
1689
1690           Local directory tree
1691
1692
1693           dir:/directory/name
1694
1695           Media in an ISO image (loopback mounted)
1696               +  Mandatory iso parameter specifying the name of the iso file.
1697               Optional url parameter specifying  the  URL  to  the  directory
1698               containing  the iso file. Optional mnt parameter specifying the
1699               preferred attach point  for  the  source  media  url.  Optional
1700               filesystem  name  of  the  filesystem  used  in  the  iso file.
1701               Defaults to "auto".
1702
1703
1704           iso:/?iso=CD1.iso'&amp;url=nfs://server/path/to/media'
1705
1706
1707           iso:/?iso=CD1.iso'&amp;url=hd:/?device=/dev/hda'
1708
1709
1710           iso:/subdir?iso=DVD1.iso'&amp;url=nfs://nfs-server/directory&amp;mnt=/nfs/attach/point&amp;filesystem=udf'
1711
1712           NFS exported directory tree
1713               To  use  NFSv4  either use schema tnfsv4:// or pass an optional
1714               parameter type=nfs4. Additional mountoptions can be  passed  as
1715               comma separated list. Defaults to "ro".
1716
1717
1718           nfs://nfs-server/exported/path
1719
1720
1721           nfs://nfs-server/exported/path'?mountoptions=ro&amp;type=nfs4'
1722
1723
1724           nfs4://nfs-server/exported/path'?mountoptions=ro'
1725
1726           CIFS/SMB directory tree
1727               There  is no difference between cifs and smb scheme (any more).
1728               In  both  cases  the  cifs  filesystem  is   used.   Additional
1729               mountoptions can be passed as comma separated list. Defaults to
1730               "ro,guest". Specify "noguest" to  turn  off  "guest".  This  is
1731               necessary if Samba is configured to reject guest connections. +
1732               Optional workgroup or domain parameter  set  the  name  of  the
1733               workgroup.  As  alternative to passing username:password in the
1734               URI authority the parameters user and pass can be used.
1735
1736
1737           smb://servername/share/path/on/the/share
1738
1739
1740           cifs://usern:passw@servername/share/path/on/the/share'?mountoptions=ro,noguest'
1741
1742
1743           cifs://usern:passw@servername/share/path/on/the/share'?workgroup=mygroup'
1744
1745
1746           cifs://servername/share/path/on/the/share'?user=usern&amp;pass=passw'
1747
1748           OpenSUSE Build Build Service (OBS) repositories
1749               Zypper  also  accepts  special  URIs identifying openSUSE Build
1750               Service (OBS) repositories in the addrepo command.  These  URIs
1751               have  the  form of obs://’project'/[platform], where project is
1752               the name of the OBS project and platform is the target platform
1753               (OS)  for  which  the  repository is intended. + If platform is
1754               omitted,  openSUSE_$releasever  is  used  unless  a  value  for
1755               obs.platform  is  defined  in zypper.conf. If you are following
1756               openSUSE_Factory or openSUSE_Tumbleweed you  may  need  to  set
1757               these  as your default platform. But we can only guess, how the
1758               directory containing the repository that fits your distribution
1759               is  named  on  the server. In case of doubt you need to look up
1760               the right URL in a browser.
1761
1762
1763           obs://zypp:Head/
1764
1765
1766           obs://zypp:Head/openSUSE_Factory
1767
1768
1769           obs://zypp:Head/openSUSE_Factory_Staging_Gcc49_standard
1770
1771                {nop}
1772               ~~~~~~
1773
1774           addrepo (ar) [options] URI alias
1775
1776
1777           addrepo (ar) [options] FILE.repo
1778               Add a new repository specified  by  URI  and  assign  specified
1779               alias  to  it  or  specify  URI  to a .repo file. + Newly added
1780               repositories have auto-refresh disabled by default (except  for
1781               repositories  imported  from  a  .repo, having the auto-refresh
1782               enabled).  To  enable  auto-refresh  use  addrepo  -f,  or  the
1783               --refresh  option  of  the  modifyrepo  command.  +  Also, this
1784               command  does  not  automatically  refresh  the   newly   added
1785               repositories. The repositories will get refreshed when used for
1786               the first time, or  you  can  use  the  refresh  command  after
1787               finishing your modifications with *repo commands.
1788
1789               -r, --repo file.repo
1790                   Read URI and alias from specified .repo file
1791
1792               -c, --check
1793                   Probe given URI.
1794
1795               -C, --no-check
1796                   Don’t probe URI, probe later during refresh.
1797
1798               -n, --name name
1799                   Specify descriptive name for the repository.
1800
1801               -e, --enable
1802                   Enable the repository (the default).
1803
1804               -d, --disable
1805                   Add  the  repository as disabled. Repositories are added as
1806                   enabled by default.
1807
1808               -f, --refresh
1809                   Enable autorefresh of the repository.  The  autorefresh  is
1810                   disabled by default when adding new repositories.
1811
1812               -F, --no-refresh
1813                   Disable auto-refresh for the repository.
1814
1815               -p, --priority positive-integer
1816                   Set  the  priority  of the repository. Priority of 1 is the
1817                   highest, the higher the number the lower the priority. -p 0
1818                   will  set  the  priority back to the default (99). Packages
1819                   from repositories with higher priority  will  be  preferred
1820                   even   in  case  there  is  a  higher  installable  version
1821                   available in the repository with a lower priority.
1822
1823               -k, --keep-packages
1824                   Enable RPM files caching for the repository.
1825
1826               -K, --no-keep-packages
1827                   Disable RPM files caching.
1828
1829               -g, --gpgcheck
1830                   Enable GPG check  for  this  repository.  The  behavior  as
1831                   described in section GPG checks.
1832
1833               --gpgcheck-strict
1834                   Enable  strict GPG check for this repository. Even packages
1835                   from signed repositories need a  valid  GPG  signature  and
1836                   using unsigned packages must be confirmed.
1837
1838               --gpgcheck-allow-unsigned
1839                   Short      hand      for     --gpgcheck-allow-unsigned-repo
1840                   --gpgcheck-allow-unsigned-package
1841
1842               --gpgcheck-allow-unsigned-repo
1843                   Enable GPG check but allow the repository  metadata  to  be
1844                   unsigned.
1845
1846               --gpgcheck-allow-unsigned-package
1847                   Enable  GPG  check  but  allow installing unsigned packages
1848                   from this repository.
1849
1850               -G, --no-gpgcheck
1851                   Disable GPG check for  this  repository.  +  Disabling  GPG
1852                   checks   is  not  recommended.  Signing  data  enables  the
1853                   recipient to verify that no  modifications  occurred  after
1854                   the  data  were  signed.  Accepting  data with no, wrong or
1855                   unknown signature can lead to a  corrupted  system  and  in
1856                   extreme cases even to a system compromise.
1857
1858               --default-gpgcheck
1859                   Use    the   global   GPG   check   settings   defined   in
1860                   /etc/zypp/zypp.conf. This is the default. + Unless you have
1861                   modified  your  zypp.conf  settings,  this  is  the same as
1862                   --gpgcheck,  the  behavior  as  described  in  section  GPG
1863                   checks.
1864
1865               Examples:
1866
1867
1868                   $ zypper ar -c -n 'Packman 11.1 repo' <http://
1869                   packman.iu-bremen.de/suse/11.1> packman
1870                       Add a HTTP repository, probe it, name it  Packman  11.1
1871                       repo, and use packman as alias.
1872
1873                   $ zypper ar <https://download.opensuse.org/repositories/
1874                   zypp:/svn/openSUSE_Factory/zypp:svn.repo>
1875
1876
1877                   $ zypper ar myreposbackup.repo
1878                       Add repositories from a .repo file.
1879
1880           removerepo (rr) [options] alias|name|#|URI...
1881               Delete repositories specified by aliases, names, numbers,  URIs
1882               or one of the aggregate options.
1883
1884               --loose-auth
1885                   Ignore user authentication data in the URI
1886
1887               --loose-query
1888                   Ignore query string in the URI
1889
1890               -a, --all
1891                   Apply changes to all repositories.
1892
1893               -l, --local
1894                   Apply changes to all local repositories.
1895
1896               -t, --remote
1897                   Apply changes to all remote repositories (http/https/ftp).
1898
1899               -m, --medium-type type
1900                   Apply  changes  to repositories of specified type. The type
1901                   corresponds to the repository URI  scheme  identifier  like
1902                   http,  dvd,  etc. You can find complete list of valid types
1903                   at <http://en.opensuse.org/openSUSE:Libzypp_URIs>.
1904
1905           repos (lr) [options] [repo]...
1906               List all defined  repositories  or  show  detailed  information
1907               about  those specified as arguments + The following data can be
1908               printed for each repository found on the system: #  (repository
1909               number),  Alias (unique identifier), Name, Enabled (whether the
1910               repository is  enabled),  GPG  Check  (whether  GPG  check  for
1911               repository  metadata  (r) and/or downloaded rpm packages (p) is
1912               enabled), Refresh (whether  auto-refresh  is  enabled  for  the
1913               repository), Priority, Type (repository meta-data type: rpm-md,
1914               yast2, plaindir). Which of the data is shown is  determined  by
1915               command  line options listed below and the main.repoListColumns
1916               setting from zypper.conf. By default, #, Alias, Name,  Enabled,
1917               GPG Check and Refresh is shown. + Repository number is a unique
1918               identifier of the repository in current set of repositories. If
1919               you add, remove or change a repository, the numbers may change.
1920               Keep that in mind when using the numbers  with  the  repository
1921               handling  commands.  On the other hand, using the alias instead
1922               of the number is always safe. + To  show  detailed  information
1923               about  specific repositories, specify them as arguments, either
1924               by alias, name, number from simple zypper lr, or by  URI;  e.g.
1925               fB zypper lr factory, or zypper lr 2.
1926
1927               -e, --export FILE.repo|-
1928                   This option causes zypper to write repository definition of
1929                   all defined repositories into a single file  in  repo  file
1930                   format.  If  -  is  specified  instead  of a file name, the
1931                   repositories will be written to the standard output.
1932
1933               -a, --alias
1934                   Add alias column to the output.
1935
1936               -n, --name
1937                   Add name column to the output.
1938
1939               -u, --uri
1940                   Add base URI column to the output.
1941
1942               -p, --priority
1943                   Add repository priority column to the output.
1944
1945               -r, --refresh
1946                   Add the autorefresh column to the output.
1947
1948               -d, --details
1949                   Show more information like URI, priority, type, etc.
1950
1951               -E, --show-enabled-only
1952                   Show enabled repositories only.
1953
1954               -U, --sort-by-uri
1955                   Add base URI column and sort the list it.
1956
1957               -P, --sort-by-priority
1958                   Add repository priority column and sort the list by it.
1959
1960               -A, --sort-by-alias
1961                   Sort the list by alias.
1962
1963               -N, --sort-by-name
1964                   Sort the list by name.
1965
1966               Examples:
1967
1968
1969                   $ zypper repos -e myreposbackup.repo
1970                       Backup your repository setup:
1971
1972                   $ zypper lr -pu
1973                       List repositories with their URIs and priorities:
1974
1975           renamerepo (nr) alias|name|#|URI new-alias
1976               Assign new alias to the repository specified  by  alias,  name,
1977               number, or URI.
1978
1979               Examples:
1980
1981
1982                   $ zypper nr 8 myrepo
1983                       Rename  repository  number  8  to myrepo (useful if the
1984                       repo has some dreadful alias which is not usable on the
1985                       command line).
1986
1987           modifyrepo (mr) options alias|name|#|URI...
1988
1989
1990           modifyrepo (mr) options --all|--remote|--local|--medium-type
1991               Modify  properties  of  repositories  specified by alias, name,
1992               number, or URI or one of the aggregate options.
1993
1994               -n, --name name
1995                   Set a descriptive name for the repository.
1996
1997               -e, --enable
1998                   Enable the repository.
1999
2000               -d, --disable
2001                   Disable the repository.
2002
2003               -f, --refresh (legacy: -r)
2004                   Enable auto-refresh for the repository.
2005
2006               -F, --no-refresh (legacy: -R)
2007                   Disable auto-refresh for the repository.
2008
2009               -p, --priority positive-integer
2010                   Set the priority of the repository. Priority of  1  is  the
2011                   highest, the higher the number the lower the priority. -p 0
2012                   will set the priority back to the  default  (99).  Packages
2013                   from  repositories  with  higher priority will be preferred
2014                   even  in  case  there  is  a  higher  installable   version
2015                   available in the repository with a lower priority.
2016
2017               -k, --keep-packages
2018                   Enable RPM files caching.
2019
2020               -K, --no-keep-packages
2021                   Disable RPM files caching.
2022
2023               -g, --gpgcheck
2024                   Enable  GPG  check  for  this  repository.  The behavior as
2025                   described in section GPG checks.
2026
2027               --gpgcheck-strict
2028                   Enable strict GPG check for this repository. Even  packages
2029                   from  signed  repositories  need  a valid GPG signature and
2030                   using unsigned packages must be confirmed.
2031
2032               --gpgcheck-allow-unsigned
2033                   Short     hand      for      --gpgcheck-allow-unsigned-repo
2034                   --gpgcheck-allow-unsigned-package
2035
2036               --gpgcheck-allow-unsigned-repo
2037                   Enable  GPG  check  but allow the repository metadata to be
2038                   unsigned.
2039
2040               --gpgcheck-allow-unsigned-package
2041                   Enable GPG check but  allow  installing  unsigned  packages
2042                   from this repository.
2043
2044               -G, --no-gpgcheck
2045                   Disable  GPG  check  for  this  repository. + Disabling GPG
2046                   checks  is  not  recommended.  Signing  data  enables   the
2047                   recipient  to  verify  that no modifications occurred after
2048                   the data were signed. Accepting  data  with  no,  wrong  or
2049                   unknown  signature  can  lead  to a corrupted system and in
2050                   extreme cases even to a system compromise.
2051
2052               --default-gpgcheck
2053                   Use   the   global   GPG   check   settings   defined    in
2054                   /etc/zypp/zypp.conf. This is the default. + Unless you have
2055                   modified your zypp.conf  settings,  this  is  the  same  as
2056                   --gpgcheck,  the  behavior  as  described  in  section  GPG
2057                   checks.
2058
2059               -a, --all
2060                   Apply changes to all repositories.
2061
2062               -l, --local
2063                   Apply changes to all local repositories.
2064
2065               -t, --remote
2066                   Apply changes to all remote repositories (http/https/ftp).
2067
2068               -m, --medium-type type
2069                   Apply changes to repositories of specified type.  The  type
2070                   corresponds  to  the  repository URI scheme identifier like
2071                   http, dvd, etc. You can find complete list of  valid  types
2072                   at <http://en.opensuse.org/openSUSE:Libzypp_URIs>.
2073
2074               Examples:
2075
2076
2077                   $ zypper mr -kt
2078                       Enable keeping of packages for all remote repositories.
2079
2080                   $ zypper mr -er updates
2081                       Enable repository updates and switch on autorefresh for
2082                       the repo.
2083
2084                   $ zypper mr -da
2085                       Disable all repositories.
2086
2087           refresh (ref) [alias|name|#|URI]...
2088               Refresh repositories specified by their alias, name, number, or
2089               URI. If no repositories are specified, all enabled repositories
2090               will be refreshed.
2091
2092               -f, --force
2093                   Force a complete refresh of  specified  repositories.  This
2094                   option  will  cause  both  the download of raw metadata and
2095                   parsing of the metadata to be  forced  even  if  everything
2096                   indicates a refresh is not needed.
2097
2098               -b, --force-build
2099                   Force  only  reparsing of cached metadata and rebuilding of
2100                   the database. Raw metadata download will not be forced.
2101
2102               -d, --force-download
2103                   Force only download of current copy of repository metadata.
2104                   Parsing and rebuild of the database will not be forced.
2105
2106               -B, --build-only
2107                   Only  parse  the  metadata  and  build  the database, don’t
2108                   download raw metadata into the cache. This will enable  you
2109                   to   repair  damaged  database  from  cached  data  without
2110                   accessing network at all.
2111
2112               -D, --download-only
2113                   Only download the raw metadata, don’t parse it or build the
2114                   database.
2115
2116               -s, --services
2117                   Refresh also services before refreshing repositories.
2118
2119           clean (cc) [options] [alias|name|#|URI]...
2120               Clean the local caches for all known or specified repositories.
2121               By default, only caches of downloaded packages are cleaned.
2122
2123               -m, --metadata
2124                   Clean repository metadata cache instead of package cache.
2125
2126               -M, --raw-metadata
2127                   Clean repository raw  metadata  cache  instead  of  package
2128                   cache.
2129
2130               -a, --all
2131                   Clean both repository metadata and package caches.
2132
2133   Service Management
2134       The    services,    addservice,   removeservice,   modifyservice,   and
2135       refresh-services commands serve for manipulating services. A service is
2136       specified  by  its  URI and needs to have a unique alias defined (among
2137       both services and repositories).
2138
2139       Standalone repositories (not belonging to any service) are treated like
2140       services,  too.  The  ls command will list them, ms command will modify
2141       them, etc. Repository specific options, like  --keep-packages  are  not
2142       available  here,  though.  You  can use repository handling commands to
2143       manipulate them.
2144
2145       addservice (as) [options] URI alias
2146           Adds a service specified by URI to the system. The  alias  must  be
2147           unique  and  serves to identify the service. + Newly added services
2148           are not refreshed automatically. Use the  refresh-services  command
2149           to refresh them. Zypper does not access the service URI when adding
2150           the service, so the type of the services is  unknown  until  it  is
2151           refreshed. +
2152
2153       -n, --name name
2154           Specify descriptive name for the service.
2155
2156       -e, --enable
2157           Enable the service (this is the default).
2158
2159       -d, --disable
2160           Add the service as disabled.
2161
2162       -f, --refresh
2163           Enable auto-refresh of the service.
2164
2165       -F, --no-refresh
2166           Disable auto-refresh of the service.
2167
2168       removeservice (rs) [options] alias|name|#|URI...
2169           Remove  specified  service from the system. Removing a service will
2170           also remove of all of its repositories.
2171
2172           --loose-auth
2173               Ignore user authentication data in the URI.
2174
2175           --loose-query
2176               Ignore query string in the URI.
2177
2178       modifyservice (ms) options alias|name|#|URI
2179
2180
2181       modifyservice (ms) options --all|--remote|--local|--medium-type
2182           Modify properties of specified services.
2183
2184           Common Options
2185               These  options  are  common  to  all  types  of  services   and
2186               repositories.
2187
2188           -n, --name name
2189               Set a descriptive name for the service.
2190
2191           -e, --enable
2192               Enable a disabled service.
2193
2194           -d, --disable
2195               Disable the service (but don’t remove it).
2196
2197           -f, --refresh  (legacy: -r)
2198               Enable auto-refresh of the service.
2199
2200           -F, --no-refresh  (legacy: -R)
2201               Disable auto-refresh of the service.
2202
2203           -a, --all
2204               Apply changes to all services.
2205
2206           -l, --local
2207               Apply changes to all local services.
2208
2209           -t, --remote
2210               Apply changes to all remote services.
2211
2212           -m, --medium-type type
2213               Apply changes to services of specified type.
2214
2215           RIS Service Specific Options
2216               These  options  are  ignored  by services other than Repository
2217               Index Services.
2218
2219           -i, --ar-to-enable alias
2220               Schedule an RIS  service  repository  to  be  enabled  at  next
2221               service refresh.
2222
2223           -I, --ar-to-disable alias
2224               Schedule  an  RIS  service  repository  to  be disabled at next
2225               service refresh.
2226
2227           -j, --rr-to-enable alias
2228               Remove a RIS service repository to enable.
2229
2230           -J, --rr-to-disable "alias'
2231               Remove a RIS service repository to disable.
2232
2233           -k, --cl-to-enable
2234               Clear the list of RIS repositories to enable.
2235
2236           -K, --cl-to-disable
2237               Clear the list of RIS repositories to disable.
2238
2239       services (ls) [options]
2240           List services defined on the system.
2241
2242           -u, --uri
2243               Show also base URI of repositories.
2244
2245           -p, --priority
2246               Show also repository priority.
2247
2248           -d, --details
2249               Show more information like URI, priority, type.
2250
2251           -r, --with-repos
2252               Show also repositories belonging to the services.
2253
2254           -P, --sort-by-priority
2255               Sort the list by repository priority.
2256
2257           -E, --show-enabled-only
2258               Show enabled services only. If used together with  --with-repos
2259               a  disabled services owning (manually) enabled repositories are
2260               shown as well.
2261
2262           -U, --sort-by-uri
2263               Sort the list by URI.
2264
2265           -N, --sort-by-name
2266               Sort the list by name.
2267
2268       refresh-services (refs) [options] alias|name|#|URI...
2269           Refreshing a service means executing the service’s special task.  +
2270           RIS  services  add,  remove,  or modify repositories on your system
2271           based on current content  of  the  repository  index.  A  differing
2272           enabled/disabled  state caused by manually calling modify-repo on a
2273           service  repository  however  will  not  be  reverted  unless   the
2274           --restore-status option is used, or the repository index explicitly
2275           requests the change. + Services only manage  defined  repositories,
2276           they  do  not  refresh  them.  To  refresh  also  repositories, use
2277           --with-repos option or the refresh command.
2278
2279           -f, --force
2280               Force a complete refresh of  specified  services.  This  option
2281               will cause both the download of raw metadata and parsing of the
2282               metadata to be forced even if everything indicates a refresh is
2283               not needed.
2284
2285           -r, --with-repos
2286               Refresh also the service repositories.
2287
2288           -R, --restore-status
2289               Also restore service repositories enabled/disabled state to the
2290               repository index default. Useful  after  you  manually  changed
2291               some service repositories enabled state.
2292
2293   Package Locks Management
2294       Package  locks  serve  the  purpose of preventing changes to the set of
2295       installed packages on the system. The locks are stored  in  form  of  a
2296       query  in  /etc/zypp/locks  file (see also locks(5)). Packages matching
2297       this query are then forbidden to  change  their  installed  status;  an
2298       installed  package  can’t  be  removed,  not installed package can’t be
2299       installed. When requesting to install or remove  such  locked  package,
2300       you will get a dependency problem dialog.
2301
2302       locks (ll)
2303           List currently active package locks.
2304
2305           -m, --matches
2306               Show  the  number  of  resolvables  matched  by each lock. This
2307               option requires loading the repositories.
2308
2309           -s, --solvables
2310               List the resolvables matched by each lock. This option requires
2311               loading the repositories.
2312
2313       addlock (al) [options] package-name...
2314           Add  a package lock. Specify packages to lock by exact name or by a
2315           glob pattern using * and ? wildcard characters.
2316
2317           -r, --repo alias|name|#|URI
2318               Restrict the lock to the specified repository.
2319
2320           -t, --type type
2321               Lock only packages of specified type  (default:  package).  See
2322               section Package Types for list of available package types.
2323
2324       removelock (rl) [options] lock-number|package-name...
2325           Remove  specified  package  lock. Specify the lock to remove by its
2326           number obtained with zypper locks or by the package name.
2327
2328           -r, --repo alias|name|#|URI
2329               Restrict the lock to the specified repository.
2330
2331           -t, --type type
2332               Restrict the lock  to  packages  of  specified  type  (default:
2333               package).  See  section  Package  Types  for  list of available
2334               package types.
2335
2336       cleanlocks (cl)
2337           Remove unused locks. + This command looks for  locks  that  do  not
2338           currently  (with  regard to repositories used) lock any package and
2339           for each such lock it asks user whether to remove it.
2340
2341       Locale  Management  ~~~~~~~  These  commands  give  information   about
2342       requested  locales  and  the  possibilty  to  manage those. A locale is
2343       defined by  a  language  code.  For  many  packages  there  are  locale
2344       dependent    packages   available   which   provide   translations   or
2345       dictionaries. To get  these  installed,  the  locale  for  the  desired
2346       language must be marked as requested by the package manager library.
2347
2348       locales (lloc) [OPTIONS] [LOCALE] ...
2349           List  requested locales. Called without argument, lists the locales
2350           which are already marked as requested. Specifying certain locale(s)
2351           prints information only for this(these).
2352
2353           -a, --all
2354               List all available locales.
2355
2356           -p, --packages
2357               Show corresponding packages.
2358
2359       addlocale (aloc) [OPTIONS] <LOCALE> ...
2360           Add specified locale(s) to the list of requested locales..
2361
2362           -n, --no-packages
2363               Do not install corresponding packages.
2364
2365       removelocale (rloc) [OPTIONS] <LOCALE> ...
2366           Remove specified locale(s) from the list of requested locales..
2367
2368           -n, --no-packages
2369               Do not remove corresponding packages.
2370
2371       Examples:
2372
2373
2374           $ zypper locales
2375               List requested locales.
2376
2377           $ zypper locales --packages de en
2378               Get  the  lists  of  packages which are available for de and en
2379               (exact match).
2380
2381           $ zypper locales en_
2382               Get all locales with lang code en that have their  own  country
2383               code, excluding the fallback en.
2384
2385           $ zypper locales en*
2386               Get all locales with lang code en with or without country code.
2387
2388           $ zypper aloc --packages de_CH
2389               Request de_CH and install language dependent packages.
2390
2391   Other Commands
2392       versioncmp (vcmp) version1 version2
2393           Compare  the  versions  supplied  as  arguments  and  tell  whether
2394           version1 is older or newer than version2 or the two version strings
2395           match.  +  The default output is in human-friendly form. If --terse
2396           global  option  is  used,  the  result  is   an   integer   number,
2397           negative/positive if version1 is older/newer than version2, zero if
2398           they match.
2399
2400           -m, --match
2401               Takes missing release number as any release.
2402
2403               For example:
2404
2405                   $ zypper vcmp -m 0.15.3 0.15.3-2
2406                       0.15.3 matches 0.15.3-2
2407
2408                   $ zypper vcmp 0.15.3 0.15.3-2
2409                       0.15.3 is older than 0.15.3-2
2410
2411       targetos (tos)
2412           Shows the ID string of the target operating system. The string  has
2413           a  form  of  distroname-architecture.  The  string is determined by
2414           libzypp,       the       distroname       is       read        from
2415           (current-rootdir)/etc/products.d/baseproduct  and  the architecture
2416           is determined from uname and CPU flags.
2417
2418       licenses
2419           Prints a report about licenses and 'EULA’s of installed packages to
2420           standard output. + First, a list of all packages and their licenses
2421           and/or EULAs is shown. This is followed by a summary, including the
2422           total  number  of  installed  packages,  the  number  of  installed
2423           packages with EULAs that required a  confirmation  from  the  user.
2424           Since  the  EULAs are not stored on the system and can only be read
2425           from repository metadata, the summary includes also the  number  of
2426           installed packages that have their counterpart in repositories. The
2427           report ends with a list of  all  licenses  uses  by  the  installed
2428           packages. + This command can be useful for companies redistributing
2429           a custom distribution (like appliances) to figure out what licenses
2430           they are bound by.
2431
2432       download
2433           Download  rpms specified on the commandline to a local directory. +
2434           Per default packages are downloaded to the  libzypp  package  cache
2435           (/var/cache/zypp/packages;         for        non-root        users
2436           $XDG_CACHE_HOME/zypp/packages), but this can be  changed  by  using
2437           the  global  --pkg-cache-dir option. + Parsable XML-output produced
2438           by zypper --xmlout will include a <download-result> node  for  each
2439           package  zypper tried to download. Upon success the location of the
2440           downloaded  package  is  found  in  the  path  attribute   of   the
2441           <localfile> subnode (xpath: download-result/localpath@path): +
2442
2443                   <download-result>
2444                     <solvable>
2445                       <kind>package</kind>
2446                       <name>zypper</name>
2447                       <edition epoch="0" version="1.9.17" release="26.1"/>
2448                       <arch>x86_64</arch>
2449                       <repository name="repo-oss-update (13.1)" alias="openSUSE:repo-oss-update"/>
2450                     </solvable>
2451                     <localfile path="/var/cache/zypp/pac.../zypper-1.9.17-26.1.x86_64.rpm"/>
2452                   </download-result>
2453
2454       --all-matches
2455                   Download  all  versions matching the commandline arguments.
2456           Otherwise only  the  best  version  of  each  matching  package  is
2457           downloaded.
2458
2459       --dry-run
2460           Don’t download any package, just report what would be done.
2461
2462       source-download
2463           Download  source  rpms  for  all  installed  packages  to  a  local
2464           directory.
2465
2466           -d, --directory dir
2467               Download  all  source  rpms  to  this  directory.  Default   is
2468               /var/cache/zypper/source-download.
2469
2470           --delete
2471               Delete  extraneous  source rpms in the local directory. This is
2472               the default.
2473
2474           --no-delete
2475               Do not delete extraneous source rpms.
2476
2477           --status
2478               Don’t download any source rpms, but show which source rpms  are
2479               missing or extraneous.
2480
2481       ps
2482           After  each  upgrade  or  removal of packages, there may be running
2483           processes on the system which continue  to  use  meanwhile  deleted
2484           files.  zypper ps lists all processes using deleted files, together
2485           with the corresponding files, and a service name hint, in case it’s
2486           a  known  service.  This gives a hint which services may need to be
2487           restarted after an update. Usually programs which continue  to  use
2488           deleted   shared   libraries.   The  list  contains  the  following
2489           information:
2490
2491           PID
2492               ID of the process
2493
2494           PPID
2495               ID of the parent process
2496
2497           UID
2498               ID of the user running the process
2499
2500           Login
2501               Login name of the user running the process
2502
2503           Command
2504               Command used to execute the process
2505
2506           Service
2507               Service name, if command is associated with a system service
2508
2509           Files
2510               The list of the deleted files
2511
2512               -s, --short
2513                   Create a short table not showing the deleted  files.  Given
2514                   twice,  show  only  processes  which  are associated with a
2515                   system service. Given  three  times,  list  the  associated
2516                   system service names only.
2517
2518               --print format
2519                   For  each  associated  system  service  print format on the
2520                   standard output, followed by a newline. Any %s directive in
2521                   format is replaced by the system service name.
2522
2523               -d, --debugFile filename
2524                   Output  a  file with all proc entries that make it into the
2525                   final set of used open files.  This  can  be  submitted  as
2526                   additional information in a bug report.
2527
2528               Examples:
2529
2530
2531           $ zypper ps -ss
2532               Show only processes associated with a system service.
2533
2534           $ zypper ps -sss
2535               Short  for  zypper  ps  --print "%s"; list services which might
2536               need a restart.
2537
2538           $ zypper ps --print "systemctl status %s"
2539               Let zypper print the commands to  retrieve  status  information
2540               for services which might need a restart.
2541
2542       needs-rebooting
2543           Checks  if  the  reboot-needed flag was set by a previous update or
2544           install of a core library or service. + The reboot-needed  flag  is
2545           set when a package from a predefined list (/etc/zypp/needreboot) is
2546           updated  or  installed.  Exit  code   ZYPPER_EXIT_INF_REBOOT_NEEDED
2547           indicates  that  a reboot is needed, otherwise the exit code is set
2548           to ZYPPER_EXIT_OK.
2549
2550   Subommands
2551       subcommand
2552           Lists available  subcommands  in  /usr/libexec/zypper/commands  and
2553           from elsewhere on your $PATH. See section SUBCOMMANDS for details.
2554

GLOBAL OPTIONS

2556       -h, --help
2557           Help.  If  a  command  is  specified  together  with --help option,
2558           command specific help is displayed.
2559
2560       -V, --version
2561           Print zypper version number and exit.
2562
2563       -c, --config file
2564           Use the  specified  zypper  config  file  instead  of  the  default
2565           zypper.conf.  Other  command  line  options specified together with
2566           --config and having their counterpart in the zypper config file are
2567           still  preferred.  +  The  order  of preference with --config is as
2568           follows:
2569
2570            1. Command line options
2571
2572            2. --config file
2573
2574            3. [/etc/zypp/zypp.conf] (system-wide  defaults  for  all  libzypp
2575               based applications)
2576
2577                   NOTE:    Use    and    location    of    the    system-wide
2578           /etc/zypp/zypp.conf can not be changed  this  way.  It’s  mentioned
2579           here  just  because  some  zypper  command  line  options  allow to
2580           overwrite system-wide defaults defined in zypp.conf.
2581
2582           +
2583                   See also FILES section for more information.
2584
2585       -v, --verbose
2586           Increase verbosity. For debugging output specify this option twice.
2587
2588       -q, --quiet
2589           Suppress normal output. Brief (esp. result  notification)  messages
2590           and  error messages will still be printed, though. If used together
2591           with conflicting  --verbose  option,  the  --verbose  option  takes
2592           preference.
2593
2594       --[no-]color
2595           Whether to use colors in output if tty supports it. For details see
2596           the [color] section in zypper.conf.
2597
2598       -A, --no-abbrev
2599           Do not abbreviate text in tables. By default  zypper  will  try  to
2600           abbreviate  texts  in some columns so that the table fits the width
2601           of the screen. If you need to see the whole text, use this option.
2602
2603       -t, --terse
2604           Terse output  for  machine  consumption.  Implies  --no-abbrev  and
2605           --no-color.
2606
2607       -s, --table-style
2608           Specifies  table  style  to  use.  Table  style is identified by an
2609           integer number.
2610
2611       -n, --non-interactive
2612           Switches to non-interactive mode. In this mode zypper  doesn’t  ask
2613           user  to  type answers to various prompts, but uses default answers
2614           automatically. Those default answers also depend on  other  options
2615           like --no-gpg-checks or --ignore-unknown.
2616
2617       --non-interactive-include-reboot-patches
2618           In  non-interactive  mode  do  not  skip  patches  which  have  the
2619           rebootSuggested-flag set. Otherwise these patches are considered to
2620           be  interactive,  like patches including a licenses or some message
2621           to confirm. NOTE: This option  does  not  turn  on  non-interactive
2622           mode.
2623
2624       -x, --xmlout
2625           Switches  to  XML  output.  This  option  is  useful for scripts or
2626           graphical frontends using zypper.
2627
2628       -i, --ignore-unknown
2629           Ignore unknown packages. This option is useful for scripts, because
2630           when  installing  in  --non-interactive  mode  zypper  expects each
2631           command line argument to match at least one known package.  Unknown
2632           names or globbing expressions with no match are treated as an error
2633           unless this option is used.
2634
2635       -D, --reposd-dir dir
2636           Use the specified directory to look for the  repository  definition
2637           (.repo) files. The default value is /etc/zypp/repos.d.
2638
2639       -C, --cache-dir dir
2640           Use an alternative root directory for all caches. The default value
2641           is /var/cache/zypp.
2642
2643       --raw-cache-dir dir
2644           Use the specified directory for storing raw  copies  of  repository
2645           metadata files. The default value is /var/cache/zypp/raw.
2646
2647       --solv-cache-dir dir
2648           Use  the specified directory to store the repository metadata cache
2649           database   files   (solv   files).    The    default    value    is
2650           /var/cache/zypp/solv.
2651
2652       --pkg-cache-dir dir
2653           Use  the  specified  directory for storing downloaded rpm packages.
2654           (see   addrepo    --keep-packages)    The    default    value    is
2655           /var/cache/zypp/packages.
2656
2657       --userdata string
2658           User  data  is expected to be a simple string without special chars
2659           or embedded newlines and may serve as transaction id.  It  will  be
2660           written  to all install history log entries created throughout this
2661           specific zypper call. It will also be passed  on  to  zypp  plugins
2662           executed during commit. This will enable e.g. a btrfs plugin to tag
2663           created snapshots with this string. For zypper itself  this  string
2664           has no special meaning.
2665
2666       Repository Options:
2667
2668
2669       --no-gpg-checks
2670           Ignore  GPG check failures and continue. If a GPG issue occurs when
2671           using  this  option  zypper  prints  and   logs   a   warning   and
2672           automatically  continues  without  interrupting  the operation. Use
2673           this option with caution,  as  you  can  easily  overlook  security
2674           problems by using it. (see section GPG checks) +
2675
2676       --gpg-auto-import-keys
2677           If  new  repository  signing  key  is found, do not ask what to do;
2678           trust and import it automatically. This option causes that the  new
2679           key  is  imported  also  in  non-interactive  mode,  where it would
2680           otherwise got rejected.
2681
2682       -p, --plus-repo URI
2683           Use an additional repository for  this  operation.  The  repository
2684           aliased  tmp# and named by the specified URI will be added for this
2685           operation and removed at the  end.  You  can  specify  this  option
2686           multiple times.
2687
2688       --plus-content tag
2689           Additionally  use  disabled  repositories  denoted  by tag for this
2690           operation. If tag matches a repositories alias, name or URL, or  is
2691           a keyword defined in the repositories metadata, the repository will
2692           be temporarily enabled for this operation. The repository will then
2693           be  refreshed  and  used  according  to the commands rules. You can
2694           specify this option multiple times. + If  a  disabled  repositories
2695           metadata  are  not  available  in  the  local  cache,  they will be
2696           downloaded to scan for matching  keywords.  Otherwise  the  keyword
2697           scan  will  use  the metadata available in the local cache. Only if
2698           used together with the refresh command, a keyword scan will refresh
2699           all disabled repositories. +
2700
2701           To refresh all disabled repositories metadata:
2702               zypper --plus-content '' ref
2703
2704           To include a disabled repository repo-debug in a search:
2705               zypper --plus-content repo-debug search ...
2706
2707           To search only in a disabled repository repo-debug:
2708               zypper --plus-content repo-debug search -r repo-debug ...
2709
2710           To enable all repos providing the debug keyword:
2711               zypper in --plus-content debug  some -debuginfo or -debugsource
2712               package
2713
2714       --disable-repositories
2715           Do not read metadata from repositories. This  option  will  prevent
2716           loading of packages from repositories, thus making zypper work only
2717           with the installed packages  (if  --disable-system-resolvables  was
2718           not specified).
2719
2720       --no-refresh
2721           Do not auto-refresh repositories (ignore the auto-refresh setting).
2722           Useful to save time when doing operations like search, if there  is
2723           not a need to have a completely up to date metadata.
2724
2725       --no-cd
2726           Ignore  CD/DVD  repositories. When this option is specified, zypper
2727           acts as if the CD/DVD repositories were not defined at all.
2728
2729       --no-remote
2730           Ignore remote repositories like http, ftp, smb  and  similar.  This
2731           makes  using  zypper easier when being offline. When this option is
2732           specified, zypper acts as  if  the  remote  repositories  were  not
2733           defined at all.
2734
2735       --releasever version
2736           Set  the  value  of  the  $releasever  variable  in all .repo files
2737           (default: current distribution version). This can be used to switch
2738           to  new  distribution  repositories  when performing a distribution
2739           upgrade. See section Repository  Management  and  the  dist-upgrade
2740           (dup) command for details. +
2741
2742           To check where you already use $releasever call:
2743               zypper --releasever @--HERE--@ lr -u
2744
2745       Target Options:
2746
2747
2748       -R, --root dir
2749           Operates  on a different root directory. This option influences the
2750           location of the repos.d directory and the metadata cache  directory
2751           and  also  causes  rpm  to  be run with the --root option to do the
2752           actual installation or removal of  packages.  See  also  the  FILES
2753           section.
2754
2755       --installroot dir
2756           Behaves  like  --root  but  shares  the  repositories with the host
2757           system.
2758
2759       --disable-system-resolvables
2760           This option serves mainly  for  testing  purposes.  It  will  cause
2761           zypper to act as if there were no packages installed in the system.
2762           Use with caution as you can damage your system using this option.
2763

SUBCOMMANDS

2765       Zypper subcommands are inspired by git(1). Subcommands  are  standalone
2766       executables       that       live       in      the      zypper_execdir
2767       (/usr/libexec/zypper/commands).  For  subcommands  zypper  provides   a
2768       wrapper that knows where the subcommands live, and runs them by passing
2769       command options and arguments to them. If a subcommand is not found  in
2770       the zypper_execdir, the wrapper will look in the rest of your $PATH for
2771       it. Thus, it’s possible to write local  zypper  extensions  that  don’t
2772       live in system space.
2773
2774       This is how to add your own subcommand zypper mytask:
2775
2776       ·   The executable must be named zypper-’mytask'.
2777
2778       ·   The executable must be located your $PATH.
2779
2780       ·   A manpage for zypper-’mytask' should be provided and explaining the
2781           commands options and return values. It will be shown  when  calling
2782           zypper help mytask.
2783
2784       ·   Zypper  built-in commands take precedence over subcommands with the
2785           same name.
2786
2787       ·   It’s  fine  to  call  zypper  or  use  libzypp  from  within   your
2788           subcommand.
2789
2790       You can use the built-in zypper subcommand command to get a list of all
2791       subcommands in zypper_execdir and from elsewhere on your $PATH.
2792
2793       Using zypper global-options  together  with  subcommands,  as  well  as
2794       executing subcommands in zypper shell is currently not supported.
2795

FILES

2797       /etc/zypp/zypper.conf, $HOME/.zypper.conf
2798           Global  (system-wide)  and  user’s  configuration  file for zypper.
2799           These files are read when zypper starts up and --config  option  is
2800           not  used.  +  User’s  settings are preferred over global settings.
2801           Similarly, command line options override the settings in either  of
2802           these  files.  To  sum it up, the order of preference is as follows
2803           (from highest to lowest):
2804
2805            1. Command line options
2806
2807            2. $HOME/.zypper.conf
2808
2809            3. /etc/zypp/zypper.conf
2810
2811            4. [/etc/zypp/zypp.conf] (system-wide  defaults  for  all  libzypp
2812               based applications)
2813
2814                   See  the  comments  in /etc/zypp/zypper.conf for a list and
2815           description of available options.
2816
2817                   NOTE: The system-wide /etc/zypp/zypp.conf is mentioned here
2818           just  because  some  zypper command line options allow to overwrite
2819           system-wide defaults defined there. zypp.conf and zypper.conf  have
2820           different content and serve different purpose.
2821
2822       /etc/zypp/zypp.conf
2823           ZYpp  configuration  file affecting all libzypp based applications.
2824           See the comments  in  the  file  for  description  of  configurable
2825           properties.  Many locations of files and directories listed in this
2826           section are configurable via zypp.conf. The location for this  file
2827           itself   can  be  redefined  only  by  setting  $ZYPP_CONF  in  the
2828           environment.
2829
2830       /etc/zypp/locks
2831           File with package lock definitions, see locks(5)  manual  page  for
2832           details.  The package lock commands (addlock, removelock, etc.) can
2833           be used to manipulate this  file.  +  This  file  is  used  by  all
2834           ZYpp-based applications.
2835
2836       /etc/zypp/repos.d
2837           Directory  containing repository definition (*.repo) files. You can
2838           use the Repository Management commands to manipulate  these  files,
2839           or  you  can  edit  them  yourself. In either case, after doing the
2840           modifications, executing *zypper refresh* is strongly  recommended.
2841           +  You can use the --reposd-dir global option to use an alternative
2842           directory for this purpose  or  the  --root  option  to  make  this
2843           directory   relative  to  the  specified  root  directory.  +  This
2844           directory is used by all ZYpp-based applications.
2845
2846       /etc/zypp/services.d
2847           Directory containing service definition (*.service) files. You  can
2848           use  the  Service Management Commands to manipulate these files, or
2849           you can edit them yourself. Running *zypper  refs*  is  recommended
2850           after modifications have been done. + This directory is used by all
2851           ZYpp-based applications.
2852
2853       /usr/libexec/zypper/commands
2854           System  directory  containing  zypper   extensions   (see   section
2855           SUBCOMMANDS)
2856
2857       /var/cache/zypp/raw
2858           Directory  for  storing raw metadata contained in repositories. Use
2859           the --raw-cache-dir global option to use an  alternative  directory
2860           for  this  purpose  or  the  --root  option  to make this directory
2861           relative to the specified root directory. + This directory is  used
2862           by all ZYpp-based applications.
2863
2864       /var/cache/zypp/solv
2865           Directory  containing  preparsed  metadata in form of solv files. +
2866           This directory is used by all ZYpp-based applications.
2867
2868       /var/cache/zypp/packages
2869           If  keeppackages  property  is  set  for  a  repository  (see   the
2870           modifyrepo   command),   all   the   RPM   file  downloaded  during
2871           installation will be kept here. See  also  the  clean  command  for
2872           cleaning  these  cache directories. + This directory is used by all
2873           ZYpp-based applications.
2874
2875       /var/log/zypp/history
2876           Installation history log.
2877
2878       ~/.zypper_history
2879           Command history for the zypper shell (see the shell command).
2880
2881       /etc/zypp/needreboot
2882           File with a list of packages that will set the  reboot-needed  flag
2883           when installed or upgraded.
2884
2885       /etc/zypp/needreboot.d
2886           Directory  that  can  be  used  to define packages that trigger the
2887           reboot-needed  flag  by  adding  additional  files  containing  the
2888           required package names.
2889

EXIT CODES

2891       There  are  several exit codes defined for zypper built-in commands for
2892       use e.g. within  scripts.  These  codes  are  defined  in  header  file
2893       src/zypper-main.h  found  in  zypper  source  package.  Codes below 100
2894       denote an error, codes above 100  provide  a  specific  information,  0
2895       represents  a normal successful run. Following is a list of these codes
2896       with descriptions:
2897
2898       0 - ZYPPER_EXIT_OK
2899           Successful run of zypper with no special info.
2900
2901       1 - ZYPPER_EXIT_ERR_BUG
2902           Unexpected situation occurred, probably caused by a bug.
2903
2904       2 - ZYPPER_EXIT_ERR_SYNTAX
2905           zypper was invoked with an invalid command  or  option,  or  a  bad
2906           syntax.
2907
2908       3 - ZYPPER_EXIT_ERR_INVALID_ARGS
2909           Some  of  provided  arguments were invalid. E.g. an invalid URI was
2910           provided to the addrepo command.
2911
2912       4 - ZYPPER_EXIT_ERR_ZYPP
2913           A problem is reported by ZYPP library.
2914
2915       5 - ZYPPER_EXIT_ERR_PRIVILEGES
2916           User invoking zypper  has  insufficient  privileges  for  specified
2917           operation.
2918
2919       6 - ZYPPER_EXIT_NO_REPOS
2920           No repositories are defined.
2921
2922       7 - ZYPPER_EXIT_ZYPP_LOCKED
2923           The ZYPP library is locked, e.g. packagekit is running.
2924
2925       8 - ZYPPER_EXIT_ERR_COMMIT
2926           An  error  occurred during installation or removal of packages. You
2927           may run zypper verify to repair any dependency problems.
2928
2929       100 - ZYPPER_EXIT_INF_UPDATE_NEEDED
2930           Returned by the patch-check command if there are patches  available
2931           for installation.
2932
2933       101 - ZYPPER_EXIT_INF_SEC_UPDATE_NEEDED
2934           Returned  by  the patch-check command if there are security patches
2935           available for installation.
2936
2937       102 - ZYPPER_EXIT_INF_REBOOT_NEEDED
2938           Returned after a successful installation of a patch which  requires
2939           reboot of computer.
2940
2941       103 - ZYPPER_EXIT_INF_RESTART_NEEDED
2942           Returned  after a successful installation of a patch which requires
2943           restart of the package manager  itself.  This  means  that  one  of
2944           patches  to be installed affects the package manager itself and the
2945           command used (e.g. zypper update) needs to be executed  once  again
2946           to install any remaining patches.
2947
2948       104 - ZYPPER_EXIT_INF_CAP_NOT_FOUND
2949           Returned  by  the install and the remove command in case any of the
2950           arguments does not  match  any  of  the  available  (or  installed)
2951           package names or other capabilities.
2952
2953       105 - ZYPPER_EXIT_ON_SIGNAL
2954           Returned upon exiting after receiving a SIGINT or SIGTERM.
2955
2956       106 - ZYPPER_EXIT_INF_REPOS_SKIPPED
2957           Some repository had to be disabled temporarily because it failed to
2958           refresh. You  should  check  your  repository  configuration  (e.g.
2959           zypper ref -f).
2960
2961       107 - ZYPPER_EXIT_INF_RPM_SCRIPT_FAILED
2962           Installation  basically  succeeded,  but some of the packages %post
2963           install scripts returned an error. These packages were successfully
2964           unpacked to disk and are registered in the rpm database, but due to
2965           the failed install script they may not work as expected. The failed
2966           scripts  output  might reveal what actually went wrong. Any scripts
2967           output is also logged to /var/log/zypp/history.
2968
2969       Zypper subcommands (see section SUBCOMMANDS) may return different codes
2970       which  should  be  described in the commands man page. Call zypper help
2971       subcommand to see the subcommands man page if one is provided.
2972

HOMEPAGE

2974       <https://github.com/openSUSE/zypper>
2975

AUTHORS

2977       The zypper project was started by Martin  Vidner,  Jan  Kupec,  Michael
2978       Andres,   Duncan   Mac-Vicar   Prett,  Josef  Reidinger  and  Stanislav
2979       Visnovsky. Many people have later contributed to it.
2980

SEE ALSO

2982       locks(5), zypper-log(8), YaST2(8)
2983
2984
2985
2986SUSE Linux                        2019-05-28                         ZYPPER(8)
Impressum