1DNF(8) DNF DNF(8)
2
6 dnf - DNF Command Reference
7
9 dnf [options] <command> [<args>...]
10
12 DNF is the next upcoming major version of YUM, a package manager for
13 RPM-based Linux distributions. It roughly maintains CLI compatibility
14 with YUM and defines a strict API for extensions and plugins.
15 Plugins can modify or extend features of DNF or provide additional CLI
17 commands on top of those mentioned below. If you know the name of such
18 a command (including commands mentioned below), you may find/install
19 the package which provides it using the appropriate virtual provide in
20 the form of dnf-command(<alias>), where <alias> is the name of the com‐
21 mand; e.g.``dnf install 'dnf-command(versionlock)'`` installs a ver‐
22 sionlock plugin. This approach also applies to specifying dependencies
23 of packages that require a particular DNF command.
24 Return values:
26 · 0 : Operation was successful.
28 · 1 : An error occurred, which was handled by dnf.
30 · 3 : An unknown unhandled error occurred during operation.
32 · 100: See check-update
34 · 200: There was a problem with acquiring or releasing of locks.
36 Available commands:
38 · alias
40 · autoremove
42 · check
44 · check-update
46 · clean
48 · deplist
50 · distro-sync
52 · downgrade
54 · group
56 · help
58 · history
60 · info
62 · install
64 · list
66 · makecache
68 · mark
70 · module
72 · provides
74 · reinstall
76 · remove
78 · repoinfo
80 · repolist
82 · repoquery
84 · repository-packages
86 · search
88 · shell
90 · swap
92 · updateinfo
94 · upgrade
96 · upgrade-minimal
98 · upgrade-to
100 Additional information:
102 · Options
104 · Specifying Packages
106 · Specifying Exact Versions of Packages
108 · Specifying Provides
110 · Specifying Groups
112 · Specifying Transactions
114 · Metadata Synchronization
116 · Configuration Files Replacement Policy
118 · Files
120 · See Also
122
124 -4 Resolve to IPv4 addresses only.
125 -6 Resolve to IPv6 addresses only.
127 --advisory=<advisory>, --advisories=<advisory>
129 Include packages corresponding to the advisory ID, Eg.
130 FEDORA-2201-123. Applicable for the install, repoquery, update‐
131 info and upgrade commands.
132 --allowerasing
134 Allow erasing of installed packages to resolve dependencies.
135 This option could be used as an alternative to the yum swap com‐
136 mand where packages to remove are not explicitly defined.
137 --assumeno
139 Automatically answer no for all questions.
140 -b, --best
142 Try the best available package versions in transactions. Specif‐
143 ically during dnf upgrade, which by default skips over updates
144 that can not be installed for dependency reasons, the switch
145 forces DNF to only consider the latest packages. When running
146 into packages with broken dependencies, DNF will fail giving a
147 reason why the latest version can not be installed.
148 --bugfix
150 Include packages that fix a bugfix issue. Applicable for the
151 install, repoquery, updateinfo and upgrade commands.
152 --bz=<bugzilla>, --bzs=<bugzilla>
154 Include packages that fix a Bugzilla ID, Eg. 123123. Applicable
155 for the install, repoquery, updateinfo and upgrade commands.
156 -C, --cacheonly
158 Run entirely from system cache, don't update the cache and use
159 it even in case it is expired.
160 DNF uses a separate cache for each user under which it executes.
162 The cache for the root user is called the system cache. This
163 switch allows a regular user read-only access to the system
164 cache, which usually is more fresh than the user's and thus he
165 does not have to wait for metadata sync.
166 --color=<color>
168 Control whether color is used in terminal output. Valid values
169 are always, never and auto (default).
170 --comment=<comment>
172 Add a comment to the transaction history.
173 -c <config file>, --config=<config file>
175 Configuration file location.
176 --cve=<cves>, --cves=<cves>
178 Include packages that fix a CVE (Common Vulnerabilities and
179 Exposures) ID (http://cve.mitre.org/about/), Eg. CVE-2201-0123.
180 Applicable for the install, repoquery, updateinfo, and upgrade
181 commands.
182 -d <debug level>, --debuglevel=<debug level>
184 Debugging output level. This is an integer value between 0 (no
185 additional information strings) and 10 (shows all debugging
186 information, even that not understandable to the user), default
187 is 2. Deprecated, use -v instead.
188 --debugsolver
190 Dump data aiding in dependency solver debugging into ./debug‐
191 data.
192 --disableexcludes=[all|main|<repoid>], --disableexcludep‐
194 kgs=[all|main|<repoid>]
195 Disable the configuration file excludes. Takes one of the following
196 three options:
197 · all, disables all configuration file excludes
199 · main, disables excludes defined in the [main] section
201 · repoid, disables excludes defined for the given repository
203 --disable, --set-disabled
205 Disable specified repositories (automatically saves). The option
206 has to be used together with the config-manager command
207 (dnf-plugins-core).
208 --disableplugin=<plugin names>
210 Disable the listed plugins specified by names or globs.
211 --disablerepo=<repoid>
213 Disable specific repositories by an id or a glob. This option is
214 mutually exclusive with --repo.
215 --downloaddir=<path>, --destdir=<path>
217 Redirect downloaded packages to provided directory. The option
218 has to be used together with the --downloadonly command line
219 option, with the download command (dnf-plugins-core) or with the
220 system-upgrade command (dnf-plugins-extras).
221 --downloadonly
223 Download the resolved package set without performing any rpm
224 transaction (install/upgrade/erase).
225 -e <error level>, --errorlevel=<error level>
227 Error output level. This is an integer value between 0 (no error
228 output) and 10 (shows all error messages), default is 3. Depre‐
229 cated, use -v instead.
230 --enable, --set-enabled
232 Enable specified repositories (automatically saves). The option
233 has to be used together with the config-manager command
234 (dnf-plugins-core).
235 --enableplugin=<plugin names>
237 Enable the listed plugins specified by names or globs.
238 --enablerepo=<repoid>
240 Enable additional repositories by an id or a glob.
241 --enhancement
243 Include enhancement relevant packages. Applicable for the
244 install, repoquery, updateinfo and upgrade commands.
245 -x <package-file-spec>, --exclude=<package-file-spec>
247 Exclude packages specified by <package-file-spec> from the oper‐
248 ation.
249 --excludepkgs=<package-file-spec>
251 Deprecated option. It was replaced by the --exclude option.
252 --forcearch=<arch>
254 Force the use of an architecture. Any architecture can be speci‐
255 fied. However, use of an architecture not supported natively by
256 your CPU will require emulation of some kind. This is usually
257 through QEMU. The behavior of --forcearch can be configured by
258 using the arch and ignorearch configuration options with values
259 <arch> and True respectively.
260 -h, --help, --help-cmd
262 Show the help.
263 --installroot=<path>
265 Specifies an alternative installroot, relative to where all
266 packages will be installed. Think of this like doing chroot
267 <root> dnf, except using --installroot allows dnf to work before
268 the chroot is created. It requires absolute path.
269 · cachedir, log files, releasever, and gpgkey are taken from or stored
271 in the installroot. Gpgkeys are imported into the installroot from a
272 path relative to the host which can be specified in the repository
273 section of configuration files.
274 · configuration file and reposdir are searched inside the installroot
276 first. If they are not present, they are taken from the host system.
277 Note: When a path is specified within a command line argument
278 (--config=<config file> in case of configuration file and
279 --setopt=reposdir=<reposdir> for reposdir) then this path is always
280 relative to the host with no exceptions.
281 · vars are taken from the host system or installroot according to
283 reposdir installroot. When varsdir paths are specified within a com‐
284 mand line argument (--setopt=varsdir=<reposdir>) then those path are
285 always relative to the host with no exceptions.
286 · The pluginpath and pluginconfpath are relative to the host.
288 Note: You may also want to use the command-line option --relea‐
289 sever=<release> when creating the installroot, otherwise the $relea‐
290 sever value is taken from the rpmdb within the installroot (and thus
291 it is empty at the time of creation and the transaction will fail).
292 If --releasever=/ is used, the releasever will be detected from the
293 host (/) system. The new installroot path at the time of creation
294 does not contain the repository, releasever and dnf.conf files.
295 On a modular system you may also want to use the --setopt=mod‐
297 ule_platform_id=<module_platform_name:stream> command-line option
298 when creating the installroot, otherwise the module_platform_id
299 value will be taken from the /etc/os-release file within the
300 installroot (and thus it will be empty at the time of creation, the
301 modular dependency could be unsatisfied and modules content could be
302 excluded).
303 Installroot examples:
305 dnf --installroot=<installroot> --releasever=<release> install sys‐
307 tem-release
308 Permanently sets the releasever of the system in the
309 <installroot> directory to <release>.
310 dnf --installroot=<installroot> --setopt=reposdir=<path> --config
312 /path/dnf.conf upgrade
313 Upgrades packages inside the installroot from a repository
314 described by --setopt using configuration from
315 /path/dnf.conf.
316 --newpackage
318 Include newpackage relevant packages. Applicable for the
319 install, repoquery, updateinfo and upgrade commands.
320 --noautoremove
322 Disable removal of dependencies that are no longer used. It sets
323 clean_requirements_on_remove configuration option to False.
324 --nobest
326 Set best option to False, so that transactions are not limited
327 to best candidates only.
328 --nodocs
330 Do not install documentation. Sets the rpm flag 'RPM‐
331 TRANS_FLAG_NODOCS'.
332 --nogpgcheck
334 Skip checking GPG signatures on packages (if RPM policy allows).
335 --noplugins
337 Disable all plugins.
338 --obsoletes
340 This option has an effect on an install/update, it enables dnf's
341 obsoletes processing logic. For more information see the obso‐
342 letes option.
343 This option also displays capabilities that the package obso‐
345 letes when used together with the repoquery command.
346 Configuration Option: obsoletes
348 -q, --quiet
350 In combination with a non-interactive command, shows just the
351 relevant content. Suppresses messages notifying about the cur‐
352 rent state or actions of DNF.
353 -R <minutes>, --randomwait=<minutes>
355 Maximum command wait time.
356 --refresh
358 Set metadata as expired before running the command.
359 --releasever=<release>
361 Configure DNF as if the distribution release was <release>. This
362 can affect cache paths, values in configuration files and mir‐
363 rorlist URLs.
364 --repofrompath <repo>,<path/url>
366 Specify a repository to add to the repositories for this query.
367 This option can be used multiple times.
368 · The repository label is specified by <repo>.
370 · The path or url to the repository is specified by <path/url>. It is
372 the same path as a baseurl and can be also enriched by the repo vari‐
373 ables.
374 · The configuration for the repository can be adjusted using -‐
376 -setopt=<repo>.<option>=<value>.
377 · If you want to view only packages from this repository, combine this
379 with the --repo=<repo> or --disablerepo="*" switches.
380 --repo=<repoid>, --repoid=<repoid>
382 Enable just specific repositories by an id or a glob. Can be
383 used multiple times with accumulative effect. It is basically a
384 shortcut for --disablerepo="*" --enablerepo=<repoid> and is
385 mutually exclusive with the --disablerepo option.
386 --rpmverbosity=<name>
388 RPM debug scriptlet output level. Sets the debug level to <name>
389 for RPM scriptlets. For available levels, see the rpmverbosity
390 configuration option.
391 --sec-severity=<severity>, --secseverity=<severity>
393 Includes packages that provide a fix for an issue of the speci‐
394 fied severity. Applicable for the install, repoquery, update‐
395 info and upgrade commands.
396 --security
398 Includes packages that provide a fix for a security issue.
399 Applicable for the upgrade command.
400 --setopt=<option>=<value>
402 Override a configuration option from the configuration file. To
403 override configuration options for repositories, use
404 repoid.option for the <option>. Values for configuration options
405 like excludepkgs, includepkgs, installonlypkgs and tsflags are
406 appended to the original value, they do not override it. How‐
407 ever, specifying an empty value (e.g. --setopt=tsflags=) will
408 clear the option.
409 --skip-broken
411 Resolve depsolve problems by removing packages that are causing
412 problems from the transaction. It is an alias for the strict
413 configuration option with value False. Additionally, with the
414 enable and disable module subcommands it allows one to perform
415 an action even in case of broken modular dependencies.
416 --showduplicates
418 Show duplicate packages in repositories. Applicable for the list
419 and search commands.
420 -v, --verbose
422 Verbose operation, show debug messages.
423 --version
425 Show DNF version and exit.
426 -y, --assumeyes
428 Automatically answer yes for all questions.
429 List options are comma-separated. Command-line options override respec‐
431 tive settings from configuration files.
432
434 For an explanation of <package-spec> and <package-file-spec> see
435 Specifying Packages.
436 For an explanation of <package-nevr-spec> see Specifying Exact Versions
438 of Packages.
439 For an explanation of <provide-spec> see Specifying Provides.
441 For an explanation of <group-spec> see Specifying Groups.
443 For an explanation of <module-spec> see Specifying Modules.
445 For an explanation of <transaction-spec> see Specifying Transactions.
447 Alias Command
449 Allows the user to define and manage a list of aliases (in the form
450 <name=value>), which can be then used as dnf commands to abbreviate
451 longer command sequences. For examples on using the alias command, see
452 Alias Examples. For examples on the alias processing, see Alias Pro‐
453 cessing Examples.
454 To use an alias (name=value), the name must be placed as the first
456 "command" (e.g. the first argument that is not an option). It is then
457 replaced by its value and the resulting sequence is again searched for
458 aliases. The alias processing stops when the first found command is not
459 a name of any alias.
460 In case the processing would result in an infinite recursion, the orig‐
462 inal arguments are used instead.
463 Also, like in shell aliases, if the result starts with a \, the alias
465 processing will stop.
466 All aliases are defined in configuration files in the
468 /etc/dnf/aliases.d/ directory in the [aliases] section, and aliases
469 created by the alias command are written to the USER.conf file. In case
470 of conflicts, the USER.conf has the highest priority, and alphabetical
471 ordering is used for the rest of the configuration files.
472 Optionally, there is the enabled option in the [main] section default‐
474 ing to True. This can be set for each file separately in the respective
475 file, or globally for all aliases in the ALIASES.conf file.
476 dnf alias [options] [list] [<name>...]
478 List aliases with their final result. The [<alias>...] parameter
479 further limits the result to only those aliases matching it.
480 dnf alias [options] add <name=value>...
482 Create new aliases.
483 dnf alias [options] delete <name>...
485 Delete aliases.
486 Alias Examples
488 dnf alias list
489 Lists all defined aliases.
490 dnf alias add rm=remove
492 Adds a new command alias called rm which works the same as the
493 remove command.
494 dnf alias add upgrade="\upgrade --skip-broken --disableexcludes=all
496 --obsoletes"
497 Adds a new command alias called upgrade which works the same as
498 the upgrade command, with additional options. Note that the
499 original upgrade command is prefixed with a \ to prevent an
500 infinite loop in alias processing.
501 Alias Processing Examples
503 If there are defined aliases in=install and FORCE="--skip-broken --dis‐
504 ableexcludes=all":
505 · dnf FORCE in will be replaced with dnf --skip-broken --disableex‐
507 cludes=all install
508 · dnf in FORCE will be replaced with dnf install FORCE (which will
510 fail)
511 If there is defined alias in=install:
513 · dnf in will be replaced with dnf install
515 · dnf --repo updates in will be replaced with dnf --repo updates in
517 (which will fail)
518 Auto Remove Command
520 dnf [options] autoremove
521 Removes all "leaf" packages from the system that were originally
522 installed as dependencies of user-installed packages, but which are
523 no longer required by any such package.
524 Packages listed in installonlypkgs are never automatically removed by
526 this command.
527 dnf [options] autoremove <spec>...
529 This is an alias for the Remove Command command with clean_require‐
530 ments_on_remove set to True. It removes the specified packages from
531 the system along with any packages depending on the packages being
532 removed. Each <spec> can be either a <package-spec>, which specifies
533 a package directly, or a @<group-spec>, which specifies an (environ‐
534 ment) group which contains it. It also removes any dependencies that
535 are no longer needed.
536 There are also a few specific autoremove commands autoremove-n,
538 autoremove-na and autoremove-nevra that allow the specification of
539 an exact argument in the NEVRA (name-epoch:version-release.architec‐
540 ture) format.
541 This command by default does not force a sync of expired metadata. See
543 also Metadata Synchronization.
544 Check Command
546 dnf [options] check [--dependencies] [--duplicates] [--obsoleted]
547 [--provides]
548 Checks the local packagedb and produces information on any problems
549 it finds. You can limit the checks to be performed by using the
550 --dependencies, --duplicates, --obsoleted and --provides options
551 (the default is to check everything).
552 Check-Update Command
554 dnf [options] check-update [--changelogs] [<package-file-spec>...]
555 Non-interactively checks if updates of the specified packages are
556 available. If no <package-file-spec> is given, checks whether any
557 updates at all are available for your system. DNF exit code will be
558 100 when there are updates available and a list of the updates will
559 be printed, 0 if not and 1 if an error occurs. If --changelogs
560 option is specified, also changelog delta of packages about to be
561 updated is printed.
562 Please note that having a specific newer version available for an
564 installed package (and reported by check-update) does not imply that
565 subsequent dnf upgrade will install it. The difference is that dnf
566 upgrade has restrictions (like package dependencies being satisfied)
567 to take into account.
568 The output is affected by the autocheck_running_kernel configuration
570 option.
571 Clean Command
573 Performs cleanup of temporary files kept for repositories. This
574 includes any such data left behind from disabled or removed reposito‐
575 ries as well as for different distribution release versions.
576 dnf clean dbcache
578 Removes cache files generated from the repository metadata. This
579 forces DNF to regenerate the cache files the next time it is
580 run.
581 dnf clean expire-cache
583 Marks the repository metadata expired. DNF will re-validate the
584 cache for each repository the next time it is used.
585 dnf clean metadata
587 Removes repository metadata. Those are the files which DNF uses
588 to determine the remote availability of packages. Using this
589 option will make DNF download all the metadata the next time it
590 is run.
591 dnf clean packages
593 Removes any cached packages from the system.
594 dnf clean all
596 Does all of the above.
597 Deplist command
599 dnf [options] deplist [<select-options>] [<query-options>] [<pack‐
600 age-spec>]
601 Alias for dnf repoquery --deplist.
602 Distro-Sync command
604 dnf distro-sync [<package-spec>...]
605 As necessary upgrades, downgrades or keeps selected installed
606 packages to match the latest version available from any enabled
607 repository. If no package is given, all installed packages are
608 considered.
609 See also Configuration Files Replacement Policy.
611 Distribution-Synchronization command
613 dnf distribution-synchronization
614 Deprecated alias for the Distro-Sync command.
615 Downgrade Command
617 dnf [options] downgrade <package-spec>...
618 Downgrades the specified packages to the highest installable
619 package of all known lower versions if possible. When version is
620 given and is lower than version of installed package then it
621 downgrades to target version.
622 Erase Command
624 dnf [options] erase <spec>...
625 Deprecated alias for the Remove Command.
626 Group Command
628 Groups are virtual collections of packages. DNF keeps track of groups
629 that the user selected ("marked") installed and can manipulate the com‐
630 prising packages with simple commands.
631 dnf [options] group [summary] <group-spec>
633 Display overview of how many groups are installed and available.
634 With a spec, limit the output to the matching groups. summary is
635 the default groups subcommand.
636 dnf [options] group info <group-spec>
638 Display package lists of a group. Shows which packages are
639 installed or available from a repository when -v is used.
640 dnf [options] group install [--with-optional] <group-spec>...
642 Mark the specified group installed and install packages it con‐
643 tains. Also include optional packages of the group if
644 --with-optional is specified. All mandatory and Default packages
645 will be installed whenever possible. Conditional packages are
646 installed if they meet their requirement. If the group is
647 already (partially) installed, the command installs the missing
648 packages from the group. Depending on the value of obsoletes
649 configuration option group installation takes obsoletes into
650 account.
651 dnf [options] group list <group-spec>...
653 List all matching groups, either among installed or available
654 groups. If nothing is specified, list all known groups.
655 --installed and --available options narrow down the requested
656 list. Records are ordered by the display_order tag defined in
657 comps.xml file. Provides a list of all hidden groups by using
658 option --hidden. Provides group IDs when the -v or --ids
659 options are used.
660 dnf [options] group remove <group-spec>...
662 Mark the group removed and remove those packages in the group
663 from the system which do not belong to another installed group
664 and were not installed explicitly by the user.
665 dnf [options] group upgrade <group-spec>...
667 Upgrades the packages from the group and upgrades the group
668 itself. The latter comprises of installing packages that were
669 added to the group by the distribution and removing packages
670 that got removed from the group as far as they were not
671 installed explicitly by the user.
672 Groups can also be marked installed or removed without physically
674 manipulating any packages:
675 dnf [options] group mark install <group-spec>...
677 Mark the specified group installed. No packages will be
678 installed by this command, but the group is then considered
679 installed.
680 dnf [options] group mark remove <group-spec>...
682 Mark the specified group removed. No packages will be removed by
683 this command.
684 See also Configuration Files Replacement Policy.
686 Groups Command
688 dnf [options] groups
689 Deprecated alias for the Group Command.
690 Help Command
692 dnf help [<command>]
693 Displays the help text for all commands. If given a command name
694 then only displays help for that particular command.
695 History Command
697 The history command allows the user to view what has happened in past
698 transactions and act according to this information (assuming the his‐
699 tory_record configuration option is set).
700 dnf history [list] [<spec>...]
702 The default history action is listing information about given
703 transactions in a table. Each <spec> can be either a <transac‐
704 tion-spec>, which specifies a transaction directly, or a <trans‐
705 action-spec>..<transaction-spec>, which specifies a range of
706 transactions, or a <package-name-spec>, which specifies a trans‐
707 action by a package which it manipulated. When no transaction is
708 specified, list all known transactions.
709 dnf history info [<spec>...]
711 Describe the given transactions. The meaning of <spec> is the
712 same as in the History List Command. When no transaction is
713 specified, describe what happened during the latest transaction.
714 dnf history redo <transaction-spec>|<package-file-spec>
716 Repeat the specified transaction. Uses the last transaction
717 (with the highest ID) if more than one transaction for given
718 <package-file-spec> is found. If it is not possible to redo some
719 operations due to the current state of RPMDB, it will not redo
720 the transaction.
721 dnf history rollback <transaction-spec>|<package-file-spec>
723 Undo all transactions performed after the specified transaction.
724 Uses the last transaction (with the highest ID) if more than one
725 transaction for given <package-file-spec> is found. If it is
726 not possible to undo some transactions due to the current state
727 of RPMDB, it will not undo any transaction.
728 dnf history undo <transaction-spec>|<package-file-spec>
730 Perform the opposite operation to all operations performed in
731 the specified transaction. Uses the last transaction (with the
732 highest ID) if more than one transaction for given <pack‐
733 age-file-spec> is found. If it is not possible to undo some
734 operations due to the current state of RPMDB, it will not undo
735 the transaction.
736 dnf history userinstalled
738 Show all installonly packages, packages installed outside of DNF
739 and packages not installed as dependency. I.e. it lists packages
740 that will stay on the system when Auto Remove Command or Remove
741 Command along with clean_requirements_on_remove configuration
742 option set to True is executed. Note the same results can be
743 accomplished with dnf repoquery --userinstalled, and the repo‐
744 query command is more powerful in formatting of the output.
745 This command by default does not force a sync of expired metadata,
747 except for the redo, rollback, and undo subcommands. See also Metadata
748 Synchronization and Configuration Files Replacement Policy.
749 Info Command
751 dnf [options] info [<package-file-spec>...]
752 Lists description and summary information about installed and
753 available packages.
754 The info command limits the displayed packages the same way as the list
756 command.
757 This command by default does not force a sync of expired metadata. See
759 also Metadata Synchronization.
760 Install Command
762 dnf [options] install <spec>...
763 Makes sure that the given packages and their dependencies are
764 installed on the system. Each <spec> can be either a
765 <package-spec>, or a @<module-spec>, or a @<group-spec>. See
766 Install Examples. If a given package or provide cannot be (and
767 is not already) installed, the exit code will be non-zero. If
768 the <spec> matches both a @<module-spec> and a @<group-spec>,
769 only the module is installed.
770 When <package-spec> to specify the exact version of the package
772 is given, DNF will install the desired version, no matter which
773 version of the package is already installed. The former version
774 of the package will be removed in the case of non-installonly
775 package.
776 There are also a few specific install commands install-n,
778 install-na and install-nevra that allow the specification of an
779 exact argument in the NEVRA format.
780 See also Configuration Files Replacement Policy.
782 Install Examples
784 dnf install tito
785 Install the tito package (tito is the package name).
786 dnf install ~/Downloads/tito-0.6.2-1.fc22.noarch.rpm
788 Install a local rpm file tito-0.6.2-1.fc22.noarch.rpm from the
789 ~/Downloads/ directory.
790 dnf install tito-0.5.6-1.fc22
792 Install the package with a specific version. If the package is
793 already installed it will automatically try to downgrade or
794 upgrade to the specific version.
795 dnf --best install tito
797 Install the latest available version of the package. If the
798 package is already installed it will try to automatically
799 upgrade to the latest version. If the latest version of the
800 package cannot be installed, the installation will fail.
801 dnf install vim
803 DNF will automatically recognize that vim is not a package name,
804 but will look up and install a package that provides vim with
805 all the required dependencies. Note: Package name match has
806 precedence over package provides match.
807 dnf install https://kojipkgs.fedoraproject.org//pack‐
809 ages/tito/0.6.0/1.fc22/noarch/tito-0.6.0-1.fc22.noarch.rpm
810 Install a package directly from a URL.
811 dnf install '@docker'
813 Install all default profiles of module 'docker' and their RPMs.
814 Module streams get enabled accordingly.
815 dnf install '@Web Server'
817 Install the 'Web Server' environmental group.
818 dnf install /usr/bin/rpmsign
820 Install a package that provides the /usr/bin/rpmsign file.
821 dnf -y install tito --setopt=install_weak_deps=False
823 Install the tito package (tito is the package name) without weak
824 deps. Weak deps are not required for core functionality of the
825 package, but they enhance the original package (like extended
826 documentation, plugins, additional functions, etc.).
827 dnf install --advisory=FEDORA-2018-b7b99fe852 \*
829 Install all packages that belong to the "FEDORA-2018-b7b99fe852"
830 advisory.
831 List Command
833 Prints lists of packages depending on the packages' relation to the
834 system. A package is installed if it is present in the RPMDB, and it is
835 available if it is not installed but is present in a repository that
836 DNF knows about.
837 The list command also limits the displayed packages according to spe‐
839 cific criteria, e.g. to only those that update an installed package
840 (respecting the repository priority). The exclude option in the config‐
841 uration file can influence the result, but if the --disableexcludes
842 command line option is used, it ensures that all installed packages
843 will be listed.
844 dnf [options] list [--all] [<package-file-spec>...]
846 Lists all packages, present in the RPMDB, in a repository or
847 both.
848 dnf [options] list --installed [<package-file-spec>...]
850 Lists installed packages.
851 dnf [options] list --available [<package-file-spec>...]
853 Lists available packages.
854 dnf [options] list --extras [<package-file-spec>...]
856 Lists extras, that is packages installed on the system that are
857 not available in any known repository.
858 dnf [options] list --obsoletes [<package-file-spec>...]
860 List packages installed on the system that are obsoleted by
861 packages in any known repository.
862 dnf [options] list --recent [<package-file-spec>...]
864 List packages recently added into the repositories.
865 dnf [options] list --upgrades [<package-file-spec>...]
867 List upgrades available for the installed packages.
868 dnf [options] list --autoremove
870 List packages which will be removed by the dnf autoremove com‐
871 mand.
872 This command by default does not force a sync of expired metadata. See
874 also Metadata Synchronization.
875 Localinstall Command
877 dnf [options] localinstall <spec>...
878 Deprecated alias for the Install Command.
879 Makecache Command
881 dnf [options] makecache
882 Downloads and caches metadata for all known repos. Tries to
883 avoid downloading whenever possible (e.g. when the local meta‐
884 data hasn't expired yet or when the metadata timestamp hasn't
885 changed).
886 dnf [options] makecache --timer
888 Like plain makecache, but instructs DNF to be more
889 resource-aware, meaning it will not do anything if running on
890 battery power and will terminate immediately if it's too soon
891 after the last successful makecache run (see dnf.conf(5), meta‐
892 data_timer_sync).
893 Mark Command
895 dnf mark install <package-spec>...
896 Marks the specified packages as installed by user. This can be
897 useful if any package was installed as a dependency and is
898 desired to stay on the system when Auto Remove Command or Remove
899 Command along with clean_requirements_on_remove configuration
900 option set to True is executed.
901 dnf mark remove <package-spec>...
903 Unmarks the specified packages as installed by user. Whenever
904 you as a user don't need a specific package you can mark it for
905 removal. The package stays installed on the system but will be
906 removed when Auto Remove Command or Remove Command along with
907 clean_requirements_on_remove configuration option set to True is
908 executed. You should use this operation instead of Remove Com‐
909 mand if you're not sure whether the package is a requirement of
910 other user installed packages on the system.
911 dnf mark group <package-spec>...
913 Marks the specified packages as installed by group. This can be
914 useful if any package was installed as a dependency or a user
915 and is desired to be protected and handled as a group member
916 like during group remove.
917 Module Command
919 Modularity overview is available at man page dnf.modularity(7). Module
920 subcommands take <module-spec>... arguments that specify modules or
921 profiles.
922 dnf [options] module install <module-spec>...
924 Install module profiles, including their packages. In case no
925 profile was provided, all default profiles get installed. Mod‐
926 ule streams get enabled accordingly.
927 This command cannot be used for switching module streams. It is
929 recommended to remove all installed content from the module and
930 reset the module using the reset command. After you reset the
931 module, you can install the other stream.
932 dnf [options] module update <module-spec>...
934 Update packages associated with an active module stream, option‐
935 ally restricted to a profile. If the profile_name is provided,
936 only the packages referenced by that profile will be updated.
937 dnf [options] module remove <module-spec>...
939 Remove installed module profiles, including packages that were
940 installed with the dnf module install command. Will not remove
941 packages required by other installed module profiles or by other
942 user-installed packages. In case no profile was provided, all
943 installed profiles get removed.
944 dnf [options] module remove --all <module-spec>...
946 Remove installed module profiles, including packages that were
947 installed with the dnf module install command. With --all
948 option it additionally removes all packages whose names are pro‐
949 vided by specified modules. Packages required by other installed
950 module profiles and packages whose names are also provided by
951 any other module are not removed.
952 dnf [options] module enable <module-spec>...
954 Enable a module stream and make the stream RPMs available in the
955 package set.
956 Modular dependencies are resolved, dependencies checked and also
958 recursively enabled. In case of modular dependency issue the
959 operation will be rejected. To perform the action anyway please
960 use --skip-broken option.
961 This command cannot be used for switching module streams. It is
963 recommended to remove all installed content from the module, and
964 reset the module using the reset command. After you reset the
965 module, you can enable the other stream.
966 dnf [options] module disable <module-name>...
968 Disable a module. All related module streams will become
969 unavailable. Consequently, all installed profiles will be
970 removed and the module RPMs will become unavailable in the pack‐
971 age set. In case of modular dependency issue the operation will
972 be rejected. To perform the action anyway please use -‐
973 -skip-broken option.
974 dnf [options] module reset <module-name>...
976 Reset module state so it's no longer enabled or disabled. Con‐
977 sequently, all installed profiles will be removed and only RPMs
978 from the default stream will be available in the package set.
979 dnf [options] module provides <package-name-spec>...
981 Lists all modular packages matching <package-name-spec> from all
982 modules (including disabled), along with the modules and streams
983 they belong to.
984 dnf [options] module list [--all] [module_name...]
986 Lists all module streams, their profiles and states (enabled,
987 disabled, default).
988 dnf [options] module list --enabled [module_name...]
990 Lists module streams that are enabled.
991 dnf [options] module list --disabled [module_name...]
993 Lists module streams that are disabled.
994 dnf [options] module list --installed [module_name...]
996 List module streams with installed profiles.
997 dnf [options] module info <module-spec>...
999 Print detailed information about given module stream.
1000 dnf [options] module info --profile <module-spec>...
1002 Print detailed information about given module profiles.
1003 dnf [options] module repoquery <module-spec>...
1005 List all available packages belonging to selected modules.
1006 dnf [options] module repoquery --available <module-spec>...
1008 List all available packages belonging to selected modules.
1009 dnf [options] module repoquery --installed <module-spec>...
1011 List all installed packages with same name like packages belong‐
1012 ing to selected modules.
1013 Provides Command
1015 dnf [options] provides <provide-spec>
1016 Finds the packages providing the given <provide-spec>. This is
1017 useful when one knows a filename and wants to find what package
1018 (installed or not) provides this file. The <provide-spec> is
1019 gradually looked for at following locations:
1020 1. The <provide-spec> is matched with all file provides of any
1022 available package:
1023 $ dnf provides /usr/bin/gzip
1025 gzip-1.9-9.fc29.x86_64 : The GNU data compression program
1026 Matched from:
1027 Filename : /usr/bin/gzip
1028 2. Then all provides of all available packages are searched:
1030 $ dnf provides "gzip(x86-64)"
1032 gzip-1.9-9.fc29.x86_64 : The GNU data compression program
1033 Matched from:
1034 Provide : gzip(x86-64) = 1.9-9.fc29
1035 3. DNF assumes that the <provide-spec> is a system command,
1037 prepends it with /usr/bin/, /usr/sbin/ prefixes (one at a
1038 time) and does the file provides search again. For legacy
1039 reasons (packages that didn't do UsrMove) also /bin and /sbin
1040 prefixes are being searched:
1041 $ dnf provides zless
1043 gzip-1.9-9.fc29.x86_64 : The GNU data compression program
1044 Matched from:
1045 Filename : /usr/bin/zless
1046 4. If this last step also fails, DNF returns "Error: No Matches
1048 found".
1049 This command by default does not force a sync of expired meta‐
1051 data. See also Metadata Synchronization.
1052 Reinstall Command
1054 dnf [options] reinstall <package-spec>...
1055 Installs the specified packages, fails if some of the packages
1056 are either not installed or not available (i.e. there is no
1057 repository where to download the same RPM).
1058 Remove Command
1060 dnf [options] remove <package-spec>...
1061 Removes the specified packages from the system along with any
1062 packages depending on the packages being removed. Each <spec>
1063 can be either a <package-spec>, which specifies a package
1064 directly, or a @<group-spec>, which specifies an (environment)
1065 group which contains it. If clean_requirements_on_remove is
1066 enabled (the default), also removes any dependencies that are no
1067 longer needed.
1068 dnf [options] remove --duplicates
1070 Removes older versions of duplicate packages. To ensure the
1071 integrity of the system it reinstalls the newest package. In
1072 some cases the command cannot resolve conflicts. In such cases
1073 the dnf shell command with remove --duplicates and upgrade
1074 dnf-shell sub-commands could help.
1075 dnf [options] remove --oldinstallonly
1077 Removes old installonly packages, keeping only latest versions
1078 and version of running kernel.
1079 There are also a few specific remove commands remove-n,
1081 remove-na and remove-nevra that allow the specification of an
1082 exact argument in the NEVRA format.
1083 Remove Examples
1085 dnf remove acpi tito
1086 Remove the acpi and tito packages.
1087 dnf remove $(dnf repoquery --extras --exclude=tito,acpi)
1089 Remove packages not present in any repository, but don't remove
1090 the tito and acpi packages (they still might be removed if they
1091 depend on some of the removed packages).
1092 Remove older versions of duplicated packages (an equivalent of yum's
1094 package-cleanup --cleandups):
1095 dnf remove --duplicates
1097 Repoinfo Command
1099 An alias for the repolist command that provides more detailed infor‐
1100 mation like dnf repolist -v.
1101 Repolist Command
1103 dnf [options] repolist [--enabled|--disabled|--all]
1104 Depending on the exact command lists enabled, disabled or all
1105 known repositories. Lists all enabled repositories by default.
1106 Provides more detailed information when -v option is used.
1107 This command by default does not force a sync of expired metadata. See
1109 also Metadata Synchronization.
1110 Repoquery Command
1112 dnf [options] repoquery [<select-options>] [<query-options>] [<pack‐
1113 age-file-spec>]
1114 Searches available DNF repositories for selected packages and
1115 displays the requested information about them. It is an equiva‐
1116 lent of rpm -q for remote repositories.
1117 dnf [options] repoquery --querytags
1119 Provides the list of tags recognized by the --queryformat repo‐
1120 query option.
1121 There are also a few specific repoquery commands repoquery-n,
1123 repoquery-na and repoquery-nevra that allow the specification of
1124 an exact argument in the NEVRA format (does not affect arguments
1125 of options like --whatprovides <arg>, ...).
1126 Select Options
1128 Together with <package-file-spec>, control what packages are displayed
1129 in the output. If <package-file-spec> is given, limits the resulting
1130 set of packages to those matching the specification. All packages are
1131 considered if no <package-file-spec> is specified.
1132 <package-file-spec>
1134 Package specification in the NEVRA format (name[-[epoch:]ver‐
1135 sion[-release]][.arch]), a package provide or a file provide.
1136 See Specifying Packages.
1137 -a, --all
1139 Query all packages (for rpmquery compatibility, also a shorthand
1140 for repoquery '*' or repoquery without arguments).
1141 --arch <arch>[,<arch>...], --archlist <arch>[,<arch>...]
1143 Limit the resulting set only to packages of selected architec‐
1144 tures (default is all architectures). In some cases the result
1145 is affected by the basearch of the running system, therefore to
1146 run repoquery for an arch incompatible with your system use the
1147 --forcearch=<arch> option to change the basearch.
1148 --duplicates
1150 Limit the resulting set to installed duplicate packages (i.e.
1151 more package versions for the same name and architecture).
1152 Installonly packages are excluded from this set.
1153 --unneeded
1155 Limit the resulting set to leaves packages that were installed
1156 as dependencies so they are no longer needed. This switch lists
1157 packages that are going to be removed after executing the dnf
1158 autoremove command.
1159 --available
1161 Limit the resulting set to available packages only (set by
1162 default).
1163 --disable-modular-filtering
1165 Disables filtering of modular packages, so that packages of
1166 inactive module streams are included in the result.
1167 --extras
1169 Limit the resulting set to packages that are not present in any
1170 of the available repositories.
1171 -f <file>, --file <file>
1173 Limit the resulting set only to the package that owns <file>.
1174 --installed
1176 Limit the resulting set to installed packages only. The exclude
1177 option in the configuration file might influence the result, but
1178 if the command line option --disableexcludes is used, it
1179 ensures that all installed packages will be listed.
1180 --installonly
1182 Limit the resulting set to installed installonly packages.
1183 --latest-limit <number>
1185 Limit the resulting set to <number> of latest packages for every
1186 package name and architecture. If <number> is negative, skip
1187 <number> of latest packages. For a negative <number> use the
1188 --latest-limit=<number> syntax.
1189 --recent
1191 Limit the resulting set to packages that were recently edited.
1192 --repo <repoid>
1194 Limit the resulting set only to packages from a repository iden‐
1195 tified by <repoid>. Can be used multiple times with accumula‐
1196 tive effect.
1197 --unsatisfied
1199 Report unsatisfied dependencies among installed packages (i.e.
1200 missing requires and and existing conflicts).
1201 --upgrades
1203 Limit the resulting set to packages that provide an upgrade for
1204 some already installed package.
1205 --userinstalled
1207 Limit the resulting set to packages installed by the user. The
1208 exclude option in the configuration file might influence the
1209 result, but if the command line option --disableexcludes is
1210 used, it ensures that all installed packages will be listed.
1211 --whatdepends <capability>[,<capability>...]
1213 Limit the resulting set only to packages that require, enhance,
1214 recommend, suggest or supplement any of <capabilities>.
1215 --whatconflicts <capability>[,<capability>...]
1217 Limit the resulting set only to packages that conflict with any
1218 of <capabilities>.
1219 --whatenhances <capability>[,<capability>...]
1221 Limit the resulting set only to packages that enhance any of
1222 <capabilities>. Use --whatdepends if you want to list all
1223 depending packages.
1224 --whatobsoletes <capability>[,<capability>...]
1226 Limit the resulting set only to packages that obsolete any of
1227 <capabilities>.
1228 --whatprovides <capability>[,<capability>...]
1230 Limit the resulting set only to packages that provide any of
1231 <capabilities>.
1232 --whatrecommends <capability>[,<capability>...]
1234 Limit the resulting set only to packages that recommend any of
1235 <capabilities>. Use --whatdepends if you want to list all
1236 depending packages.
1237 --whatrequires <capability>[,<capability>...]
1239 Limit the resulting set only to packages that require any of
1240 <capabilities>. Use --whatdepends if you want to list all
1241 depending packages.
1242 --whatsuggests <capability>[,<capability>...]
1244 Limit the resulting set only to packages that suggest any of
1245 <capabilities>. Use --whatdepends if you want to list all
1246 depending packages.
1247 --whatsupplements <capability>[,<capability>...]
1249 Limit the resulting set only to packages that supplement any of
1250 <capabilities>. Use --whatdepends if you want to list all
1251 depending packages.
1252 --alldeps
1254 This option is stackable with --whatrequires or --whatdepends
1255 only. Additionally it adds all packages requiring the package
1256 features to the result set (used as default).
1257 --exactdeps
1259 This option is stackable with --whatrequires or --whatdepends
1260 only. Limit the resulting set only to packages that require
1261 <capability> specified by --whatrequires.
1262 --srpm Operate on the corresponding source RPM.
1264 Query Options
1266 Set what information is displayed about each package.
1267 The following are mutually exclusive, i.e. at most one can be speci‐
1269 fied. If no query option is given, matching packages are displayed in
1270 the standard NEVRA notation.
1271 -i, --info
1273 Show detailed information about the package.
1274 -l, --list
1276 Show the list of files in the package.
1277 -s, --source
1279 Show the package source RPM name.
1280 --changelogs
1282 Print the package changelogs.
1283 --conflicts
1285 Display capabilities that the package conflicts with. Same as
1286 --qf "%{conflicts}.
1287 --depends
1289 Display capabilities that the package depends on, enhances, rec‐
1290 ommends, suggests or supplements.
1291 --enhances
1293 Display capabilities enhanced by the package. Same as --qf
1294 "%{enhances}"".
1295 --location
1297 Show a location where the package could be downloaded from.
1298 --obsoletes
1300 Display capabilities that the package obsoletes. Same as --qf
1301 "%{obsoletes}".
1302 --provides
1304 Display capabilities provided by the package. Same as --qf
1305 "%{provides}".
1306 --recommends
1308 Display capabilities recommended by the package. Same as --qf
1309 "%{recommends}".
1310 --requires
1312 Display capabilities that the package depends on. Same as --qf
1313 "%{requires}".
1314 --requires-pre
1316 Display capabilities that the package depends on for running a
1317 %pre script. Same as --qf "%{requires-pre}".
1318 --suggests
1320 Display capabilities suggested by the package. Same as --qf
1321 "%{suggests}".
1322 --supplements
1324 Display capabilities supplemented by the package. Same as --qf
1325 "%{supplements}".
1326 --tree Display a recursive tree of packages with capabilities specified
1328 by one of the following supplementary options: --whatrequires,
1329 --requires, --conflicts, --enhances, --suggests, --provides,
1330 --supplements, --recommends.
1331 --deplist
1333 Produce a list of all direct dependencies and what packages pro‐
1334 vide those dependencies for the given packages. The result only
1335 shows the newest providers (which can be changed by using --ver‐
1336 bose).
1337 --nvr Show found packages in the name-version-release format. Same as
1339 --qf "%{name}-%{version}-%{release}".
1340 --nevra
1342 Show found packages in the name-epoch:version-release.architec‐
1343 ture format. Same as --qf "%{name}-%{epoch}:%{ver‐
1344 sion}-%{release}.%{arch}" (default).
1345 --envra
1347 Show found packages in the epoch:name-version-release.architec‐
1348 ture format. Same as --qf "%{epoch}:%{name}-%{ver‐
1349 sion}-%{release}.%{arch}"
1350 --qf <format>, --queryformat <format>
1352 Custom display format. <format> is the string to output for each
1353 matched package. Every occurrence of %{<tag>} within is replaced
1354 by the corresponding attribute of the package. The list of rec‐
1355 ognized tags can be displayed by running dnf repoquery --query‐
1356 tags.
1357 --recursive
1359 Query packages recursively. Has to be used with --whatrequires
1360 <REQ> (optionally with --alldeps, but not with --exactdeps) or
1361 with --requires <REQ> --resolve.
1362 --resolve
1364 resolve capabilities to originating package(s).
1365 Examples
1367 Display NEVRAs of all available packages matching light*:
1368 dnf repoquery 'light*'
1370 Display NEVRAs of all available packages matching name light* and
1372 architecture noarch (accepts only arguments in the "<name>.<arch>" for‐
1373 mat):
1374 dnf repoquery-na 'light*.noarch'
1376 Display requires of all lighttpd packages:
1378 dnf repoquery --requires lighttpd
1380 Display packages providing the requires of python packages:
1382 dnf repoquery --requires python --resolve
1384 Display source rpm of ligttpd package:
1386 dnf repoquery --source lighttpd
1388 Display package name that owns the given file:
1390 dnf repoquery --file /etc/lighttpd/lighttpd.conf
1392 Display name, architecture and the containing repository of all
1394 lighttpd packages:
1395 dnf repoquery --queryformat '%{name}.%{arch} : %{reponame}' lighttpd
1397 Display all available packages providing "webserver":
1399 dnf repoquery --whatprovides webserver
1401 Display all available packages providing "webserver" but only for
1403 "i686" architecture:
1404 dnf repoquery --whatprovides webserver --arch i686
1406 Display duplicate packages:
1408 dnf repoquery --duplicates
1410 Display source packages that require a <provide> for a build:
1412 dnf repoquery --disablerepo="*" --enablerepo="*-source" --arch=src --whatrequires <provide>
1414 Repo-Pkgs Command
1416 dnf [options] repo-pkgs
1417 Deprecated alias for the Repository-Packages Command.
1418 Repository-Packages Command
1420 The repository-packages command allows the user to run commands on top
1421 of all packages in the repository named <repoid>. However, any depen‐
1422 dency resolution takes into account packages from all enabled reposito‐
1423 ries. The <package-file-spec> and <package-spec> specifications further
1424 limit the candidates to only those packages matching at least one of
1425 them.
1426 The info subcommand lists description and summary information about
1428 packages depending on the packages' relation to the repository. The
1429 list subcommand just prints lists of those packages.
1430 dnf [options] repository-packages <repoid> check-update [<pack‐
1432 age-file-spec>...]
1433 Non-interactively checks if updates of the specified packages in
1434 the repository are available. DNF exit code will be 100 when
1435 there are updates available and a list of the updates will be
1436 printed.
1437 dnf [options] repository-packages <repoid> info [--all] [<pack‐
1439 age-file-spec>...]
1440 List all related packages.
1441 dnf [options] repository-packages <repoid> info --installed [<pack‐
1443 age-file-spec>...]
1444 List packages installed from the repository.
1445 dnf [options] repository-packages <repoid> info --available [<pack‐
1447 age-file-spec>...]
1448 List packages available in the repository but not currently
1449 installed on the system.
1450 dnf [options] repository-packages <repoid> info --extras [<pack‐
1452 age-file-specs>...]
1453 List packages installed from the repository that are not avail‐
1454 able in any repository.
1455 dnf [options] repository-packages <repoid> info --obsoletes [<pack‐
1457 age-file-spec>...]
1458 List packages in the repository that obsolete packages installed
1459 on the system.
1460 dnf [options] repository-packages <repoid> info --recent [<pack‐
1462 age-file-spec>...]
1463 List packages recently added into the repository.
1464 dnf [options] repository-packages <repoid> info --upgrades [<pack‐
1466 age-file-spec>...]
1467 List packages in the repository that upgrade packages installed
1468 on the system.
1469 dnf [options] repository-packages <repoid> install [<package-spec>...]
1471 Install all packages in the repository.
1472 dnf [options] repository-packages <repoid> list [--all] [<pack‐
1474 age-file-spec>...]
1475 List all related packages.
1476 dnf [options] repository-packages <repoid> list --installed [<pack‐
1478 age-file-spec>...]
1479 List packages installed from the repository.
1480 dnf [options] repository-packages <repoid> list --available [<pack‐
1482 age-file-spec>...]
1483 List packages available in the repository but not currently
1484 installed on the system.
1485 dnf [options] repository-packages <repoid> list --extras [<pack‐
1487 age-file-spec>...]
1488 List packages installed from the repository that are not avail‐
1489 able in any repository.
1490 dnf [options] repository-packages <repoid> list --obsoletes [<pack‐
1492 age-file-spec>...]
1493 List packages in the repository that obsolete packages installed
1494 on the system.
1495 dnf [options] repository-packages <repoid> list --recent [<pack‐
1497 age-file-spec>...]
1498 List packages recently added into the repository.
1499 dnf [options] repository-packages <repoid> list --upgrades [<pack‐
1501 age-file-spec>...]
1502 List packages in the repository that upgrade packages installed
1503 on the system.
1504 dnf [options] repository-packages <repoid> move-to [<package-spec>...]
1506 Reinstall all those packages that are available in the reposi‐
1507 tory.
1508 dnf [options] repository-packages <repoid> reinstall [<pack‐
1510 age-spec>...]
1511 Run the reinstall-old subcommand. If it fails, run the move-to
1512 subcommand.
1513 dnf [options] repository-packages <repoid> reinstall-old [<pack‐
1515 age-spec>...]
1516 Reinstall all those packages that were installed from the repos‐
1517 itory and simultaneously are available in the repository.
1518 dnf [options] repository-packages <repoid> remove [<package-spec>...]
1520 Remove all packages installed from the repository along with any
1521 packages depending on the packages being removed. If
1522 clean_requirements_on_remove is enabled (the default) also
1523 removes any dependencies that are no longer needed.
1524 dnf [options] repository-packages <repoid> remove-or-distro-sync
1526 [<package-spec>...]
1527 Select all packages installed from the repository. Upgrade,
1528 downgrade or keep those of them that are available in another
1529 repository to match the latest version available there and
1530 remove the others along with any packages depending on the pack‐
1531 ages being removed. If clean_requirements_on_remove is enabled
1532 (the default) also removes any dependencies that are no longer
1533 needed.
1534 dnf [options] repository-packages <repoid> remove-or-reinstall [<pack‐
1536 age-spec>...]
1537 Select all packages installed from the repository. Reinstall
1538 those of them that are available in another repository and
1539 remove the others along with any packages depending on the pack‐
1540 ages being removed. If clean_requirements_on_remove is enabled
1541 (the default) also removes any dependencies that are no longer
1542 needed.
1543 dnf [options] repository-packages <repoid> upgrade [<package-spec>...]
1545 Update all packages to the highest resolvable version available
1546 in the repository.
1547 dnf [options] repository-packages <repoid> upgrade-to <pack‐
1549 age-nevr-specs>...
1550 Update packages to the specified versions that are available in
1551 the repository. Upgrade-to is a deprecated alias for the upgrade
1552 subcommand.
1553 Search Command
1555 dnf [options] search [--all] <keywords>...
1556 Search package metadata for keywords. Keywords are matched as
1557 case-insensitive substrings, globbing is supported. By default
1558 lists packages that match all requested keys (AND operation).
1559 Keys are searched in package names and summaries. If the
1560 "--all" option is used, lists packages that match at least one
1561 of the keys (an OR operation). In addition the keys are
1562 searched in the package descriptions and URLs. The result is
1563 sorted from the most relevant results to the least.
1564 This command by default does not force a sync of expired metadata. See
1566 also Metadata Synchronization.
1567 Shell Command
1569 dnf [options] shell [filename]
1570 Open an interactive shell for conducting multiple commands dur‐
1571 ing a single execution of DNF. These commands can be issued man‐
1572 ually or passed to DNF from a file. The commands are much the
1573 same as the normal DNF command line options. There are a few
1574 additional commands documented below.
1575 config [conf-option] [value]
1577 · Set a configuration option to a requested value. If no
1579 value is given it prints the current value.
1580 repo [list|enable|disable] [repo-id]
1582 · list: list repositories and their status
1584 · enable: enable repository
1586 · disable: disable repository
1588 transaction [list|reset|solve|run]
1590 · list: resolve and list the content of the transaction
1592 · reset: reset the transaction
1594 · run: resolve and run the transaction
1596 Note that all local packages must be used in the first shell
1598 transaction subcommand (e.g. install /tmp/nodejs-1-1.x86_64.rpm
1599 /tmp/acpi-1-1.noarch.rpm) otherwise an error will occur. Any
1600 disable, enable, and reset module operations (e.g. module enable
1601 nodejs) must also be performed before any other shell transac‐
1602 tion subcommand is used.
1603 Swap Command
1605 dnf [options] swap <remove-spec> <install-spec>
1606 Remove spec and install spec in one transaction. Each <spec> can be
1607 either a <package-spec>, which specifies a package directly, or a
1608 @<group-spec>, which specifies an (environment) group which contains
1609 it. Automatic conflict solving is provided in DNF by the --allow‐
1610 erasing option that provides the functionality of the swap command
1611 automatically.
1612 Update Command
1614 dnf [options] update
1615 Deprecated alias for the Upgrade Command.
1616 Updateinfo Command
1618 dnf [options] updateinfo [--summary|--list|--info] [<availability>]
1619 [<spec>...]
1620 Display information about update advisories.
1621 Depending on the output type, DNF displays just counts of advi‐
1623 sory types (omitted or --summary), list of advisories (--list)
1624 or detailed information (--info). When the -v option is used
1625 with --info, the information is even more detailed.
1626 <availability> specifies whether advisories about newer versions
1628 of installed packages (omitted or --available), advisories about
1629 equal and older versions of installed packages (--installed),
1630 advisories about newer versions of those installed packages for
1631 which a newer version is available (--updates) or advisories
1632 about any versions of installed packages (--all) are taken into
1633 account. Most of the time, --available and --updates displays
1634 the same output. The outputs differ only in the cases when an
1635 advisory refers to a newer version but there is no enabled
1636 repository which contains any newer version.
1637 Note, that --available tooks only the latest installed versions
1639 of packages into account. In case of the kernel packages (when
1640 multiple version could be installed simultaneously) also pack‐
1641 ages of the currently running version of kernel are added.
1642 To print only advisories referencing a CVE or a bugzilla use
1644 --with-cve or --with-bz options. When these switches are used
1645 also the output of the --list is altered - the ID of the CVE or
1646 the bugzilla is printed instead of the one of the advisory.
1647 If given and if neither ID, type (bugfix, enhancement, secu‐
1649 rity/sec) nor a package name of an advisory matches <spec>, the
1650 advisory is not taken into account. The matching is case-sensi‐
1651 tive and in the case of advisory IDs and package names, globbing
1652 is supported.
1653 Output of the --summary option is affected by the autocheck_run‐
1655 ning_kernel configuration option.
1656 Update-Minimal Command
1658 dnf [options] update-minimal
1659 Deprecated alias for the Upgrade-Minimal Command.
1660 Upgrade Command
1662 dnf [options] upgrade
1663 Updates each package to the latest version that is both avail‐
1664 able and resolvable.
1665 dnf [options] upgrade <package-spec>...
1667 Updates each specified package to the latest available version.
1668 Updates dependencies as necessary.
1669 dnf [options] upgrade <package-nevr-specs>...
1671 Upgrades packages to the specified versions.
1672 dnf [options] upgrade @<spec>...
1674 Alias for the dnf module update command.
1675 If the main obsoletes configure option is true or the --obsoletes flag
1677 is present, dnf will include package obsoletes in its calculations.
1678 For more information see obsoletes.
1679 See also Configuration Files Replacement Policy.
1681 Upgrade-Minimal Command
1683 dnf [options] upgrade-minimal
1684 Updates each package to the latest available version that pro‐
1685 vides a bugfix, enhancement or a fix for a security issue (secu‐
1686 rity).
1687 dnf [options] upgrade-minimal <package-spec>...
1689 Updates each specified package to the latest available version
1690 that provides a bugfix, enhancement or a fix for security issue
1691 (security). Updates dependencies as necessary.
1692 Update-To Command
1694 dnf [options] update-to <package-nevr-specs>...
1695 Deprecated alias for the Upgrade Command.
1696 Upgrade-To Command
1698 dnf [options] upgrade-to <package-nevr-specs>...
1699 Deprecated alias for the Upgrade Command.
1700
1702 Many commands take a <package-spec> parameter that selects a package
1703 for the operation. The <package-spec> argument is matched against pack‐
1704 age NEVRAs, provides and file provides.
1705 <package-file-spec> is similar to <package-spec>, except provides
1707 matching is not performed. Therefore, <package-file-spec> is matched
1708 only against NEVRAs and file provides.
1709 <package-name-spec> is matched against NEVRAs only.
1711 Globs
1713 Package specification supports the same glob pattern matching that
1714 shell does, in all three above mentioned packages it matches against
1715 (NEVRAs, provides and file provides).
1716 The following patterns are supported:
1718 * Matches any number of characters.
1720 ? Matches any single character.
1722 [] Matches any one of the enclosed characters. A pair of characters
1724 separated by a hyphen denotes a range expression; any character
1725 that falls between those two characters, inclusive, is matched.
1726 If the first character following the [ is a ! or a ^ then any
1727 character not enclosed is matched.
1728 {} Matches any of the comma separated list of enclosed strings.
1730 NEVRA Matching
1732 When matching against NEVRAs, partial matching is supported. DNF tries
1733 to match the spec against the following list of NEVRA forms (in
1734 decreasing order of priority):
1735 · name-[epoch:]version-release.arch
1737 · name.arch
1739 · name
1741 · name-[epoch:]version-release
1743 · name-[epoch:]version
1745 Note that name can in general contain dashes (e.g. pack‐
1747 age-with-dashes).
1748 The first form that matches any packages is used and the remaining
1750 forms are not tried. If none of the forms match any packages, an
1751 attempt is made to match the <package-spec> against full package
1752 NEVRAs. This is only relevant if globs are present in the <pack‐
1753 age-spec>.
1754 <package-spec> matches NEVRAs the same way <package-name-spec> does,
1756 but in case matching NEVRAs fails, it attempts to match against pro‐
1757 vides and file provides of packages as well.
1758 You can specify globs as part of any of the five NEVRA components. You
1760 can also specify a glob pattern to match over multiple NEVRA components
1761 (in other words, to match across the NEVRA separators). In that case,
1762 however, you need to write the spec to match against full package
1763 NEVRAs, as it is not possible to split such spec into NEVRA forms.
1764
1766 Commands accepting the <package-nevr-spec> parameter need not only the
1767 name of the package, but also its version, release and optionally the
1768 architecture. Further, the version part can be preceded by an epoch
1769 when it is relevant (i.e. the epoch is non-zero).
1770
1772 <provide-spec> in command descriptions means the command operates on
1773 packages providing the given spec. This can either be an explicit pro‐
1774 vide, an implicit provide (i.e. name of the package) or a file provide.
1775 The selection is case-sensitive and globbing is supported.
1776
1778 <group-spec> allows one to select (environment) groups a particular
1779 operation should work on. It is a case insensitive string (supporting
1780 globbing characters) that is matched against a group's ID, canonical
1781 name and name translated into the current LC_MESSAGES locale (if possi‐
1782 ble).
1783
1785 <module-spec> allows one to select modules or profiles a particular
1786 operation should work on.
1787 It is in the form of NAME:STREAM:VERSION:CONTEXT:ARCH/PROFILE and sup‐
1789 ported partial forms are the following:
1790 · NAME
1792 · NAME:STREAM
1794 · NAME:STREAM:VERSION
1796 · NAME:STREAM:VERSION:CONTEXT
1798 · all above combinations with ::ARCH (e.g. NAME::ARCH)
1800 · NAME:STREAM:VERSION:CONTEXT:ARCH
1802 · all above combinations with /PROFILE (e.g. NAME/PROFILE)
1804 In case stream is not specified, the enabled or the default stream is
1806 used, in this order. In case profile is not specified, the system
1807 default profile or the 'default' profile is used.
1808
1810 <transaction-spec> can be in one of several forms. If it is an integer,
1811 it specifies a transaction ID. Specifying last is the same as specify‐
1812 ing the ID of the most recent transaction. The last form is last-<off‐
1813 set>, where <offset> is a positive integer. It specifies offset-th
1814 transaction preceding the most recent transaction.
1815
1817 Package filtering filters packages out from the available package set,
1818 making them invisible to most of dnf commands. They cannot be used in a
1819 transaction. Packages can be filtered out by either Exclude Filtering
1820 or Modular Filtering.
1821 Exclude Filtering
1823 Exclude Filtering is a mechanism used by a user or by a DNF plugin to
1824 modify the set of available packages. Exclude Filtering can be modified
1825 by either includepkgs or excludepkgs configuration options in configu‐
1826 ration files. The --disableexcludes command line option can be used to
1827 override excludes from configuration files. In addition to user-config‐
1828 ured excludes, plugins can also extend the set of excluded packages. To
1829 disable excludes from a DNF plugin you can use the --disableplugin com‐
1830 mand line option.
1831 To disable all excludes for e.g. the install command you can use the
1833 following combination of command line options:
1834 dnf --disableexcludes=all --disableplugin="*" install bash
1836 Modular Filtering
1838 Please see the modularity documentation for details on how Modular Fil‐
1839 tering works.
1840 With modularity, only RPM packages from active module streams are
1842 included in the available package set. RPM packages from inactive mod‐
1843 ule streams, as well as non-modular packages with the same name or pro‐
1844 vides as a package from an active module stream, are filtered out. Mod‐
1845 ular filtering is not applied to packages added from the command line,
1846 installed packages, or packages from repositories with module_hot‐
1847 fixes=true in their .repo file.
1848 Disabling of modular filtering is not recommended, because it could
1850 cause the system to get into a broken state. To disable modular filter‐
1851 ing for a particular repository, specify module_hotfixes=true in the
1852 .repo file or use --setopt=<repo_id>.module_hotfixes=true.
1853 To discover the module which contains an excluded package use dnf mod‐
1855 ule provides.
1856
1858 Correct operation of DNF depends on having access to up-to-date data
1859 from all enabled repositories but contacting remote mirrors on every
1860 operation considerably slows it down and costs bandwidth for both the
1861 client and the repository provider. The metadata_expire (see
1862 dnf.conf(5)) repository configuration option is used by DNF to deter‐
1863 mine whether a particular local copy of repository data is due to be
1864 re-synced. It is crucial that the repository providers set the option
1865 well, namely to a value where it is guaranteed that if particular meta‐
1866 data was available in time T on the server, then all packages it refer‐
1867 ences will still be available for download from the server in time T +
1868 metadata_expire.
1869 To further reduce the bandwidth load, some of the commands where having
1871 up-to-date metadata is not critical (e.g. the list command) do not look
1872 at whether a repository is expired and whenever any version of it is
1873 locally available to the user's account, it will be used. For non-root
1874 use, see also the --cacheonly switch. Note that in all situations the
1875 user can force synchronization of all enabled repositories with the
1876 --refresh switch.
1877
1879 The updated packages could replace the old modified configuration files
1880 with the new ones or keep the older files. Neither of the files are
1881 actually replaced. To the conflicting ones RPM gives additional suffix
1882 to the origin name. Which file should maintain the true name after
1883 transaction is not controlled by package manager but is specified by
1884 each package itself, following packaging guideline.
1885
1887 Cache Files
1888 /var/cache/dnf
1889 Main Configuration
1891 /etc/dnf/dnf.conf
1892 Repository
1894 /etc/yum.repos.d/
1895
1897 · dnf.conf(5), DNF Configuration Reference
1898 · dnf-PLUGIN(8) for documentation on DNF plugins.
1900 · dnf.modularity(7), Modularity overview.
1902 · DNF project homepage (‐
1904 https://github.com/rpm-software-management/dnf/)
1905 · How to report a bug (‐
1907 https://github.com/rpm-software-management/dnf/wiki/Bug-Reporting)
1908 · YUM project homepage (http://yum.baseurl.org/)
1910
1912 See AUTHORS in DNF source distribution.
1913
1915 2012-2020, Red Hat, Licensed under GPLv2+
19164.2.21 Apr 08, 2020 DNF(8)