Linux系统管理基础-RHEL软件包管理03-yum指令的man手册_yum multiple matches

Linux系统管理基础-RHEL软件包管理03-yum指令的man手册

YUM(8)                                       DNF                                      YUM(8)

NAME
       yum - redirecting to DNF Command Reference

SYNOPSIS
       dnf [options] <command> [<args>...]

DESCRIPTION
       DNF  is the next upcoming major version of YUM, a package manager for RPM-based Linux
       distributions. It roughly maintains CLI compatibility with YUM and defines  a  strict
       API for extensions and plugins.

       Plugins  can  modify  or extend features of DNF or provide additional CLI commands on
       top of those mentioned below. If you know the name of such a command (including  com‐
       mands  mentioned below), you may find/install the package which provides it using the
       appropriate virtual provide in the form of dnf-command(<alias>), where <alias> is the
       name  of  the command; e.g.``dnf install 'dnf-command(versionlock)'`` installs a ver‐
       sionlock plugin. This approach also applies to specifying  dependencies  of  packages
       that require a particular DNF command.

       Return values:

       • 0  : Operation was successful.

       • 1  : An error occurred, which was handled by dnf.

       • 3  : An unknown unhandled error occurred during operation.

       • 100: See check-update

       • 200: There was a problem with acquiring or releasing of locks.

       Available commands:

       • alias

       • autoremove

       • check

       • check-update

       • clean

       • deplist

       • distro-sync

       • downgrade

       • group

       • help

       • history

       • info

       • install

       • list

       • makecache

       • mark

       • module

       • provides

       • reinstall

       • remove

       • repoinfo

       • repolist

       • repoquery

       • repository-packages

       • search

       • shell

       • swap

       • updateinfo

       • upgrade

       • upgrade-minimal

       Additional information:

       • Options

       • Specifying Packages

       • Specifying Provides

       • Specifying File Provides

       • Specifying Groups

       • Specifying Transactions

       • Metadata Synchronization

       • Configuration Files Replacement Policy

       • Files

       • See Also

