From Fedora Project Wiki

(add check subcommand)
 
(18 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
{{autolang|base=yes}}
 
{{autolang|base=yes}}
  
DNF is a software package manager that installs, updates, and removes [[package]]s on [[RPM]]-based Linux distributions. It automatically computes dependencies and figures out what things should occur to install packages. DNF makes it easier to maintain groups of machines without having to manually update each one using [[rpm]].  
+
'''DNF''' is a software package manager that installs, updates, and removes [[package]]s on [[RPM]]-based Linux distributions. It automatically computes dependencies and determines the actions required to install packages. DNF also makes it easier to maintain groups of machines, eliminating the need to manually update each one using [[rpm]]. Introduced in Fedora 18, it has been the default package manager since Fedora 22.
  
DNF is the next upcoming major version of [[Yum]]. It roughly maintains <abbr Title="Command-Line Interface">CLI</abbr> compatibility with [[Yum]] and defines strict <abbr Title="Application Program Interface">API</abbr> for extensions and plugins. Plugins can modify or extend features of DNF or provide additional <abbr Title="Command-Line Interface">CLI</abbr> commands on top of those mentioned below. If you know the name of such a command (including commands mentioned bellow), 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-command(repoquery) for a repoquery command (the same applies to specifying dependencies of packages that require a particular command).
+
DNF or Dandified yum is the next generation version of [[yum]]. It roughly maintains <abbr Title="Command-Line Interface">CLI</abbr> compatibility with [[yum]] and defines a strict <abbr Title="Application Programming Interface">API</abbr> for extensions and plugins. Plugins can modify or extend features of DNF or provide additional <abbr Title="Command-Line Interface">CLI</abbr> commands on top of those mentioned below. If you know the name of such a command (including commands mentioned bellow), 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-command(repoquery) for a repoquery command (the same applies to specifying dependencies of packages that require a particular command).
  
 
{{Infobox package
 
{{Infobox package
Line 10: Line 10:
 
| package_added = Fedora 18, and later versions
 
| package_added = Fedora 18, and later versions
  
| website =http://dnf.baseurl.org/
+
| website = https://github.com/rpm-software-management/dnf
 
}}
 
}}
 +
== Features ==
 +
 +
* Support for multiple repositories
 +
* Simple configuration
 +
* Dependency calculation based on  modern depsolving technology
 +
* Faster and less memory-intensive operation
 +
* RPM-consistent behavior
 +
* Package group support, including multiple-repository groups
 +
* Simple interface
 +
* Documented, solid Python API
 +
* DNF runs in both Python 2 and Python 3
 +
* C bindings for lower level libraries:
 +
** hawkey for package querying and depsolving. PackageKit is already making use of hawkey
 +
** librepo for repo operations. PackageKit is already making use of librepo
 +
** libcomps for comps operations
 +
 
== Available commands ==
 
== Available commands ==
  
 
<abbr Title="dnf [options] autoremove&#13;&#13;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.">autoremove</abbr>
 
<abbr Title="dnf [options] autoremove&#13;&#13;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.">autoremove</abbr>
 +
 +
<abbr Title="dnf [options] check [--duplicates] [--obsoleted] [--provides]&#13;&#13;Checks the local packagedb and produces information on any problems it finds. You can pass the check command the options “--dependencies”, “--duplicates”, “--obsoleted” or “--provides”, to limit the checking that is performed (the default is “all” which does all).">check</abbr>
  
 
<abbr Title="dnf [options] check-update [&lt;package-specs&gt;...]&#13;&#13;Non-interactively checks if updates of the specified packages are available. If no &lt;package-specs&gt; are 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.&#13;&#13;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 must also ensure the satisfiability of all dependencies and other restrictions.">check-update</abbr>
 
<abbr Title="dnf [options] check-update [&lt;package-specs&gt;...]&#13;&#13;Non-interactively checks if updates of the specified packages are available. If no &lt;package-specs&gt; are 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.&#13;&#13;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 must also ensure the satisfiability of all dependencies and other restrictions.">check-update</abbr>
Line 32: Line 50:
 
<abbr Title="dnf [options] info [&lt;package-spec&gt;...]&#13;&#13;Is used to list description and summary information about available packages.&#13;&#13;This command by default does not force a sync of expired metadata.">info</abbr>
 
<abbr Title="dnf [options] info [&lt;package-spec&gt;...]&#13;&#13;Is used to list description and summary information about available packages.&#13;&#13;This command by default does not force a sync of expired metadata.">info</abbr>
  
<abbr Title="dnf [options] install &lt;spec&gt;...&#13;&#13;    Make sure that the given packages and their dependencies can be installed on the system. Each &lt;spec&gt; can be either a &lt;package-spec&gt;, which specifies a package directly, or a path to the local rpm package, or an URL to a remote rpm package, or a @&lt;group-spec&gt;, which specifies an (environment) group which contains it. If a given package cannot be (and is not already) installed, the exit code will be non-zero.&#13;&#13;Please make sure that you understand which package will be selected in case of multiple matches.">install</abbr>
+
<abbr Title="dnf [options] install &lt;spec&gt;...&#13;&#13;    Dnf makes sure that the given packages and their dependencies are installed on the system. Each &lt;spec&gt; can be either a &lt;package-spec&gt;, which specifies a package directly, or a path to the local rpm package, or an URL to a remote rpm package, or a @&lt;group-spec&gt;, which specifies an (environment) group which contains it. If a given package cannot be (and is not already) installed, the exit code will be non-zero.&#13;&#13;Please make sure that you understand which package will be selected in case of multiple matches.">install</abbr>
  
 
<abbr Title="Dumps 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 installed but it is present in a repository that DNF knows about. The list command can also limit the displayed packages according to other criteria, e.g. to only those that update an installed package.&#13;&#13;All the forms take a [&lt;package-specs&gt;...] parameter to further limit the result to only those packages matching it.&#13;&#13;dnf [options] list [all] [&lt;package-name-specs&gt;...]&#13;    Lists all packages known to us, present in the RPMDB, in a repo or in both.&#13;&#13;dnf [options] list installed [&lt;package-name-specs&gt;...]&#13;    Lists installed packages.&#13;&#13;dnf [options] list available [&lt;package-name-specs&gt;...]&#13;    Lists available packages.&#13;&#13;dnf [options] list extras [&lt;package-name-specs&gt;...]&#13;    Lists extras, that is packages installed on the system that are not available in any known repository.&#13;&#13;dnf [options] list obsoletes [&lt;package-name-specs&gt;...]&#13;    List the packages installed on the system that are obsoleted by packages in any known repository.&#13;&#13;dnf [options] list recent [&lt;package-name-specs&gt;...]&#13;    List packages recently added into the repositories.&#13;&#13;dnf [options] list upgrades [&lt;package-name-specs&gt;...]&#13;    List upgrades available for the installed packages.&#13;&#13;dnf [options] list autoremove&#13;    List packages which will be removed by dnf autoremove command.&#13;&#13;This command by default does not force a sync of expired metadata.">list</abbr>
 
<abbr Title="Dumps 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 installed but it is present in a repository that DNF knows about. The list command can also limit the displayed packages according to other criteria, e.g. to only those that update an installed package.&#13;&#13;All the forms take a [&lt;package-specs&gt;...] parameter to further limit the result to only those packages matching it.&#13;&#13;dnf [options] list [all] [&lt;package-name-specs&gt;...]&#13;    Lists all packages known to us, present in the RPMDB, in a repo or in both.&#13;&#13;dnf [options] list installed [&lt;package-name-specs&gt;...]&#13;    Lists installed packages.&#13;&#13;dnf [options] list available [&lt;package-name-specs&gt;...]&#13;    Lists available packages.&#13;&#13;dnf [options] list extras [&lt;package-name-specs&gt;...]&#13;    Lists extras, that is packages installed on the system that are not available in any known repository.&#13;&#13;dnf [options] list obsoletes [&lt;package-name-specs&gt;...]&#13;    List the packages installed on the system that are obsoleted by packages in any known repository.&#13;&#13;dnf [options] list recent [&lt;package-name-specs&gt;...]&#13;    List packages recently added into the repositories.&#13;&#13;dnf [options] list upgrades [&lt;package-name-specs&gt;...]&#13;    List upgrades available for the installed packages.&#13;&#13;dnf [options] list autoremove&#13;    List packages which will be removed by dnf autoremove command.&#13;&#13;This command by default does not force a sync of expired metadata.">list</abbr>
Line 44: Line 62:
 
<abbr Title="dnf [options] reinstall &lt;package-specs&gt;...&#13;    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).">reinstall</abbr>
 
<abbr Title="dnf [options] reinstall &lt;package-specs&gt;...&#13;    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).">reinstall</abbr>
  
    remove
+
<abbr Title="dnf [options] remove &lt;package-specs&gt;...&#13;    Removes the specified packages from the system along with any packages depending on the packages being removed. Each &lt;spec&gt; can be either a &lt;package-spec&gt;, which specifies a package directly, or a @&lt;group-spec&gt;, which specifies an (environment) group which contains it. If clean_requirements_on_remove is enabled (the default) also removes any dependencies that are no longer needed.">remove</abbr>
    repolist
+
 
    repository-packages
+
<abbr Title="dnf [options] repolist [enabled|disabled|all]&#13;    Depending on the exact command, lists enabled, disabled or all known repositories. Lists all enabled repositories by default. Provides more detailed information when -v option is used.&#13;&#13;This command by default does not force a sync of expired metadata.">repolist</abbr>
    search
+
 
    updateinfo
+
<abbr Title="The repository-packages command allows the user to run commands on top of all packages in the repository named &lt;repoid&gt;. However, any dependency resolution takes into account packages from all enabled repositories. Specifications &lt;package-name-spec&gt; and &lt;package-spec&gt; further limit the candidates to only those packages matching at least one of them.&#13;&#13;info subcommand lists description and summary information about packages depending on the packages’ relation to the repository. list subcommand just dumps lists of that packages.&#13;&#13; See detailed description in Command Reference (see bellow)">repository-packages</abbr>
    upgrade
+
 
    upgrade-to
+
<abbr Title="dnf [options] search [all] &lt;keywords&gt;...&#13;    Search package metadata for the keywords. Keywords are matched as case-insensitive substrings, globbing is supported. By default the command will only look at package names and summaries, failing that (or whenever all was given as an argument) it will match against package descriptions and URLs. The result is sorted from the most relevant results to the least.&#13;&#13;This command by default does not force a sync of expired metadata.">search</abbr>
 +
 
 +
<abbr Title="dnf [options] updateinfo [&lt;output&gt;] [&lt;availability&gt;] [&lt;spec&gt;...]&#13;&#13;Display information about update advisories.&#13;&#13;Depending on &lt;output&gt;, DNF displays just counts of advisory types (omitted or summary), list of advisories (list) or detailed information (info). When info with -v option is used, the information is even more detailed.&#13;&#13;&lt;availability&gt; 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 advisories about any versions of installed packages (all) are taken into account. 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 version but there is no enabled repository which contains any newer version.&#13;&#13;If given and if neither ID, type (bugfix, enhancement, security/sec) nor a package name of an advisory does match &lt;spec&gt;, the advisory is not taken into account. The matching is case-sensitive and in the case of advisory IDs and package names, globbing is supported.">updateinfo</abbr>
 +
 
 +
<abbr Title="dnf [options] upgrade&#13;    Updates each package to a highest version that is both available and resolvable.&#13;&#13;dnf [options] upgrade &lt;package-installed-specs&gt;...&#13;    Updates each specified package to the latest available version. Updates dependencies as necessary.">upgrade</abbr>
 +
 
 +
<abbr Title="dnf [options] upgrade-to &lt;package-nevr-specs&gt;...&#13;    Upgrades packages to the specified versions.">upgrade-to</abbr>
  
 
== Installation ==
 
== Installation ==
DNF comes with Fedora since version 18, but DNF can installed by using the Yum Command:
+
DNF comes with Fedora since version 18, but DNF can installed by using the yum Command:
 
<pre># yum install dnf</pre>
 
<pre># yum install dnf</pre>
As of Fedora 22, [[Yum]] has been replaced with DNF and doesn't need to be install.
+
As of Fedora 22, [[yum]] has been replaced with DNF and doesn't need to be installed.
  
 
== Usage ==
 
== Usage ==
In the basic methods, dnf can be used almost exactly as YUM:  
+
In the basic methods, DNF can be used almost exactly as yum to search, install or remove packages:  
  
<pre># sudo dnf search audacity </pre>
+
<pre># dnf search audacity </pre>
<pre># sudo dnf install audacity.x86_64 </pre>
+
<pre># dnf install audacity </pre>
<pre># sudo dnf remove audacity </pre>
+
<pre># dnf remove audacity </pre>
 +
 
 +
=== Automatic Updates ===
 +
The DNF-Automatic RPM package as a DNF component provides a service for automatic download and installation of updates. It can automatically monitor and report via email availability of updates, or send a log about downloaded packages and installed updates. See [[AutoUpdates]] section or [http://dnf.readthedocs.org/en/latest/automatic.html DNF-Automatic] page.
 +
 
 +
=== System Upgrades ===
 +
Fedora Products can be upgraded with DNF system upgrade plugin or directly with DNF. See [[Upgrade]] section.
 +
 
 +
=== Language Support Using DNF ===
 +
DNF can be used to install or remove Language Support. A detailed description with a list of available languages can be found on [https://fedoraproject.org/wiki/I18N/Language_Support_Using_Dnf Language Support Using Dnf] page.
 +
 
 +
=== DNF conpared with Apt ===
 +
Users coming from Debian or Ubuntu may find this table on [https://fedoraproject.org/wiki/Differences_to_Ubuntu#Package_Management package management comparison] useful.
  
 
== Documentation ==
 
== Documentation ==
https://github.com/rpm-software-management/dnf/wiki lists two documentation links
 
  
 
1. [http://dnf.readthedocs.org/ Documentation Index]
 
1. [http://dnf.readthedocs.org/ Documentation Index]
  
 
2. [http://dnf.readthedocs.org/en/latest/command_ref.html Command Reference]
 
2. [http://dnf.readthedocs.org/en/latest/command_ref.html Command Reference]
 +
 +
3. [http://dnf.baseurl.org/ DNF blog]
 +
 +
4. [https://github.com/rpm-software-management/dnf/wiki DNF wiki]
 +
 +
5. [[Changes/DNF-2.0]]
 +
 +
[[Category:Documentation]]
 +
[[Category:Software Management]]

Latest revision as of 06:02, 18 November 2018

DNF is a software package manager that installs, updates, and removes packages on RPM-based Linux distributions. It automatically computes dependencies and determines the actions required to install packages. DNF also makes it easier to maintain groups of machines, eliminating the need to manually update each one using rpm. Introduced in Fedora 18, it has been the default package manager since Fedora 22.

DNF or Dandified yum is the next generation version of yum. 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 bellow), 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-command(repoquery) for a repoquery command (the same applies to specifying dependencies of packages that require a particular command).

DNF
Echo-package-48px.png

RPM package dnf
Added in Fedora 18, and later versions
Website https://github.com/rpm-software-management/dnf

BugsBodhiKoji

Features

  • Support for multiple repositories
  • Simple configuration
  • Dependency calculation based on modern depsolving technology
  • Faster and less memory-intensive operation
  • RPM-consistent behavior
  • Package group support, including multiple-repository groups
  • Simple interface
  • Documented, solid Python API
  • DNF runs in both Python 2 and Python 3
  • C bindings for lower level libraries:
    • hawkey for package querying and depsolving. PackageKit is already making use of hawkey
    • librepo for repo operations. PackageKit is already making use of librepo
    • libcomps for comps operations

Available commands

autoremove

check

check-update

clean

distro-sync

downgrade

group

help

history

info

install

list

makecache

mark

provides

reinstall

remove

repolist

repository-packages

search

updateinfo

upgrade

upgrade-to

Installation

DNF comes with Fedora since version 18, but DNF can installed by using the yum Command:

# yum install dnf

As of Fedora 22, yum has been replaced with DNF and doesn't need to be installed.

Usage

In the basic methods, DNF can be used almost exactly as yum to search, install or remove packages:

# dnf search audacity 
# dnf install audacity 
# dnf remove audacity 

Automatic Updates

The DNF-Automatic RPM package as a DNF component provides a service for automatic download and installation of updates. It can automatically monitor and report via email availability of updates, or send a log about downloaded packages and installed updates. See AutoUpdates section or DNF-Automatic page.

System Upgrades

Fedora Products can be upgraded with DNF system upgrade plugin or directly with DNF. See Upgrade section.

Language Support Using DNF

DNF can be used to install or remove Language Support. A detailed description with a list of available languages can be found on Language Support Using Dnf page.

DNF conpared with Apt

Users coming from Debian or Ubuntu may find this table on package management comparison useful.

Documentation

1. Documentation Index

2. Command Reference

3. DNF blog

4. DNF wiki

5. Changes/DNF-2.0