..

  Copyright (C) 2014-2018 Red Hat, Inc.

  This copyrighted material is made available to anyone wishing to use,

  modify, copy, or redistribute it subject to the terms and conditions of

  the GNU General Public License v.2, or (at your option) any later version.

  This program is distributed in the hope that it will be useful, but WITHOUT

  ANY WARRANTY expressed or implied, including the implied warranties of

  MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General

  Public License for more details.  You should have received a copy of the

  GNU General Public License along with this program; if not, write to the

  Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA

  02110-1301, USA.  Any Red Hat trademarks that are incorporated in the

  source code or documentation are not subject to the GNU General Public

  License and may only be used or replicated with the express permission of

  Red Hat, Inc.

.. _command_ref-label:

#######################

 DNF Command Reference

#######################

========

Synopsis

========

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

===========

Description

===========

.. _command_provides-label:

`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 commands 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 ``versionlock`` plugin. This approach also applies to

specifying dependencies of packages that require a particular DNF command.

.. _exit_codes-label:

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 :ref:`check-update <check_update_command-label>`

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

Available commands:

* :ref:`alias <alias_command-label>`

* :ref:`autoremove <autoremove_command-label>`

* :ref:`check <check_command-label>`

* :ref:`check-update <check_update_command-label>`

* :ref:`clean <clean_command-label>`

* :ref:`deplist <deplist_command-label>`

* :ref:`distro-sync <distro_sync_command-label>`

* :ref:`downgrade <downgrade_command-label>`

* :ref:`group <group_command-label>`

* :ref:`help <help_command-label>`

* :ref:`history <history_command-label>`

* :ref:`info <info_command-label>`

* :ref:`install <install_command-label>`

* :ref:`list <list_command-label>`

* :ref:`makecache <makecache_command-label>`

* :ref:`mark <mark_command-label>`

* :ref:`module <module_command-label>`

* :ref:`provides <provides_command-label>`

* :ref:`reinstall <reinstall_command-label>`

* :ref:`remove <remove_command-label>`

* :ref:`repoinfo <repoinfo_command-label>`

* :ref:`repolist <repolist_command-label>`

* :ref:`repoquery <repoquery_command-label>`

* :ref:`repository-packages <repository_packages_command-label>`

* :ref:`search <search_command-label>`

* :ref:`shell <shell_command-label>`

* :ref:`swap <swap_command-label>`

* :ref:`updateinfo <updateinfo_command-label>`

* :ref:`upgrade <upgrade_command-label>`

* :ref:`upgrade-minimal <upgrade_minimal_command-label>`

Additional information:

* :ref:`Options <options-label>`

* :ref:`Specifying Packages <specifying_packages-label>`

* :ref:`Specifying Provides <specifying_provides-label>`

* :ref:`Specifying Groups <specifying_groups-label>`

* :ref:`Specifying Transactions <specifying_transactions-label>`

* :ref:`Metadata Synchronization <metadata_synchronization-label>`

* :ref:`Configuration Files Replacement Policy <configuration_files_replacement_policy-label>`

* :ref:`Files <files-label>`

* :ref:`See Also <see_also-label>`

.. _options-label:

=======

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.

    Applicable for the install, repoquery, updateinfo and upgrade 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 :ref:`dnf upgrade <upgrade_command-label>`, which by default skips over updates that can not be installed for dependency reasons, the switch forces DNF to only consider the latest packages. When running into packages with broken dependencies, DNF will fail giving a reason why the latest version can not be installed.

``--bugfix``

    Include packages that fix a bugfix issue. Applicable for the install, repoquery, updateinfo and

    upgrade commands.

``--bz=<bugzilla>, --bzs=<bugzilla>``

    Include packages that fix a Bugzilla ID, Eg. 123123. Applicable for the install, repoquery,

    updateinfo and upgrade 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,

    and upgrade commands.

``-d <debug level>, --debuglevel=<debug level>``

    Debugging output level. This is an integer value between 0 (no additional information strings) and 10 (shows all debugging information, even that not understandable to the user), default is 2. Deprecated, use ``-v`` instead.

``--debugsolver``

    Dump data aiding in dependency solver debugging into ``./debugdata``.

.. _disableexcludes-label:

``--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-label:

``--disableplugin=<plugin names>``

    Disable the listed plugins specified by names or globs.

``--disablerepo=<repoid>``

    Disable specific repositories by an id or a glob. This option is mutually exclusive with ``--repo``.

``--downloaddir=<path>, --destdir=<path>``

    Redirect downloaded packages to provided directory. The option has to be used together with the \-\

    :ref:`-downloadonly <downloadonly-label>` command line option, with the

    ``download`` command (dnf-plugins-core) or with the ``system-upgrade`` command

    (dnf-plugins-extras).

.. _downloadonly-label:

``--downloadonly``

    Download the resolved package set without performing any rpm transaction (install/upgrade/erase).

``-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>``

    Enable additional repositories by an id or a glob.

``--enhancement``

    Include enhancement relevant packages. Applicable for the install, repoquery, updateinfo and

    upgrade commands.

.. _exclude_option-label:

``-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 \-\ :ref:`-exclude <exclude_option-label>` 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 emulation of some kind. This is usually through QEMU. The behavior of ``--forcearch``

    can be configured by using the :ref:`arch <arch-label>` and :ref:`ignorearch <ignorearch-label>`

    configuration options with values ``<arch>`` and ``True`` respectively.

``-h, --help, --help-cmd``

    Show the help.

.. _installroot-label:

``--installroot=<path>``

    Specifies an alternative installroot, relative to where all packages will be

    installed. Think of this like doing ``chroot <root> dnf``, except using

    ``--installroot`` 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 installroot. *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 :ref:`reposdir <reposdir-label>` are searched inside the installroot first. If

  they are not present, they are taken from the host system.

  Note:  When a path is specified within a command line argument

  (``--config=<config file>`` in case of *configuration 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 :ref:`reposdir <reposdir-label>`

  . When *reposdir* path is specified within a command line argument, vars are taken from the

  installroot. When :ref:`varsdir <varsdir_options-label>` paths are specified within a command line

  argument (``--setopt=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=<module_platform_name:stream>`` command-line option when creating the installroot,

 otherwise the :ref:`module_platform_id <module_platform_id-label>` 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>`` directory 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 and

    upgrade commands.

``--noautoremove``

    Disable removal of dependencies that are no longer used. It sets

    :ref:`clean_requirements_on_remove <clean_requirements_on_remove-label>` configuration option to ``False``.

``--nobest``

    Set best option to ``False``, so that transactions are not limited to best candidates 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_option-label:

``--obsoletes``

    This option has an effect on an install/update, it enables

    dnf's obsoletes processing logic. For more information see the

    :ref:`obsoletes <obsoletes_conf_option-label>` option.

    This option also displays capabilities that the package obsoletes when used together with the :ref:`repoquery <repoquery_command-label>` command.

    Configuration Option: :ref:`obsoletes <obsoletes_conf_option-label>`

``-q, --quiet``

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

``-R <minutes>, --randomwait=<minutes>``

    Maximum command wait time.

.. _refresh_command-label:

``--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_options-label:

``--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

  :ref:`repo variables <repo-variables-label>`.

- The configuration for the repository can be adjusted using \-\

  :ref:`-setopt <setopt_option-label>`\=<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

    ``--disablerepo="*" --enablerepo=<repoid>`` and is mutually exclusive with

    the ``--disablerepo`` 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 and upgrade commands.

``--security``

    Includes packages that provide a fix for a security issue. Applicable for the

    upgrade command.

.. _setopt_option-label:

``--setopt=<option>=<value>``

    Override a configuration option from the configuration file. To override configuration options for repositories, use

    ``repoid.option`` for the ``<option>``. Values for configuration options like ``excludepkgs``, ``includepkgs``,

    ``installonlypkgs`` and ``tsflags`` are appended to the original value, they do not override it. However, specifying

    an empty value (e.g. ``--setopt=tsflags=``) will clear the option.

.. _skip-broken_option-label:

``--skip-broken``

    Resolve depsolve problems by removing packages that are causing problems from the transaction.

    It is an alias for the :ref:`strict <strict-label>` configuration option with value ``False``.

    Additionally, with the :ref:`enable <module_enable_command-label>` and

    :ref:`disable <module_disable_command-label>` 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.

.. _verbose_options-label:

``-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

:ref:`\specifying_packages-label`.

For an explanation of ``<provide-spec>`` see :ref:`\specifying_provides-label`.

For an explanation of ``<group-spec>`` see :ref:`\specifying_groups-label`.

For an explanation of ``<module-spec>`` see :ref:`\specifying_modules-label`.

For an explanation of ``<transaction-spec>`` see :ref:`\specifying_transactions-label`.

.. _alias_command-label:

-------------

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 :ref:`\Alias Examples\ <alias_examples-label>`. For examples on the alias

processing, see :ref:`\Alias Processing Examples\ <alias_processing_examples-label>`.

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 alphabetical 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-label:

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-label:

Alias Processing Examples

-------------------------

If there are defined aliases ``in=install`` and ``FORCE="--skip-broken --disableexcludes=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-label:

------------------

Autoremove Command

------------------

| Command: ``autoremove``

| Aliases for :ref:`explicit NEVRA matching <specifying_nevra_matching_explicitly-label>`: ``autoremove-n``, ``autoremove-na``, ``autoremove-nevra``

``dnf [options] autoremove``

    Removes all "leaf" packages from the system that were originally installed as dependencies of user-installed packages, but which are no longer required by any such package.

Packages listed in :ref:`installonlypkgs <installonlypkgs-label>` are never automatically removed by

this command.

``dnf [options] autoremove <spec>...``

    This is an alias for the :ref:`\remove_command-label` 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 dependencies 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 :ref:`\metadata_synchronization-label`.

.. _check_command-label:

-------------

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-label:

--------------------

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 package (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 dependencies being satisfied) to take into account.

    The output is affected by the :ref:`autocheck_running_kernel <autocheck_running_kernel-label>` configuration option.

.. _clean_command-label:

-------------

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 distribution 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-label:

---------------

Deplist Command

---------------

``dnf [options] deplist [<select-options>] [<query-options>] [<package-spec>]``

    Alias for :ref:`dnf repoquery --deplist <deplist_option-label>`.

.. _distro_sync_command-label:

-------------------

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 :ref:`\configuration_files_replacement_policy-label`.

.. _downgrade_command-label:

-----------------

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 version of installed package then it

    downgrades to target version.

.. _group_command-label:

-------------

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 subcommand.

``dnf [options] group info <group-spec>``

    Display package lists of a group. Shows which packages are installed or

    available 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

    include `optional` packages of the group if ``--with-optional`` is

    specified. All `mandatory` and `Default` packages will be installed whenever possible.

    Conditional 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 :ref:`obsoletes configuration option <obsoletes_conf_option-label>` group installation takes obsoletes into account.

.. _grouplist_command-label:

``dnf [options] group list <group-spec>...``

    List all matching groups, either among installed or available groups. If

    nothing 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 option ``--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 explicitly 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 distribution 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 command, 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 :ref:`\configuration_files_replacement_policy-label`.

.. _help_command-label:

------------

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-label:

---------------

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 option is set).

.. _history_list_command-label:

``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 specifies a range of transactions, or a ``<package-name-spec>``,

    which specifies a transaction by a package which it manipulated. When no

    transaction is specified, list all known transactions.

    ``--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 :ref:`History List Command <history_list_command-label>`. When no

    transaction is specified, describe what happened during the latest

    transaction.

.. _history_redo_command-label:

``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.

.. _history_replay_command-label:

``dnf history replay [--ignore-installed] [--ignore-extras] [--skip-unavailable] <filename>``

    Replay a transaction stored in file ``<filename>`` by :ref:`History Store

    Command <history_store_command-label>`. The replay will perform the exact

    same operations on the packages as in the original transaction and will

    return with an error if case of any differences in installed packages or

    their versions. See also the :ref:`Transaction JSON Format specification <transaction_json-label>` 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

        target 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.

.. _history_store_command-label:

``dnf history store [--output <output-file>] <transaction-spec>``

    Store a transaction specified by ``<transaction-spec>``. The transaction

    can later be replayed by the :ref:`History Replay Command

    <history_replay_command-label>`.

    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 replay (or between versions as long as it stays the same).

    ``-o <output-file>, --output=<output-file>``

    Store the serialized transaction into ``

``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 system when

    :ref:`\autoremove_command-label` or :ref:`\remove_command-label` along with

    `clean_requirements_on_remove` configuration option set to True is executed. Note the same

    results can be accomplished with ``dnf repoquery --userinstalled``, and the repoquery

    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 :ref:`\metadata_synchronization-label`

and :ref:`\configuration_files_replacement_policy-label`.

.. _info_command-label:

------------

Info Command

------------

| Command: ``info``

``dnf [options] info [<package-file-spec>...]``

    Lists description and summary information about installed and available packages.

The info command limits the displayed packages the same way as the :ref:`list command<list_command-label>`.

This command by default does not force a sync of expired metadata. See also :ref:`\metadata_synchronization-label`.

.. _install_command-label:

---------------

Install Command

---------------

| Command: ``install``

| Aliases: ``in``

| Aliases for :ref:`explicit NEVRA matching <specifying_nevra_matching_explicitly-label>`: ``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 :ref:`<package-spec> <specifying_packages-label>`,

    or a \@\ :ref:`\<module-spec>\ <specifying_modules-label>`, or a \@\ :ref:`\<group-spec>\ <specifying_groups-label>`.

    See :ref:`\Install Examples\ <install_examples-label>`.

    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 \@\ :ref:`\<module-spec>\ <specifying_modules-label>` and

    a \@\ :ref:`\<group-spec>\ <specifying_groups-label>`, only the module is installed.

    When :ref:`<package-spec> <specifying_packages-label>` 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.

    There are also a few specific install commands ``install-n``, ``install-na`` and

    ``install-nevra`` that allow the specification of an exact argument in the NEVRA format.

    See also :ref:`\configuration_files_replacement_policy-label`.

.. _install_examples-label:

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 installed it

    will automatically try to downgrade or upgrade to the specific version.

``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//packages/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 functions, etc.).

``dnf install --advisory=FEDORA-2018-b7b99fe852 \*``

    Install all packages that belong to the "FEDORA-2018-b7b99fe852" advisory.

.. _list_command-label:

------------

List Command

------------