OPTIONS
       -4     Resolve to IPv4 addresses only.

       -6     Resolve to IPv6 addresses only.

       --advisory=<advisory>, --advisories=<advisory>
              Include  packages  corresponding to the advisory ID, Eg. FEDORA-2201-123.  Ap‐
              plicable for the install, repoquery, updateinfo, upgrade  and  offline-upgrade
              (dnf-plugins-core) commands.

       --allowerasing
              Allow erasing of installed packages to resolve dependencies. This option could
              be used as an alternative to the yum swap command where packages to remove are
              not explicitly defined.

       --assumeno
              Automatically answer no for all questions.

       -b, --best
              Try  the  best available package versions in transactions. Specifically during
              dnf upgrade, which by default skips over updates that can not be installed for
              dependency  reasons,  the  switch forces DNF to only consider the latest pack‐
              ages. When running into packages with broken dependencies, DNF will fail  giv‐
              ing a reason why the latest version can not be installed.

              Note  that  the use of the newest available version is only guaranteed for the
              packages directly requested (e.g. as a command line arguments), and the solver
              may use older versions of dependencies to meet their requirements.

       --bugfix
              Include  packages  that fix a bugfix issue.  Applicable for the install, repo‐
              query, updateinfo, upgrade and offline-upgrade (dnf-plugins-core) commands.

       --bz=<bugzilla>, --bzs=<bugzilla>
              Include packages that fix a Bugzilla ID, Eg. 123123.  Applicable for  the  in‐
              stall,  repoquery,  updateinfo, upgrade and offline-upgrade (dnf-plugins-core)
              commands.

       -C, --cacheonly
              Run entirely from system cache, don't update the cache and use it even in case
              it is expired.

              DNF uses a separate cache for each user under which it executes. The cache for
              the root user is called the system cache. This switch allows  a  regular  user
              read-only  access  to  the  system cache, which usually is more fresh than the
              user's and thus he does not have to wait for metadata sync.

       --color=<color>
              Control whether color is used in terminal output.  Valid  values  are  always,
              never and auto (default).

       --comment=<comment>
              Add a comment to the transaction history.

       -c <config file>, --config=<config file>
              Configuration file location.

       --cve=<cves>, --cves=<cves>
              Include  packages  that fix a CVE (Common Vulnerabilities and Exposures) ID (‐
              http://cve.mitre.org/about/), Eg. CVE-2201-0123.  Applicable for the  install,
              repoquery,  updateinfo,  upgrade  and  offline-upgrade (dnf-plugins-core) com‐
              mands.

       -d <debug level>, --debuglevel=<debug level>
              Debugging output level. This is an integer value between 0 (no additional  in‐
              formation  strings) and 10 (shows all debugging information, even that not un‐
              derstandable to the user), default is 2. Deprecated, use -v instead.

       --debugsolver
              Dump data aiding in dependency solver debugging into ./debugdata.

       --disableexcludes=[all|main|<repoid>], --disableexcludepkgs=[all|main|<repoid>]
          Disable the configuration file excludes. Takes one of the following three options:

          • all, disables all configuration file excludes

          • main, disables excludes defined in the [main] section

          • repoid, disables excludes defined for the given repository

       --disable, --set-disabled
              Disable specified repositories (automatically saves). The  option  has  to  be
              used together with the config-manager command (dnf-plugins-core).

       --disableplugin=<plugin names>
              Disable the listed plugins specified by names or globs.

       --disablerepo=<repoid>
              Temporarily  disable  active  repositories  for the purpose of the current dnf
              command.  Accepts an id, a comma-separated list of ids, or a glob of ids. This
              option can be specified multiple times, but is mutually exclusive with --repo.

       --downloaddir=<path>, --destdir=<path>
              Redirect  downloaded packages to provided directory. The option has to be used
              together with the --downloadonly command line option, with the download,  mod‐
              ulesync, reposync or system-upgrade commands (dnf-plugins-core).

       --downloadonly
              Download  the resolved package set without performing any rpm transaction (in‐
              stall/upgrade/erase).

              Packages are removed after the next successful transaction. This applies  also
              when  used  together with --destdir option as the directory is considered as a
              part of the DNF cache. To persist the packages, use the download  command  in‐
              stead.

       -e <error level>, --errorlevel=<error level>
              Error  output  level. This is an integer value between 0 (no error output) and
              10 (shows all error messages), default is 3. Deprecated, use -v instead.

       --enable, --set-enabled
              Enable specified repositories (automatically saves). The option has to be used
              together with the config-manager command (dnf-plugins-core).

       --enableplugin=<plugin names>
              Enable the listed plugins specified by names or globs.

       --enablerepo=<repoid>
              Temporarily  enable additional repositories for the purpose of the current dnf
              command.  Accepts an id, a comma-separated list of ids, or a glob of ids. This
              option can be specified multiple times.

       --enhancement
              Include enhancement relevant packages.  Applicable for the install, repoquery,
              updateinfo, upgrade and offline-upgrade (dnf-plugins-core) commands.

       -x <package-file-spec>, --exclude=<package-file-spec>
              Exclude packages specified by <package-file-spec> from the operation.

       --excludepkgs=<package-file-spec>
              Deprecated option. It was replaced by the --exclude option.

       --forcearch=<arch>
              Force the use of an architecture. Any architecture can be specified.  However,
              use  of an architecture not supported natively by your CPU will require emula‐
              tion of some kind. This is usually through QEMU. The behavior  of  --forcearch
              can  be configured by using the arch and ignorearch configuration options with
              values <arch> and True respectively.

       -h, --help, --help-cmd
              Show the help.

       --installroot=<path>
              Specifies an alternative installroot, relative to where all packages  will  be
              installed. Think of this like doing chroot <root> dnf, except using --install‐
              root allows dnf to work before the chroot is  created.  It  requires  absolute
              path.

       • cachedir,  log  files,  releasever,  and gpgkey are taken from or stored in the in‐
         stallroot. Gpgkeys are imported into the installroot from a path  relative  to  the
         host which can be specified in the repository section of configuration files.

       • configuration  file and reposdir are searched inside the installroot first. If they
         are not present, they are taken from the host system.  Note:  When a path is speci‐
         fied  within  a command line argument (--config=<config file> in case of configura‐
         tion file and --setopt=reposdir=<reposdir> for reposdir) then this path  is  always
         relative to the host with no exceptions.

       • vars are taken from the host system or installroot according to reposdir . When re‐
         posdir path is specified within a command line argument, vars are  taken  from  the
         installroot. When varsdir paths are specified within a command line argument (--se‐
         topt=varsdir=<reposdir>) then those path are always relative to the  host  with  no
         exceptions.

       • The pluginpath and pluginconfpath are relative to the host.
          Note: You may also want to use the command-line option --releasever=<release> when
          creating the installroot, otherwise the $releasever value is taken from the  rpmdb
          within  the  installroot  (and  thus  it  is empty at the time of creation and the
          transaction will fail). If --releasever=/ is used, the releasever will be detected
          from  the  host  (/) system. The new installroot path at the time of creation does
          not contain the repository, releasever and dnf.conf files.

          On a modular system you may also want to use the --setopt=module_platform_id=<mod‐
          ule_platform_name:stream>  command-line option when creating the installroot, oth‐
          erwise the module_platform_id value will be taken from  the  /etc/os-release  file
          within  the  installroot  (and  thus it will be empty at the time of creation, the
          modular dependency could be unsatisfied and modules content could be excluded).

          Installroot examples:

          dnf --installroot=<installroot> --releasever=<release> install system-release
                 Permanently sets the releasever of the system in the  <installroot>  direc‐
                 tory to <release>.

          dnf  --installroot=<installroot>  --setopt=reposdir=<path> --config /path/dnf.conf
          upgrade
                 Upgrades packages inside the installroot from  a  repository  described  by
                 --setopt using configuration from /path/dnf.conf.

       --newpackage
              Include  newpackage relevant packages.  Applicable for the install, repoquery,
              updateinfo, upgrade and offline-upgrade (dnf-plugins-core) commands.

       --noautoremove
              Disable removal of dependencies that are no longer  used.  It  sets  clean_re‐
              quirements_on_remove configuration option to False.

       --nobest
              Set  best option to False, so that transactions are not limited to best candi‐
              dates only.

       --nodocs
              Do not install documentation. Sets the rpm flag 'RPMTRANS_FLAG_NODOCS'.

       --nogpgcheck
              Skip checking GPG signatures on packages (if RPM policy allows).

       --noplugins
              Disable all plugins.

       --obsoletes
              This option has an effect on an install/update,  it  enables  dnf's  obsoletes
              processing logic. For more information see the obsoletes option.

              This  option  also  displays capabilities that the package obsoletes when used
              together with the repoquery command.

              Configuration Option: obsoletes

       -q, --quiet
              In combination with a non-interactive command, shows just  the  relevant  con‐
              tent. Suppresses messages notifying about the current state or actions of DNF.

       -R <minutes>, --randomwait=<minutes>
              Maximum command wait time.

       --refresh
              Set metadata as expired before running the command.

       --releasever=<release>
              Configure  DNF  as  if the distribution release was <release>. This can affect
              cache paths, values in configuration files and mirrorlist URLs.

       --repofrompath <repo>,<path/url>
              Specify a repository to add to the repositories for this query.   This  option
              can be used multiple times.

       • The repository label is specified by <repo>.

       • The  path or url to the repository is specified by <path/url>.  It is the same path
         as a baseurl and can be also enriched by the repo variables.

       • The   configuration   for   the   repository   can    be    adjusted    using    -‐
         -setopt=<repo>.<option>=<value>.

       • If  you  want  to  view  only  packages from this repository, combine this with the
         --repo=<repo> or --disablerepo="*" switches.

       --repo=<repoid>, --repoid=<repoid>
              Enable just specific repositories by an id or a glob.  Can  be  used  multiple
              times  with  accumulative  effect.  It  is  basically  a  shortcut  for --dis‐
              ablerepo="*" --enablerepo=<repoid> and is mutually exclusive with  the  --dis‐
              ablerepo option.

       --rpmverbosity=<name>
              RPM  debug  scriptlet  output  level.  Sets  the debug level to <name> for RPM
              scriptlets.  For available levels, see the rpmverbosity configuration option.

       --sec-severity=<severity>, --secseverity=<severity>
              Includes packages that provide a fix for an issue of the  specified  severity.
              Applicable for the install, repoquery, updateinfo, upgrade and offline-upgrade
              (dnf-plugins-core) commands.

       --security
              Includes packages that provide a fix for a security issue.  Applicable for the
              install, repoquery, updateinfo, upgrade and offline-upgrade (dnf-plugins-core)
              commands.

       --setopt=<option>=<value>
              Override a configuration option from the configuration file. To override  con‐
              figuration  options for repositories, use repoid.option for the <option>. Val‐
              ues for configuration options like excludepkgs,  includepkgs,  installonlypkgs
              and  tsflags are appended to the original value, they do not override it. How‐
              ever, specifying an empty value (e.g. --setopt=tsflags=) will  clear  the  op‐
              tion.

       --skip-broken
              Resolve  depsolve problems by removing packages that are causing problems from
              the transaction.  It is an alias for  the  strict  configuration  option  with
              value  False.  Additionally, with the enable and disable module subcommands it
              allows one to perform an action even in case of broken modular dependencies.

       --showduplicates
              Show duplicate packages in repositories. Applicable for the  list  and  search
              commands.

       -v, --verbose
              Verbose operation, show debug messages.

       --version
              Show DNF version and exit.

       -y, --assumeyes
              Automatically answer yes for all questions.

       List  options  are comma-separated. Command-line options override respective settings
       from configuration files.

COMMANDS
       For an explanation of <package-spec>, <package-file-spec> and <package-name-spec> see
       Specifying Packages.

       For an explanation of <provide-spec> see Specifying Provides.

       For an explanation of <group-spec> see Specifying Groups.

       For an explanation of <module-spec> see Specifying Modules.

       For an explanation of <transaction-spec> see Specifying Transactions.

   Alias Command
       Command: alias

       Allows  the  user  to define and manage a list of aliases (in the form <name=value>),
       which can be then used as dnf commands to abbreviate longer  command  sequences.  For
       examples  on  using  the alias command, see Alias Examples. For examples on the alias
       processing, see Alias Processing Examples.

       To use an alias (name=value), the name must be placed as the  first  "command"  (e.g.
       the  first  argument that is not an option). It is then replaced by its value and the
       resulting sequence is again searched for aliases. The alias processing stops when the
       first found command is not a name of any alias.

       In  case the processing would result in an infinite recursion, the original arguments
       are used instead.

       Also, like in shell aliases, if the result starts with a \, the alias processing will
       stop.

       All  aliases  are defined in configuration files in the /etc/dnf/aliases.d/ directory
       in the [aliases] section, and aliases created by the alias command are written to the
       USER.conf file. In case of conflicts, the USER.conf has the highest priority, and al‐
       phabetical ordering is used for the rest of the configuration files.

       Optionally, there is the enabled option in the [main]  section  defaulting  to  True.
       This  can be set for each file separately in the respective file, or globally for all
       aliases in the ALIASES.conf file.

       dnf alias [options] [list] [<name>...]
          List aliases with their final result. The [<alias>...]  parameter  further  limits
          the result to only those aliases matching it.

       dnf alias [options] add <name=value>...
          Create new aliases.

       dnf alias [options] delete <name>...
          Delete aliases.

   Alias Examples
       dnf alias list
              Lists all defined aliases.

       dnf alias add rm=remove
              Adds a new command alias called rm which works the same as the remove command.

       dnf alias add upgrade="\upgrade --skip-broken --disableexcludes=all --obsoletes"
              Adds  a  new  command alias called upgrade which works the same as the upgrade
              command, with additional options. Note that the original  upgrade  command  is
              prefixed with a \ to prevent an infinite loop in alias processing.

   Alias Processing Examples
       If  there  are  defined  aliases  in=install  and  FORCE="--skip-broken  --disableex‐
       cludes=all":

       • dnf FORCE in will be replaced with dnf --skip-broken --disableexcludes=all install

       • dnf in FORCE will be replaced with dnf install FORCE (which will fail)

       If there is defined alias in=install:

       • dnf in will be replaced with dnf install

       • dnf --repo updates in will be replaced with dnf --repo updates in (which will fail)

   Autoremove Command
       Command: autoremove
       Aliases for explicit NEVRA matching: autoremove-n, autoremove-na, autoremove-nevra

       dnf [options] autoremove
          Removes all "leaf" packages from the system that were originally installed as  de‐
          pendencies  of  user-installed  packages,  but which are no longer required by any
          such package.

       Packages listed in installonlypkgs are never automatically removed by this command.

       dnf [options] autoremove <spec>...
          This is an alias for the Remove Command command with  clean_requirements_on_remove
          set  to  True.  It  removes  the specified packages from the system along with any
          packages depending on the packages being removed. Each  <spec>  can  be  either  a
          <package-spec>,  which  specifies  a  package  directly, or a @<group-spec>, which
          specifies an (environment) group which contains it. It also removes any  dependen‐
          cies that are no longer needed.

          There  are also a few specific autoremove commands autoremove-n, autoremove-na and
          autoremove-nevra that allow the specification of an exact argument  in  the  NEVRA
          (name-epoch:version-release.architecture) format.

       This  command by default does not force a sync of expired metadata. See also Metadata
       Synchronization.

   Check Command
       Command: check

       dnf [options] check [--dependencies] [--duplicates] [--obsoleted] [--provides]
          Checks the local packagedb and produces information on any problems it finds.  You
          can  limit  the  checks to be performed by using the --dependencies, --duplicates,
          --obsoleted and --provides options (the default is to check everything).

   Check-Update Command
       Command: check-update
       Aliases: check-upgrade

       dnf [options] check-update [--changelogs] [<package-file-spec>...]
          Non-interactively checks if updates of the specified packages are available. If no
          <package-file-spec>  is given, checks whether any updates at all are available for
          your system. DNF exit code will be 100 when there are updates available and a list
          of the updates will be printed, 0 if not and 1 if an error occurs. If --changelogs
          option is specified, also changelog delta of  packages  about  to  be  updated  is
          printed.

          Please  note that having a specific newer version available for an installed pack‐
          age (and reported by check-update) does not imply that subsequent dnf upgrade will
          install  it. The difference is that dnf upgrade has restrictions (like package de‐
          pendencies being satisfied) to take into account.

          The output is affected by the autocheck_running_kernel configuration option.

   Clean Command
       Command: clean

       Performs cleanup of temporary files kept for repositories.  This  includes  any  such
       data  left behind from disabled or removed repositories as well as for different dis‐
       tribution release versions.

       dnf clean dbcache
              Removes cache files generated from the repository metadata. This forces DNF to
              regenerate the cache files the next time it is run.

       dnf clean expire-cache
              Marks the repository metadata expired. DNF will re-validate the cache for each
              repository the next time it is used.

       dnf clean metadata
              Removes repository metadata. Those are the files which DNF uses  to  determine
              the  remote availability of packages. Using this option will make DNF download
              all the metadata the next time it is run.

       dnf clean packages
              Removes any cached packages from the system.

       dnf clean all
              Does all of the above.

   Deplist Command
       dnf [options] deplist [<select-options>] [<query-options>] [<package-spec>]
              Deprecated alias for dnf repoquery --deplist.

   Distro-Sync Command
       Command: distro-sync
       Aliases: dsync
       Deprecated aliases: distrosync, distribution-synchronization

       dnf distro-sync [<package-spec>...]
              As necessary upgrades, downgrades or  keeps  selected  installed  packages  to
              match  the latest version available from any enabled repository. If no package
              is given, all installed packages are considered.

              See also Configuration Files Replacement Policy.

   Downgrade Command
       Command: downgrade
       Aliases: dg

       dnf [options] downgrade <package-spec>...
              Downgrades the specified packages to the highest installable  package  of  all
              known lower versions if possible. When version is given and is lower than ver‐
              sion of installed package then it downgrades to target version.

   Group Command
       Command: group
       Aliases: grp
       Deprecated aliases: groups, grouplist, groupinstall, groupupdate, groupremove, grouperase, groupinfo

       Groups are virtual collections of packages. DNF keeps track of groups that  the  user
       selected  ("marked") installed and can manipulate the comprising packages with simple
       commands.

       dnf [options] group [summary] <group-spec>
              Display overview of how many groups are installed and available. With a  spec,
              limit the output to the matching groups. summary is the default groups subcom‐
              mand.

       dnf [options] group info <group-spec>
              Display package lists of a group. Shows which packages are installed or avail‐
              able from a repository when -v is used.

       dnf [options] group install [--with-optional] <group-spec>...
              Mark  the specified group installed and install packages it contains. Also in‐
              clude optional packages of the group  if  --with-optional  is  specified.  All
              mandatory  and  Default  packages will be installed whenever possible.  Condi‐
              tional packages are installed if they meet their requirement.  If the group is
              already  (partially) installed, the command installs the missing packages from
              the group.  Depending on the value of obsoletes configuration option group in‐
              stallation takes obsoletes into account.

       dnf [options] group list <group-spec>...
              List all matching groups, either among installed or available groups. If noth‐
              ing is specified, list all known groups. --installed and  --available  options
              narrow  down the requested list.  Records are ordered by the display_order tag
              defined in comps.xml file.  Provides a list of all hidden groups by using  op‐
              tion --hidden.  Provides group IDs when the -v or --ids options are used.

       dnf [options] group remove <group-spec>...
              Mark  the group removed and remove those packages in the group from the system
              which do not belong to another installed group and were not installed  explic‐
              itly by the user.

       dnf [options] group upgrade <group-spec>...
              Upgrades the packages from the group and upgrades the group itself. The latter
              comprises of installing packages that were added to the group by the distribu‐
              tion and removing packages that got removed from the group as far as they were
              not installed explicitly by the user.

       Groups can also be marked installed or removed without  physically  manipulating  any
       packages:

       dnf [options] group mark install <group-spec>...
              Mark the specified group installed. No packages will be installed by this com‐
              mand, but the group is then considered installed.

       dnf [options] group mark remove <group-spec>...
              Mark the specified group removed. No packages will be removed by this command.

       See also Configuration Files Replacement Policy.

   Help Command
       Command: help

       dnf help [<command>]
              Displays the help text for all commands. If given a  command  name  then  only
              displays help for that particular command.

   History Command
       Command: history
       Aliases: hist

       The  history  command  allows the user to view what has happened in past transactions
       and act according to this information (assuming the history_record configuration  op‐
       tion is set).

       dnf history [list] [--reverse] [<spec>...]
              The  default history action is listing information about given transactions in
              a table. Each <spec> can be either a  <transaction-spec>,  which  specifies  a
              transaction directly, or a <transaction-spec>..<transaction-spec>, which spec‐
              ifies a range of transactions, or a  <package-name-spec>,  which  specifies  a
              transaction  by  a package which it manipulated. When no transaction is speci‐
              fied, list all known transactions.

              The "Action(s)" column lists each type of action taken in the transaction. The
              possible values are:

              • Install (I): a new package was installed on the system

              • Downgrade  (D):  an  older  version of a package replaced the previously-in‐
                stalled version

              • Obsolete (O): an obsolete package was replaced by a new package

              • Upgrade (U): a newer version of  the  package  replaced  the  previously-in‐
                stalled version

              • Remove (E): a package was removed from the system

              • Reinstall (R): a package was reinstalled with the same version

              • Reason change (C): a package was kept in the system but its reason for being
                installed changed

              The "Altered" column lists the number of actions taken  in  each  transaction,
              possibly followed by one or two the following symbols:

              • >: The RPM database was changed, outside DNF, after the transaction

              • <: The RPM database was changed, outside DNF, before the transaction

              • *: The transaction aborted before completion

              • #: The transaction completed, but with a non-zero status

              • E: The transaction completed successfully, but had warning/error output

              --reverse
                     The order of history list output is printed in reverse order.

       dnf history info [<spec>...]
              Describe  the  given transactions. The meaning of <spec> is the same as in the
              History List Command. When no transaction is specified, describe what happened
              during the latest transaction.

       dnf history redo <transaction-spec>|<package-file-spec>
              Repeat  the specified transaction. Uses the last transaction (with the highest
              ID) if more than one transaction for given <package-file-spec> is found. If it
              is  not possible to redo some operations due to the current state of RPMDB, it
              will not redo the transaction.

       dnf history replay [--ignore-installed] [--ignore-extras] [--skip-unavailable] <file‐
       name>
              Replay  a  transaction stored in file <filename> by History Store Command. The
              replay will perform the exact same operations on the packages as in the origi‐
              nal  transaction  and  will return with an error if case of any differences in
              installed packages or their versions. See also  the  Transaction  JSON  Format
              specification of the file format.

              --ignore-installed
                     Don't check for the installed packages being in the same state as those
                     recorded in the transaction. E.g. in case there is an  upgrade  foo-1.0
                     -> foo-2.0 stored in the transaction, but there is foo-1.1 installed on
                     the target system.

              --ignore-extras
                     Don't check for extra packages pulled into the transaction on the  tar‐
                     get  system. E.g. the target system may not have some dependency, which
                     was installed on the source system. The replay errors out  on  this  by
                     default, as the transaction would not be the same.

              --skip-unavailable
                     In  case  some  packages stored in the transaction are not available on
                     the target system, skip them instead of erroring out.

       dnf history rollback <transaction-spec>|<package-file-spec>
              Undo all transactions performed after the specified transaction. Uses the last
              transaction  (with  the  highest  ID)  if  more than one transaction for given
              <package-file-spec> is found.  If it is not possible to undo some transactions
              due to the current state of RPMDB, it will not undo any transaction.

       dnf history store [--output <output-file>] <transaction-spec>
              Store a transaction specified by <transaction-spec>. The transaction can later
              be replayed by the History Replay Command.

              Warning: The stored transaction format is considered unstable and  may  change
              at  any time. It will work if the same version of dnf is used to store and re‐
              play (or between versions as long as it stays the same).

              -o <output-file>, --output=<output-file> Store the serialized transaction into
              <output-file. Default is transaction.json.

       dnf history undo <transaction-spec>|<package-file-spec>
              Perform  the  opposite  operation to all operations performed in the specified
              transaction.  Uses the last transaction (with the highest ID) if more than one
              transaction  for  given <package-file-spec> is found. If it is not possible to
              undo some operations due to the current state of RPMDB, it will not  undo  the
              transaction.

       dnf history userinstalled
              Show  all installonly packages, packages installed outside of DNF and packages
              not installed as dependency. I.e. it lists packages that will stay on the sys‐
              tem  when  Autoremove  Command  or  Remove  Command  along with clean_require‐
              ments_on_remove configuration option set to True is executed.  Note  the  same
              results  can be accomplished with dnf repoquery --userinstalled, and the repo‐
              query command is more powerful in formatting of the output.

       This command by default does not force a sync of expired  metadata,  except  for  the
       redo,  rollback,  and  undo  subcommands.   See  also  Metadata  Synchronization  and
       Configuration Files Replacement Policy.

   Info Command
       Command: info
       Aliases: if

       dnf [options] info [<package-file-spec>...]
              Lists description and summary information about installed and available  pack‐
              ages.

       The info command limits the displayed packages the same way as the list command.

       This  command by default does not force a sync of expired metadata. See also Metadata
       Synchronization.

   Install Command
       Command: install
       Aliases: in
       Aliases for explicit NEVRA matching: install-n, install-na, install-nevra
       Deprecated aliases: localinstall

       dnf [options] install <spec>...
              Makes sure that the given packages and their dependencies are installed on the
              system.  Each <spec> can be either a <package-spec>, or a @<module-spec>, or a
              @<group-spec>.  See Install Examples.  If a given package or provide cannot be
              (and is not already) installed, the exit code will be non-zero.  If the <spec>
              matches both a @<module-spec> and a @<group-spec>,  only  the  module  is  in‐
              stalled.

              When  <package-spec> to specify the exact version of the package is given, DNF
              will install the desired version, no matter which version of  the  package  is
              already  installed.  The  former version of the package will be removed in the
              case of non-installonly package.

              On the other hand if <package-spec> specifies only a name, DNF also takes into
              account  packages  obsoleting  it when picking which package to install.  This
              behaviour is specific to the install command.  Note  that  this  can  lead  to
              seemingly unexpected results if a package has multiple versions and some older
              version is being obsoleted. It creates a split in the  upgrade-path  and  both
              ways are considered correct, the resulting package is picked simply by lexico‐
              graphical order.

              There are also a few specific install commands install-n, install-na  and  in‐
              stall-nevra  that  allow  the  specification of an exact argument in the NEVRA
              format.

              See also Configuration Files Replacement Policy.

   Install Examples
       dnf install tito
              Install the tito package (tito is the package name).

       dnf install ~/Downloads/tito-0.6.2-1.fc22.noarch.rpm
              Install a local rpm file tito-0.6.2-1.fc22.noarch.rpm  from  the  ~/Downloads/
              directory.

       dnf install tito-0.5.6-1.fc22
              Install  the  package  with  a specific version. If the package is already in‐
              stalled it will automatically try to downgrade or upgrade to the specific ver‐
              sion.

       dnf --best install tito
              Install the latest available version of the package. If the package is already
              installed it will try to automatically upgrade to the latest version.  If  the
              latest version of the package cannot be installed, the installation will fail.

       dnf install vim
              DNF will automatically recognize that vim is not a package name, but will look
              up and install a package that provides vim with all the required dependencies.
              Note: Package name match has precedence over package provides match.

       dnf                 install                 https://kojipkgs.fedoraproject.org//pack‐
       ages/tito/0.6.0/1.fc22/noarch/tito-0.6.0-1.fc22.noarch.rpm
              Install a package directly from a URL.

       dnf install '@docker'
              Install all default profiles of module 'docker' and their RPMs. Module streams
              get enabled accordingly.

       dnf install '@Web Server'
              Install the 'Web Server' environmental group.

       dnf install /usr/bin/rpmsign
              Install a package that provides the /usr/bin/rpmsign file.

       dnf -y install tito --setopt=install_weak_deps=False
              Install  the  tito  package (tito is the package name) without weak deps. Weak
              deps are not required for core functionality of the package, but they  enhance
              the  original  package (like extended documentation, plugins, additional func‐
              tions, etc.).

       dnf install --advisory=FEDORA-2018-b7b99fe852 \*
              Install all packages that belong to the "FEDORA-2018-b7b99fe852" advisory.

   List Command
       Command: list
       Aliases: ls

       Prints lists of packages depending on the packages' relation to the system. A package
       is  installed  if  it  is  present in the RPMDB, and it is available if it is not in‐
       stalled but is present in a repository that DNF knows about.

       The list command also limits the displayed packages according to  specific  criteria,
       e.g. to only those that update an installed package (respecting the repository prior‐
       ity). The exclude option in the configuration file can influence the result,  but  if
       the  --disableexcludes  command  line  option  is used, it ensures that all installed
       packages will be listed.

       dnf [options] list [--all] [<package-file-spec>...]
              Lists all packages, present in the RPMDB, in a repository or both.

       dnf [options] list --installed [<package-file-spec>...]
              Lists installed packages.

       dnf [options] list --available [<package-file-spec>...]
              Lists available packages.

       dnf [options] list --extras [<package-file-spec>...]
              Lists extras, that is packages installed on the system that are not  available
              in any known repository.

       dnf [options] list --obsoletes [<package-file-spec>...]
              List  packages  installed  on the system that are obsoleted by packages in any
              known repository.

       dnf [options] list --recent [<package-file-spec>...]
              List packages recently added into the repositories.

       dnf [options] list --upgrades [<package-file-spec>...]
              List upgrades available for the installed packages.

       dnf [options] list --autoremove
              List packages which will be removed by the dnf autoremove command.

       This command by default does not force a sync of expired metadata. See also  Metadata
       Synchronization.

   Makecache Command
       Command: makecache
       Aliases: mc

       dnf [options] makecache
              Downloads  and  caches metadata for enabled repositories. Tries to avoid down‐
              loading whenever possible (e.g. when the local metadata hasn't expired yet  or
              when the metadata timestamp hasn't changed).

       dnf [options] makecache --timer
              Like  plain makecache, but instructs DNF to be more resource-aware, meaning it
              will not do anything if running on battery power and  will  terminate  immedi‐
              ately  if  it's  too  soon  after  the  last  successful  makecache  run  (see
              dnf.conf(5), metadata_timer_sync).

   Mark Command
       Command: mark

       dnf mark install <package-spec>...
              Marks the specified packages as installed by user. This can be useful  if  any
              package  was  installed  as  a dependency and is desired to stay on the system
              when Autoremove Command or Remove Command along with clean_requirements_on_re‐
              move configuration option set to True is executed.

       dnf mark remove <package-spec>...
              Unmarks  the  specified  packages as installed by user. Whenever you as a user
              don't need a specific package you can mark it for removal. The  package  stays
              installed  on the system but will be removed when Autoremove Command or Remove
              Command along with clean_requirements_on_remove configuration  option  set  to
              True  is  executed. You should use this operation instead of Remove Command if
              you're not sure whether the package is a requirement of other  user  installed
              packages on the system.

       dnf mark group <package-spec>...
              Marks  the specified packages as installed by group. This can be useful if any
              package was installed as a dependency or a user and is desired to be protected
              and handled as a group member like during group remove.

   Module Command
       Command: module

       Modularity  overview  is available at man page dnf.modularity(7).  Module subcommands
       take <module-spec>... arguments that specify modules or profiles.

       dnf [options] module install <module-spec>...
              Install module profiles, including their packages.  In  case  no  profile  was
              provided,  all default profiles get installed.  Module streams get enabled ac‐
              cordingly.

              This command cannot be used for switching module streams. Use the  dnf  module
              switch-to command for that.

       dnf [options] module update <module-spec>...
              Update packages associated with an active module stream, optionally restricted
              to a profile.  If the profile_name is provided, only the  packages  referenced
              by that profile will be updated.

       dnf [options] module switch-to <module-spec>...
              Switch  to or enable a module stream, change versions of installed packages to
              versions provided by the new stream, and remove packages from the  old  stream
              that  are  no longer available. It also updates installed profiles if they are
              available for the new stream. When a profile was provided,  it  installs  that
              profile and does not update any already installed profiles.

              This  command  can be used as a stronger version of the dnf module enable com‐
              mand, which not only enables modules, but also does a distrosync to all  modu‐
              lar packages in the enabled modules.

              It  can  also be used as a stronger version of the dnf module install command,
              but it requires to specify profiles that are supposed to be installed, because
              switch-to command does not use default profiles. The switch-to command doesn't
              only install profiles, it also makes a distrosync to all modular  packages  in
              the installed module.

       dnf [options] module remove <module-spec>...
              Remove  installed module profiles, including packages that were installed with
              the dnf module install command. Will not remove packages required by other in‐
              stalled  module profiles or by other user-installed packages.  In case no pro‐
              file was provided, all installed profiles get removed.

       dnf [options] module remove --all <module-spec>...
              Remove installed module profiles, including packages that were installed  with
              the dnf module install command.  With --all option it additionally removes all
              packages whose names are provided by specified modules. Packages  required  by
              other  installed module profiles and packages whose names are also provided by
              any other module are not removed.

       dnf [options] module enable <module-spec>...
              Enable a module stream and make the stream RPMs available in the package set.

              Modular dependencies are resolved, dependencies checked and  also  recursively
              enabled.  In  case of modular dependency issue the operation will be rejected.
              To perform the action anyway please use --skip-broken option.

              This command cannot be used for switching module streams. Use the  dnf  module
              switch-to command for that.

       dnf [options] module disable <module-name>...
              Disable  a module. All related module streams will become unavailable.  Conse‐
              quently, all installed profiles will be removed and the module RPMs  will  be‐
              come  unavailable  in the package set. In case of modular dependency issue the
              operation will be rejected.  To  perform  the  action  anyway  please  use  -‐
              -skip-broken option.

       dnf [options] module reset <module-name>...
              Reset  module  state so it's no longer enabled or disabled.  Consequently, all
              installed profiles will be removed and only RPMs from the default stream  will
              be available in the package set.

       dnf [options] module provides <package-name-spec>...
              Lists  all modular packages matching <package-name-spec> from all modules (in‐
              cluding disabled), along with the modules and streams they belong to.

       dnf [options] module list [--all] [module_name...]
              Lists all module streams, their profiles and states  (enabled,  disabled,  de‐
              fault).

       dnf [options] module list --enabled [module_name...]
              Lists module streams that are enabled.

       dnf [options] module list --disabled [module_name...]
              Lists module streams that are disabled.

       dnf [options] module list --installed [module_name...]
              List module streams with installed profiles.

       dnf [options] module info <module-spec>...
              Print detailed information about given module stream.

       dnf [options] module info --profile <module-spec>...
              Print detailed information about given module profiles.

       dnf [options] module repoquery <module-spec>...
              List all available packages belonging to selected modules.

       dnf [options] module repoquery --available <module-spec>...
              List all available packages belonging to selected modules.

       dnf [options] module repoquery --installed <module-spec>...
              List all installed packages with same name like packages belonging to selected
              modules.

   Provides Command
       Command: provides
       Aliases: prov, whatprovides, wp

       dnf [options] provides <provide-spec>
              Finds the packages providing the given <provide-spec>. This is useful when one
              knows  a  filename  and wants to find what package (installed or not) provides
              this file.  The <provide-spec> is gradually looked for at following locations:

              1. The <provide-spec> is matched with all file provides of any available pack‐
                 age:

                    $ dnf provides /usr/bin/gzip
                    gzip-1.9-9.fc29.x86_64 : The GNU data compression program
                    Matched from:
                    Filename    : /usr/bin/gzip

              2. Then all provides of all available packages are searched:

                    $ dnf provides "gzip(x86-64)"
                    gzip-1.9-9.fc29.x86_64 : The GNU data compression program
                    Matched from:
                    Provide     : gzip(x86-64) = 1.9-9.fc29

              3. DNF  assumes  that the <provide-spec> is a system command, prepends it with
                 /usr/bin/, /usr/sbin/ prefixes (one at a time) and does the  file  provides
                 search  again.  For  legacy  reasons (packages that didn't do UsrMove) also
                 /bin and /sbin prefixes are being searched:

                    $ dnf provides zless
                    gzip-1.9-9.fc29.x86_64 : The GNU data compression program
                    Matched from:
                    Filename    : /usr/bin/zless

              4. If this last step also fails, DNF returns "Error: No Matches found".

              This command by default does not force a sync of expired  metadata.  See  also
              Metadata Synchronization.

   Reinstall Command
       Command: reinstall
       Aliases: rei

       dnf [options] reinstall <package-spec>...
              Installs  the specified packages, fails if some of the packages are either not
              installed or not available (i.e. there is no repository where to download  the
              same RPM).

   Remove Command
       Command: remove
       Aliases: rm
       Aliases for explicit NEVRA matching: remove-n, remove-na, remove-nevra
       Deprecated aliases: erase, erase-n, erase-na, erase-nevra

       dnf [options] remove <package-spec>...
              Removes the specified packages from the system along with any packages depend‐
              ing on the packages being removed. Each <spec> can be either a <package-spec>,
              which  specifies  a  package  directly, or a @<group-spec>, which specifies an
              (environment) group which contains it. If clean_requirements_on_remove is  en‐
              abled (the default), also removes any dependencies that are no longer needed.

       dnf [options] remove --duplicates
              Removes  older  versions of duplicate packages. To ensure the integrity of the
              system it reinstalls the newest package. In some cases the command cannot  re‐
              solve  conflicts. In such cases the dnf shell command with remove --duplicates
              and upgrade dnf-shell sub-commands could help.

       dnf [options] remove --oldinstallonly
              Removes old installonly packages, keeping only latest versions and version  of
              running kernel.

              There  are  also  a  few  specific remove commands remove-n, remove-na and re‐
              move-nevra that allow the specification of an exact argument in the NEVRA for‐
              mat.

   Remove Examples
       dnf remove acpi tito
              Remove the acpi and tito packages.

       dnf remove $(dnf repoquery --extras --exclude=tito,acpi)
              Remove  packages  not present in any repository, but don't remove the tito and
              acpi packages (they still might be removed if they depend on some of  the  re‐
              moved packages).

       Remove  older versions of duplicated packages (an equivalent of yum's package-cleanup
       --cleandups):

          dnf remove --duplicates

   Repoinfo Command
       Command: repoinfo

          An alias for the repolist command that provides more detailed information like dnf
          repolist -v.

   Repolist Command
       Command: repolist

       dnf [options] repolist [--enabled|--disabled|--all]
              Depending  on the exact command lists enabled, disabled or all known reposito‐
              ries. Lists all enabled repositories by default. Provides more detailed infor‐
              mation when -v option is used.

       This  command by default does not force a sync of expired metadata. See also Metadata
       Synchronization.

   Repoquery Command
       Command: repoquery
       Aliases: rq
       Aliases for explicit NEVRA matching: repoquery-n, repoquery-na, repoquery-nevra

       dnf [options] repoquery [<select-options>] [<query-options>] [<package-file-spec>]
              Searches available DNF repositories for selected packages and displays the re‐
              quested  information  about  them.  It  is  an equivalent of rpm -q for remote
              repositories.

       dnf [options] repoquery --groupmember <package-spec>...
              List groups that contain <package-spec>.

       dnf [options] repoquery --querytags
              Provides the list of tags recognized by the --queryformat repoquery option.

              There are also a few specific repoquery commands repoquery-n, repoquery-na and
              repoquery-nevra that allow the specification of an exact argument in the NEVRA
              format (does not affect arguments of options like --whatprovides <arg>, ...).

   Select Options
       Together with <package-file-spec>, control what packages are displayed in the output.
       If <package-file-spec> is given, limits the resulting set of packages to those match‐
       ing the specification. All packages are considered if no <package-file-spec> is spec‐
       ified.

       <package-file-spec>
              Package   specification   in   the  NEVRA  format  (name[-[epoch:]version[-re‐
              lease]][.arch]), a package provide or a file provide. See Specifying Packages.

       -a, --all
              Query all packages (for rpmquery compatibility, also a shorthand for repoquery
              '*' or repoquery without arguments).

       --arch <arch>[,<arch>...], --archlist <arch>[,<arch>...]
              Limit the resulting set only to packages of selected architectures (default is
              all architectures). In some cases the result is affected by  the  basearch  of
              the  running  system, therefore to run repoquery for an arch incompatible with
              your system use the --forcearch=<arch> option to change the basearch.

       --duplicates
              Limit the resulting set to installed duplicate  packages  (i.e.  more  package
              versions  for  the  same  name and architecture). Installonly packages are ex‐
              cluded from this set.

       --unneeded
              Limit the resulting set to leaves packages that were installed as dependencies
              so  they are no longer needed. This switch lists packages that are going to be
              removed after executing the dnf autoremove command.

       --available
              Limit the resulting set to available packages only (set by default).

       --disable-modular-filtering
              Disables filtering of modular packages, so that packages  of  inactive  module
              streams are included in the result.

       --extras
              Limit  the resulting set to packages that are not present in any of the avail‐
              able repositories.

       -f <file>, --file <file>
              Limit the resulting set only to the package that owns <file>.

       --installed
              Limit the resulting set to installed packages only. The exclude option in  the
              configuration  file might influence the result, but if the command line option
              --disableexcludes is used, it ensures that  all  installed  packages  will  be
              listed.

       --installonly
              Limit the resulting set to installed installonly packages.

       --latest-limit <number>
              Limit  the resulting set to <number> of latest packages for every package name
              and architecture.  If <number> is negative, skip <number> of latest  packages.
              For a negative <number> use the --latest-limit=<number> syntax.

       --recent
              Limit the resulting set to packages that were recently edited.

       --repo <repoid>
              Limit  the resulting set only to packages from a repository identified by <re‐
              poid>.  Can be used multiple times with accumulative effect.

       --unsatisfied
              Report unsatisfied dependencies among installed  packages  (i.e.  missing  re‐
              quires and existing conflicts).

       --upgrades
              Limit  the  resulting set to packages that provide an upgrade for some already
              installed package.

       --userinstalled
              Limit the resulting set to packages installed by the user. The exclude  option
              in  the configuration file might influence the result, but if the command line
              option  --disableexcludes is used, it ensures that all installed packages will
              be listed.

       --whatdepends <capability>[,<capability>...]
              Limit  the  resulting  set  only to packages that require, enhance, recommend,
              suggest or supplement any of <capabilities>.

       --whatconflicts <capability>[,<capability>...]
              Limit the resulting set only to packages that conflict with any of  <capabili‐
              ties>.

       --whatenhances <capability>[,<capability>...]
              Limit  the  resulting set only to packages that enhance any of <capabilities>.
              Use --whatdepends if you want to list all depending packages.

       --whatobsoletes <capability>[,<capability>...]
              Limit the resulting set only to packages that obsolete any of <capabilities>.

       --whatprovides <capability>[,<capability>...]
              Limit the resulting set only to packages that provide any of <capabilities>.

       --whatrecommends <capability>[,<capability>...]
              Limit the resulting set only to packages that recommend any of <capabilities>.
              Use --whatdepends if you want to list all depending packages.

       --whatrequires <capability>[,<capability>...]
              Limit  the  resulting set only to packages that require any of <capabilities>.
              Use --whatdepends if you want to list all depending packages.

       --whatsuggests <capability>[,<capability>...]
              Limit the resulting set only to packages that suggest any  of  <capabilities>.
              Use --whatdepends if you want to list all depending packages.

       --whatsupplements <capability>[,<capability>...]
              Limit  the  resulting  set  only to packages that supplement any of <capabili‐
              ties>. Use --whatdepends if you want to list all depending packages.

       --alldeps
              This option is stackable with --whatrequires or --whatdepends only.  Addition‐
              ally  it  adds  all  packages requiring the package features to the result set
              (used as default).

       --exactdeps
              This option is stackable with --whatrequires or --whatdepends only. Limit  the
              resulting  set  only to packages that require <capability> specified by --wha‐
              trequires.

       --srpm Operate on the corresponding source RPM.

   Query Options
       Set what information is displayed about each package.

       The following are mutually exclusive, i.e. at most one can be specified. If no  query
       option is given, matching packages are displayed in the standard NEVRA notation.

       -i, --info
              Show detailed information about the package.

       -l, --list
              Show the list of files in the package.

       -s, --source
              Show the package source RPM name.

       --changelogs
              Print the package changelogs.

       --conflicts
              Display  capabilities  that  the  package conflicts with. Same as --qf "%{con‐
              flicts}.

       --depends
              Display capabilities that the package depends on, enhances,  recommends,  sug‐
              gests or supplements.

       --enhances
              Display capabilities enhanced by the package. Same as --qf "%{enhances}"".

       --location
              Show a location where the package could be downloaded from.

       --obsoletes
              Display capabilities that the package obsoletes. Same as --qf "%{obsoletes}".

       --provides
              Display capabilities provided by the package. Same as --qf "%{provides}".

       --recommends
              Display capabilities recommended by the package. Same as --qf "%{recommends}".

       --requires
              Display capabilities that the package depends on. Same as --qf "%{requires}".

       --requires-pre
              Display  capabilities  that  the package depends on for running a %pre script.
              Same as --qf "%{requires-pre}".

       --suggests
              Display capabilities suggested by the package. Same as --qf "%{suggests}".

       --supplements
              Display capabilities supplemented by the  package.  Same  as  --qf  "%{supple‐
              ments}".

       --tree Display a recursive tree of packages with capabilities specified by one of the
              following  supplementary  options:  --whatrequires,  --requires,  --conflicts,
              --enhances, --suggests, --provides, --supplements, --recommends.

       --deplist
              Produce  a list of all direct dependencies and what packages provide those de‐
              pendencies for the given packages. The result only shows the newest  providers
              (which can be changed by using --verbose).

       --nvr  Show   found  packages  in  the  name-version-release  format.  Same  as  --qf
              "%{name}-%{version}-%{release}".

       --nevra
              Show found packages  in  the  name-epoch:version-release.architecture  format.
              Same as --qf "%{name}-%{epoch}:%{version}-%{release}.%{arch}" (default).

       --envra
              Show  found  packages  in  the epoch:name-version-release.architecture format.
              Same as --qf "%{epoch}:%{name}-%{version}-%{release}.%{arch}"

       --qf <format>, --queryformat <format>
              Custom display format. <format> is the string to output for each matched pack‐
              age.  Every occurrence of %{<tag>} within is replaced by the corresponding at‐
              tribute of the package. The list of recognized tags can be displayed  by  run‐
              ning dnf repoquery --querytags.

       --recursive
              Query  packages recursively. Has to be used with --whatrequires <REQ> (option‐
              ally with --alldeps, but not with --exactdeps) or with --requires <REQ>  --re‐
              solve.

       --resolve
              resolve capabilities to originating package(s).

   Examples
       Display NEVRAs of all available packages matching light*:

          dnf repoquery 'light*'

       Display NEVRAs of all available packages matching name light* and architecture noarch
       (accepts only arguments in the "<name>.<arch>" format):

          dnf repoquery-na 'light*.noarch'

       Display requires of all lighttpd packages:

          dnf repoquery --requires lighttpd

       Display packages providing the requires of python packages:

          dnf repoquery --requires python --resolve

       Display source rpm of ligttpd package:

          dnf repoquery --source lighttpd

       Display package name that owns the given file:

          dnf repoquery --file /etc/lighttpd/lighttpd.conf

       Display name, architecture and the containing repository of all lighttpd packages:

          dnf repoquery --queryformat '%{name}.%{arch} : %{reponame}' lighttpd

       Display all available packages providing "webserver":

          dnf repoquery --whatprovides webserver

       Display all available packages providing "webserver" but only  for  "i686"  architec‐
       ture:

          dnf repoquery --whatprovides webserver --arch i686

       Display duplicate packages:

          dnf repoquery --duplicates

       Display source packages that require a <provide> for a build:

          dnf repoquery --disablerepo="*" --enablerepo="*-source" --arch=src --whatrequires <provide>

   Repository-Packages Command
       Command: repository-packages
       Deprecated aliases: repo-pkgs, repo-packages, repository-pkgs

       The  repository-packages  command allows the user to run commands on top of all pack‐
       ages in the repository named <repoid>. However, any dependency resolution takes  into
       account  packages  from  all enabled repositories. The <package-file-spec> and <pack‐
       age-spec> specifications further limit the candidates to only those packages matching
       at least one of them.

       The  info subcommand lists description and summary information about packages depend‐
       ing on the packages' relation to the repository.  The  list  subcommand  just  prints
       lists of those packages.

       dnf [options] repository-packages <repoid> check-update [<package-file-spec>...]
              Non-interactively  checks  if updates of the specified packages in the reposi‐
              tory are available. DNF exit code will be 100 when there are updates available
              and a list of the updates will be printed.

       dnf [options] repository-packages <repoid> info [--all] [<package-file-spec>...]
              List all related packages.

       dnf [options] repository-packages <repoid> info --installed [<package-file-spec>...]
              List packages installed from the repository.

       dnf [options] repository-packages <repoid> info --available [<package-file-spec>...]
              List  packages  available in the repository but not currently installed on the
              system.

       dnf [options] repository-packages <repoid> info --extras [<package-file-specs>...]
              List packages installed from the repository that  are  not  available  in  any
              repository.

       dnf [options] repository-packages <repoid> info --obsoletes [<package-file-spec>...]
              List  packages  in the repository that obsolete packages installed on the sys‐
              tem.

       dnf [options] repository-packages <repoid> info --recent [<package-file-spec>...]
              List packages recently added into the repository.

       dnf [options] repository-packages <repoid> info --upgrades [<package-file-spec>...]
              List packages in the repository that upgrade packages installed on the system.

       dnf [options] repository-packages <repoid> install [<package-spec>...]
              Install packages  matching  <package-spec>  from  the  repository.  If  <pack‐
              age-spec> isn't specified at all, install all packages from the repository.

       dnf [options] repository-packages <repoid> list [--all] [<package-file-spec>...]
              List all related packages.

       dnf [options] repository-packages <repoid> list --installed [<package-file-spec>...]
              List packages installed from the repository.

       dnf [options] repository-packages <repoid> list --available [<package-file-spec>...]
              List  packages  available in the repository but not currently installed on the
              system.

       dnf [options] repository-packages <repoid> list --extras [<package-file-spec>...]
              List packages installed from the repository that  are  not  available  in  any
              repository.

       dnf [options] repository-packages <repoid> list --obsoletes [<package-file-spec>...]
              List  packages  in the repository that obsolete packages installed on the sys‐
              tem.

       dnf [options] repository-packages <repoid> list --recent [<package-file-spec>...]
              List packages recently added into the repository.

       dnf [options] repository-packages <repoid> list --upgrades [<package-file-spec>...]
              List packages in the repository that upgrade packages installed on the system.

       dnf [options] repository-packages <repoid> move-to [<package-spec>...]
              Reinstall all those packages that are available in the repository.

       dnf [options] repository-packages <repoid> reinstall [<package-spec>...]
              Run the reinstall-old subcommand. If it fails, run the move-to subcommand.

       dnf [options] repository-packages <repoid> reinstall-old [<package-spec>...]
              Reinstall all those packages that were installed from the repository  and  si‐
              multaneously are available in the repository.

       dnf [options] repository-packages <repoid> remove [<package-spec>...]
              Remove  all packages installed from the repository along with any packages de‐
              pending on the packages being removed. If clean_requirements_on_remove is  en‐
              abled (the default) also removes any dependencies that are no longer needed.

       dnf [options] repository-packages <repoid> remove-or-distro-sync [<package-spec>...]
              Select  all packages installed from the repository. Upgrade, downgrade or keep
              those of them that are available in another repository  to  match  the  latest
              version  available there and remove the others along with any packages depend‐
              ing on the packages being removed. If clean_requirements_on_remove is  enabled
              (the default) also removes any dependencies that are no longer needed.

       dnf [options] repository-packages <repoid> remove-or-reinstall [<package-spec>...]
              Select  all  packages  installed  from the repository. Reinstall those of them
              that are available in another repository and remove the others along with  any
              packages depending on the packages being removed. If clean_requirements_on_re‐
              move is enabled (the default) also removes any dependencies that are no longer
              needed.

       dnf [options] repository-packages <repoid> upgrade [<package-spec>...]
              Update all packages to the highest resolvable version available in the reposi‐
              tory.  When versions are specified in the <package-spec>, update to these ver‐
              sions.

       dnf [options] repository-packages <repoid> upgrade-to [<package-specs>...]
              A deprecated alias for the upgrade subcommand.

   Search Command
       Command: search
       Aliases: se

       dnf [options] search [--all] <keywords>...
              Search package metadata for keywords. Keywords are matched as case-insensitive
              substrings, globbing is supported.  By default lists packages that  match  all
              requested  keys  (AND  operation). Keys are searched in package names and sum‐
              maries.  If the "--all" option is used, lists packages that match at least one
              of the keys (an OR operation).  In addition the keys are searched in the pack‐
              age descriptions and URLs.  The result is sorted from the  most  relevant  re‐
              sults to the least.

       This  command by default does not force a sync of expired metadata. See also Metadata
       Synchronization.

   Shell Command
       Command: shell
       Aliases: sh

       dnf [options] shell [filename]
              Open an interactive shell for conducting multiple commands during a single ex‐
              ecution  of DNF. These commands can be issued manually or passed to DNF from a
              file. The commands are much the same as the normal DNF command  line  options.
              There are a few additional commands documented below.

              config [conf-option] [value]

                     • Set a configuration option to a requested value. If no value is given
                       it prints the current value.

              repo [list|enable|disable] [repo-id]

                     • list: list repositories and their status

                     • enable: enable repository

                     • disable: disable repository

              transaction [list|reset|solve|run]

                     • list: resolve and list the content of the transaction

                     • reset: reset the transaction

                     • run: resolve and run the transaction

              Note that all local packages must be used in the first shell transaction  sub‐
              command  (e.g.   install  /tmp/nodejs-1-1.x86_64.rpm /tmp/acpi-1-1.noarch.rpm)
              otherwise an error will occur.  Any disable, enable, and reset  module  opera‐
              tions  (e.g.  module  enable  nodejs)  must also be performed before any other
              shell transaction subcommand is used.

   Swap Command
       Command: swap

       dnf [options] swap <remove-spec> <install-spec>
          Remove spec and install spec in one transaction.  Each  <spec>  can  be  either  a
          <package-spec>,  which  specifies  a  package  directly, or a @<group-spec>, which
          specifies an (environment) group which contains it. Automatic conflict solving  is
          provided  in  DNF  by the --allowerasing option that provides the functionality of
          the swap command automatically.

   Updateinfo Command
       Command: updateinfo
       Aliases: upif
       Deprecated aliases: list-updateinfo, list-security, list-sec, info-updateinfo, info-security, info-sec, summary-updateinfo

       dnf [options] updateinfo [--summary|--list|--info] [<availability>] [<spec>...]
              Display information about update advisories.

              Depending on the output type, DNF  displays  just  counts  of  advisory  types
              (omitted  or  --summary),  list of advisories (--list) or detailed information
              (--info). The -v option extends the output. When used with --info, the  infor‐
              mation is even more detailed. When used with --list, an additional column with
              date of the last advisory update is added.

              <availability> specifies whether advisories about newer versions of  installed
              packages  (omitted  or --available), advisories about equal and older versions
              of installed packages (--installed), advisories about newer versions of  those
              installed packages for which a newer version is available (--updates) or advi‐
              sories about any versions of installed packages (--all)  are  taken  into  ac‐
              count.  Most  of the time, --available and --updates displays the same output.
              The outputs differ only in the cases when an advisory refers to a  newer  ver‐
              sion but there is no enabled repository which contains any newer version.

              Note,  that  --available  takes only the latest installed versions of packages
              into account. In case of the kernel packages (when multiple version  could  be
              installed  simultaneously)  also  packages of the currently running version of
              kernel are added.

              To print only advisories referencing a CVE or a  bugzilla  use  --with-cve  or
              --with-bz  options. When these switches are used also the output of the --list
              is altered - the ID of the CVE or the bugzilla is printed instead of  the  one
              of the advisory.

              If  given  and  if  neither ID, type (bugfix, enhancement, security/sec) nor a
              package name of an advisory matches <spec>, the advisory is not taken into ac‐
              count.  The  matching  is  case-sensitive  and in the case of advisory IDs and
              package names, globbing is supported.

              Output of the --summary option is  affected  by  the  autocheck_running_kernel
              configuration option.

   Upgrade Command
       Command: upgrade
       Aliases: up
       Deprecated aliases: update, upgrade-to, update-to, localupdate

       dnf [options] upgrade
              Updates  each package to the latest version that is both available and resolv‐
              able.

       dnf [options] upgrade <package-spec>...
              Updates each specified package to the latest available version. Updates depen‐
              dencies  as  necessary. When versions are specified in the <package-spec>, up‐
              date to these versions.

       dnf [options] upgrade @<spec>...
              Alias for the dnf module update command.

       If the main obsoletes configure option is true or the --obsoletes  flag  is  present,
       dnf will include package obsoletes in its calculations.  For more information see ob‐
       soletes.

       See also Configuration Files Replacement Policy.

   Upgrade-Minimal Command
       Command: upgrade-minimal
       Aliases: up-min
       Deprecated aliases: update-minimal

       dnf [options] upgrade-minimal
              Updates each package to the latest available version that provides  a  bugfix,
              enhancement or a fix for a security issue (security).

       dnf [options] upgrade-minimal <package-spec>...
              Updates each specified package to the latest available version that provides a
              bugfix, enhancement or a fix for security issue (security). Updates  dependen‐
              cies as necessary.

SPECIFYING PACKAGES
       Many  commands  take a <package-spec> parameter that selects a package for the opera‐
       tion. The <package-spec> argument is matched against  package  NEVRAs,  provides  and
       file provides.

       <package-file-spec>  is  similar  to  <package-spec>, except provides matching is not
       performed. Therefore, <package-file-spec> is matched only  against  NEVRAs  and  file
       provides.

       <package-name-spec> is matched against NEVRAs only.

   Globs
       Package specification supports the same glob pattern matching that shell does, in all
       three above mentioned packages it matches against (NEVRAs,  provides  and  file  pro‐
       vides).

       The following patterns are supported:

       *      Matches any number of characters.

       ?      Matches any single character.

       []     Matches  any one of the enclosed characters. A pair of characters separated by
              a hyphen denotes a range expression; any character that  falls  between  those
              two  characters, inclusive, is matched. If the first character following the [
              is a ! or a ^ then any character not enclosed is matched.

       Note: Curly brackets ({}) are not supported. You can still use them  in  shells  that
       support  them  and let the shell do the expansion, but if quoted or escaped, dnf will
       not expand them.

   NEVRA Matching
       When matching against NEVRAs, partial matching is supported. DNF tries to  match  the
       spec against the following list of NEVRA forms (in decreasing order of priority):

       • name-[epoch:]version-release.arch

       • name.arch

       • name

       • name-[epoch:]version-release

       • name-[epoch:]version

       Note that name can in general contain dashes (e.g. package-with-dashes).

       The  first  form  that  matches  any packages is used and the remaining forms are not
       tried. If none of the forms match any packages, an  attempt  is  made  to  match  the
       <package-spec>  against  full  package  NEVRAs.  This  is  only relevant if globs are
       present in the <package-spec>.

       <package-spec> matches NEVRAs the same way  <package-name-spec>  does,  but  in  case
       matching  NEVRAs  fails,  it  attempts to match against provides and file provides of
       packages as well.

       You can specify globs as part of any of the five NEVRA components. You can also spec‐
       ify  a glob pattern to match over multiple NEVRA components (in other words, to match
       across the NEVRA separators). In that case, however, you need to write  the  spec  to
       match  against  full  package  NEVRAs,  as it is not possible to split such spec into
       NEVRA forms.

   Specifying NEVRA Matching Explicitly
       Some commands (autoremove, install, remove and repoquery) also have aliases with suf‐
       fixes -n, -na and -nevra that allow to explicitly specify how to parse the arguments:

       • Command install-n only matches against name.

       • Command install-na only matches against name.arch.

       • Command install-nevra only matches against name-[epoch:]version-release.arch.

SPECIFYING PROVIDES
       <provide-spec> in command descriptions means the command operates on packages provid‐
       ing the given spec. This can either be an explicit provide, an implicit provide (i.e.
       name  of the package) or a file provide. The selection is case-sensitive and globbing
       is supported.

   Specifying File Provides
       If a spec starts with either / or */, it is considered as a potential file provide.

SPECIFYING GROUPS
       <group-spec> allows one to select (environment) groups a particular operation  should
       work  on.  It  is  a case insensitive string (supporting globbing characters) that is
       matched against a group's ID, canonical name and name  translated  into  the  current
       LC_MESSAGES locale (if possible).

SPECIFYING MODULES
       <module-spec>  allows one to select modules or profiles a particular operation should
       work on.

       It is in the form of NAME:STREAM:VERSION:CONTEXT:ARCH/PROFILE and  supported  partial
       forms are the following:

       • NAME

       • NAME:STREAM

       • NAME:STREAM:VERSION

       • NAME:STREAM:VERSION:CONTEXT

       • all above combinations with ::ARCH (e.g. NAME::ARCH)

       • NAME:STREAM:VERSION:CONTEXT:ARCH

       • all above combinations with /PROFILE (e.g. NAME/PROFILE)

       In  case  stream is not specified, the enabled or the default stream is used, in this
       order. In case profile is not specified, the system default profile or the  'default'
       profile is used.

SPECIFYING TRANSACTIONS
       <transaction-spec>  can be in one of several forms. If it is an integer, it specifies
       a transaction ID. Specifying last is the same as specifying the ID of the most recent
       transaction. The last form is last-<offset>, where <offset> is a positive integer. It
       specifies offset-th transaction preceding the most recent transaction.

PACKAGE FILTERING
       Package filtering filters packages out from the available package  set,  making  them
       invisible to most of dnf commands. They cannot be used in a transaction. Packages can
       be filtered out by either Exclude Filtering or Modular Filtering.

   Exclude Filtering
       Exclude Filtering is a mechanism used by a user or by a DNF plugin to modify the  set
       of available packages. Exclude Filtering can be modified by either includepkgs or ex‐
       cludepkgs configuration options in configuration files. The --disableexcludes command
       line option can be used to override excludes from configuration files. In addition to
       user-configured excludes, plugins can also extend the set of  excluded  packages.  To
       disable  excludes  from a DNF plugin you can use the --disableplugin command line op‐
       tion.

       To disable all excludes for e.g. the install command you can use the following combi‐
       nation of command line options:

       dnf --disableexcludes=all --disableplugin="*" install bash

   Modular Filtering
       Please see the modularity documentation for details on how Modular Filtering works.

       With  modularity,  only  RPM  packages from active module streams are included in the
       available package set. RPM packages from inactive module streams, as well as non-mod‐
       ular  packages  with  the  same  name  or provides as a package from an active module
       stream, are filtered out. Modular filtering is not applied to packages added from the
       command  line,  installed  packages,  or  packages from repositories with module_hot‐
       fixes=true in their .repo file.

       Disabling of modular filtering is not recommended, because it could cause the  system
       to get into a broken state. To disable modular filtering for a particular repository,
       specify module_hotfixes=true in the .repo file or use  --setopt=<repo_id>.module_hot‐
       fixes=true.

       To discover the module which contains an excluded package use dnf module provides.

METADATA SYNCHRONIZATION
       Correct operation of DNF depends on having access to up-to-date data from all enabled
       repositories but contacting remote mirrors on every operation considerably  slows  it
       down  and  costs bandwidth for both the client and the repository provider. The meta‐
       data_expire (see dnf.conf(5)) repository configuration option is used by DNF  to  de‐
       termine whether a particular local copy of repository data is due to be re-synced. It
       is crucial that the repository providers set the option well, namely to a value where
       it  is  guaranteed that if particular metadata was available in time T on the server,
       then all packages it references will still be available for download from the  server
       in time T + metadata_expire.

       To  further  reduce  the bandwidth load, some of the commands where having up-to-date
       metadata is not critical (e.g. the list command) do not look at whether a  repository
       is expired and whenever any version of it is locally available to the user's account,
       it will be used. For non-root use, see also the --cacheonly switch. Note that in  all
       situations  the  user  can force synchronization of all enabled repositories with the
       --refresh switch.

CONFIGURATION FILES REPLACEMENT POLICY
       The updated packages could replace the old modified configuration files with the  new
       ones  or  keep  the  older files. Neither of the files are actually replaced.  To the
       conflicting ones RPM gives additional suffix to the origin name.  Which  file  should
       maintain  the true name after transaction is not controlled by package manager but is
       specified by each package itself, following packaging guideline.

FILES
       Cache Files
              /var/cache/dnf

       Main Configuration
              /etc/dnf/dnf.conf

       Repository
              /etc/yum.repos.d/

SEE ALSO
       • dnf.conf(5), DNF Configuration Reference

       • dnf-PLUGIN(8) for documentation on DNF plugins.

       • dnf.modularity(7), Modularity overview.

       • dnf-transaction-json(5), Stored Transaction JSON Format Specification.

       • DNF project homepage (https://github.com/rpm-software-management/dnf/)

       • How             to             report             a             bug              (‐
         https://github.com/rpm-software-management/dnf/wiki/Bug-Reporting)

       • YUM project homepage (http://yum.baseurl.org/)

AUTHOR
       See AUTHORS in DNF source distribution.

COPYRIGHT
       2012-2023, Red Hat, Licensed under GPLv2+

4.14.0                                  Jun 28, 2023                                  YUM(8)

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908