1YUM(8) DNF YUM(8)
2
6 yum - redirecting to 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 Additional information:
100 • Options
102 • Specifying Packages
104 • Specifying Provides
106 • Specifying Groups
108 • Specifying Transactions
110 • Metadata Synchronization
112 • Configuration Files Replacement Policy
114 • Files
116 • See Also
118
120 -4 Resolve to IPv4 addresses only.
121 -6 Resolve to IPv6 addresses only.
123 --advisory=<advisory>, --advisories=<advisory>
125 Include packages corresponding to the advisory ID, Eg. FE‐
126 DORA-2201-123. Applicable for the install, repoquery, update‐
127 info and upgrade commands.
128 --allowerasing
130 Allow erasing of installed packages to resolve dependencies.
131 This option could be used as an alternative to the yum swap com‐
132 mand where packages to remove are not explicitly defined.
133 --assumeno
135 Automatically answer no for all questions.
136 -b, --best
138 Try the best available package versions in transactions. Specif‐
139 ically during dnf upgrade, which by default skips over updates
140 that can not be installed for dependency reasons, the switch
141 forces DNF to only consider the latest packages. When running
142 into packages with broken dependencies, DNF will fail giving a
143 reason why the latest version can not be installed.
144 --bugfix
146 Include packages that fix a bugfix issue. Applicable for the in‐
147 stall, repoquery, updateinfo and upgrade commands.
148 --bz=<bugzilla>, --bzs=<bugzilla>
150 Include packages that fix a Bugzilla ID, Eg. 123123. Applicable
151 for the install, repoquery, updateinfo and upgrade commands.
152 -C, --cacheonly
154 Run entirely from system cache, don't update the cache and use
155 it even in case it is expired.
156 DNF uses a separate cache for each user under which it executes.
158 The cache for the root user is called the system cache. This
159 switch allows a regular user read-only access to the system
160 cache, which usually is more fresh than the user's and thus he
161 does not have to wait for metadata sync.
162 --color=<color>
164 Control whether color is used in terminal output. Valid values
165 are always, never and auto (default).
166 --comment=<comment>
168 Add a comment to the transaction history.
169 -c <config file>, --config=<config file>
171 Configuration file location.
172 --cve=<cves>, --cves=<cves>
174 Include packages that fix a CVE (Common Vulnerabilities and Ex‐
175 posures) ID (http://cve.mitre.org/about/), Eg. CVE-2201-0123.
176 Applicable for the install, repoquery, updateinfo, and upgrade
177 commands.
178 -d <debug level>, --debuglevel=<debug level>
180 Debugging output level. This is an integer value between 0 (no
181 additional information strings) and 10 (shows all debugging in‐
182 formation, even that not understandable to the user), default is
183 2. Deprecated, use -v instead.
184 --debugsolver
186 Dump data aiding in dependency solver debugging into ./debug‐
187 data.
188 --disableexcludes=[all|main|<repoid>], --disableexcludep‐
190 kgs=[all|main|<repoid>]
191 Disable the configuration file excludes. Takes one of the following
192 three options:
193 • all, disables all configuration file excludes
195 • main, disables excludes defined in the [main] section
197 • repoid, disables excludes defined for the given repository
199 --disable, --set-disabled
201 Disable specified repositories (automatically saves). The option
202 has to be used together with the config-manager command
203 (dnf-plugins-core).
204 --disableplugin=<plugin names>
206 Disable the listed plugins specified by names or globs.
207 --disablerepo=<repoid>
209 Disable specific repositories by an id or a glob. This option is
210 mutually exclusive with --repo.
211 --downloaddir=<path>, --destdir=<path>
213 Redirect downloaded packages to provided directory. The option
214 has to be used together with the --downloadonly command line op‐
215 tion, with the download command (dnf-plugins-core) or with the
216 system-upgrade command (dnf-plugins-extras).
217 --downloadonly
219 Download the resolved package set without performing any rpm
220 transaction (install/upgrade/erase).
221 -e <error level>, --errorlevel=<error level>
223 Error output level. This is an integer value between 0 (no error
224 output) and 10 (shows all error messages), default is 3. Depre‐
225 cated, use -v instead.
226 --enable, --set-enabled
228 Enable specified repositories (automatically saves). The option
229 has to be used together with the config-manager command
230 (dnf-plugins-core).
231 --enableplugin=<plugin names>
233 Enable the listed plugins specified by names or globs.
234 --enablerepo=<repoid>
236 Enable additional repositories by an id or a glob.
237 --enhancement
239 Include enhancement relevant packages. Applicable for the in‐
240 stall, repoquery, updateinfo and upgrade commands.
241 -x <package-file-spec>, --exclude=<package-file-spec>
243 Exclude packages specified by <package-file-spec> from the oper‐
244 ation.
245 --excludepkgs=<package-file-spec>
247 Deprecated option. It was replaced by the --exclude option.
248 --forcearch=<arch>
250 Force the use of an architecture. Any architecture can be speci‐
251 fied. However, use of an architecture not supported natively by
252 your CPU will require emulation of some kind. This is usually
253 through QEMU. The behavior of --forcearch can be configured by
254 using the arch and ignorearch configuration options with values
255 <arch> and True respectively.
256 -h, --help, --help-cmd
258 Show the help.
259 --installroot=<path>
261 Specifies an alternative installroot, relative to where all
262 packages will be installed. Think of this like doing chroot
263 <root> dnf, except using --installroot allows dnf to work before
264 the chroot is created. It requires absolute path.
265 • cachedir, log files, releasever, and gpgkey are taken from or stored
267 in the installroot. Gpgkeys are imported into the installroot from a
268 path relative to the host which can be specified in the repository
269 section of configuration files.
270 • configuration file and reposdir are searched inside the installroot
272 first. If they are not present, they are taken from the host system.
273 Note: When a path is specified within a command line argument
274 (--config=<config file> in case of configuration file and --se‐
275 topt=reposdir=<reposdir> for reposdir) then this path is always rela‐
276 tive to the host with no exceptions.
277 • vars are taken from the host system or installroot according to re‐
279 posdir . When reposdir path is specified within a command line argu‐
280 ment, vars are taken from the installroot. When varsdir paths are
281 specified within a command line argument (--setopt=varsdir=<repos‐
282 dir>) then those path are always relative to the host with no excep‐
283 tions.
284 • The pluginpath and pluginconfpath are relative to the host.
286 Note: You may also want to use the command-line option --relea‐
287 sever=<release> when creating the installroot, otherwise the $relea‐
288 sever value is taken from the rpmdb within the installroot (and thus
289 it is empty at the time of creation and the transaction will fail).
290 If --releasever=/ is used, the releasever will be detected from the
291 host (/) system. The new installroot path at the time of creation
292 does not contain the repository, releasever and dnf.conf files.
293 On a modular system you may also want to use the --setopt=mod‐
295 ule_platform_id=<module_platform_name:stream> command-line option
296 when creating the installroot, otherwise the module_platform_id
297 value will be taken from the /etc/os-release file within the in‐
298 stallroot (and thus it will be empty at the time of creation, the
299 modular dependency could be unsatisfied and modules content could be
300 excluded).
301 Installroot examples:
303 dnf --installroot=<installroot> --releasever=<release> install sys‐
305 tem-release
306 Permanently sets the releasever of the system in the <in‐
307 stallroot> directory to <release>.
308 dnf --installroot=<installroot> --setopt=reposdir=<path> --config
310 /path/dnf.conf upgrade
311 Upgrades packages inside the installroot from a repository
312 described by --setopt using configuration from
313 /path/dnf.conf.
314 --newpackage
316 Include newpackage relevant packages. Applicable for the in‐
317 stall, repoquery, updateinfo and upgrade commands.
318 --noautoremove
320 Disable removal of dependencies that are no longer used. It sets
321 clean_requirements_on_remove configuration option to False.
322 --nobest
324 Set best option to False, so that transactions are not limited
325 to best candidates only.
326 --nodocs
328 Do not install documentation. Sets the rpm flag 'RPM‐
329 TRANS_FLAG_NODOCS'.
330 --nogpgcheck
332 Skip checking GPG signatures on packages (if RPM policy allows).
333 --noplugins
335 Disable all plugins.
336 --obsoletes
338 This option has an effect on an install/update, it enables dnf's
339 obsoletes processing logic. For more information see the obso‐
340 letes option.
341 This option also displays capabilities that the package obso‐
343 letes when used together with the repoquery command.
344 Configuration Option: obsoletes
346 -q, --quiet
348 In combination with a non-interactive command, shows just the
349 relevant content. Suppresses messages notifying about the cur‐
350 rent state or actions of DNF.
351 -R <minutes>, --randomwait=<minutes>
353 Maximum command wait time.
354 --refresh
356 Set metadata as expired before running the command.
357 --releasever=<release>
359 Configure DNF as if the distribution release was <release>. This
360 can affect cache paths, values in configuration files and mir‐
361 rorlist URLs.
362 --repofrompath <repo>,<path/url>
364 Specify a repository to add to the repositories for this query.
365 This option can be used multiple times.
366 • The repository label is specified by <repo>.
368 • The path or url to the repository is specified by <path/url>. It is
370 the same path as a baseurl and can be also enriched by the repo vari‐
371 ables.
372 • The configuration for the repository can be adjusted using -‐
374 -setopt=<repo>.<option>=<value>.
375 • If you want to view only packages from this repository, combine this
377 with the --repo=<repo> or --disablerepo="*" switches.
378 --repo=<repoid>, --repoid=<repoid>
380 Enable just specific repositories by an id or a glob. Can be
381 used multiple times with accumulative effect. It is basically a
382 shortcut for --disablerepo="*" --enablerepo=<repoid> and is mu‐
383 tually exclusive with the --disablerepo option.
384 --rpmverbosity=<name>
386 RPM debug scriptlet output level. Sets the debug level to <name>
387 for RPM scriptlets. For available levels, see the rpmverbosity
388 configuration option.
389 --sec-severity=<severity>, --secseverity=<severity>
391 Includes packages that provide a fix for an issue of the speci‐
392 fied severity. Applicable for the install, repoquery, update‐
393 info and upgrade commands.
394 --security
396 Includes packages that provide a fix for a security issue. Ap‐
397 plicable for the upgrade command.
398 --setopt=<option>=<value>
400 Override a configuration option from the configuration file. To
401 override configuration options for repositories, use repoid.op‐
402 tion for the <option>. Values for configuration options like ex‐
403 cludepkgs, includepkgs, installonlypkgs and tsflags are appended
404 to the original value, they do not override it. However, speci‐
405 fying an empty value (e.g. --setopt=tsflags=) will clear the op‐
406 tion.
407 --skip-broken
409 Resolve depsolve problems by removing packages that are causing
410 problems from the transaction. It is an alias for the strict
411 configuration option with value False. Additionally, with the
412 enable and disable module subcommands it allows one to perform
413 an action even in case of broken modular dependencies.
414 --showduplicates
416 Show duplicate packages in repositories. Applicable for the list
417 and search commands.
418 -v, --verbose
420 Verbose operation, show debug messages.
421 --version
423 Show DNF version and exit.
424 -y, --assumeyes
426 Automatically answer yes for all questions.
427 List options are comma-separated. Command-line options override respec‐
429 tive settings from configuration files.
430
432 For an explanation of <package-spec>, <package-file-spec> and <pack‐
433 age-name-spec> see Specifying Packages.
434 For an explanation of <provide-spec> see Specifying Provides.
436 For an explanation of <group-spec> see Specifying Groups.
438 For an explanation of <module-spec> see Specifying Modules.
440 For an explanation of <transaction-spec> see Specifying Transactions.
442 Alias Command
444 Command: alias
445 Allows the user to define and manage a list of aliases (in the form
448 <name=value>), which can be then used as dnf commands to abbreviate
449 longer command sequences. For examples on using the alias command, see
450 Alias Examples. For examples on the alias processing, see Alias Pro‐
451 cessing Examples.
452 To use an alias (name=value), the name must be placed as the first
454 "command" (e.g. the first argument that is not an option). It is then
455 replaced by its value and the resulting sequence is again searched for
456 aliases. The alias processing stops when the first found command is not
457 a name of any alias.
458 In case the processing would result in an infinite recursion, the orig‐
460 inal arguments are used instead.
461 Also, like in shell aliases, if the result starts with a \, the alias
463 processing will stop.
464 All aliases are defined in configuration files in the
466 /etc/dnf/aliases.d/ directory in the [aliases] section, and aliases
467 created by the alias command are written to the USER.conf file. In case
468 of conflicts, the USER.conf has the highest priority, and alphabetical
469 ordering is used for the rest of the configuration files.
470 Optionally, there is the enabled option in the [main] section default‐
472 ing to True. This can be set for each file separately in the respective
473 file, or globally for all aliases in the ALIASES.conf file.
474 dnf alias [options] [list] [<name>...]
476 List aliases with their final result. The [<alias>...] parameter
477 further limits the result to only those aliases matching it.
478 dnf alias [options] add <name=value>...
480 Create new aliases.
481 dnf alias [options] delete <name>...
483 Delete aliases.
484 Alias Examples
486 dnf alias list
487 Lists all defined aliases.
488 dnf alias add rm=remove
490 Adds a new command alias called rm which works the same as the
491 remove command.
492 dnf alias add upgrade="\upgrade --skip-broken --disableexcludes=all
494 --obsoletes"
495 Adds a new command alias called upgrade which works the same as
496 the upgrade command, with additional options. Note that the
497 original upgrade command is prefixed with a \ to prevent an in‐
498 finite loop in alias processing.
499 Alias Processing Examples
501 If there are defined aliases in=install and FORCE="--skip-broken --dis‐
502 ableexcludes=all":
503 • dnf FORCE in will be replaced with dnf --skip-broken --disableex‐
505 cludes=all install
506 • dnf in FORCE will be replaced with dnf install FORCE (which will
508 fail)
509 If there is defined alias in=install:
511 • dnf in will be replaced with dnf install
513 • dnf --repo updates in will be replaced with dnf --repo updates in
515 (which will fail)
516 Autoremove Command
518 Command: autoremove
519 Aliases for explicit NEVRA matching: autoremove-n, autoremove-na, autoremove-nevra
520 dnf [options] autoremove
523 Removes all "leaf" packages from the system that were originally in‐
524 stalled as dependencies of user-installed packages, but which are no
525 longer required by any such package.
526 Packages listed in installonlypkgs are never automatically removed by
528 this command.
529 dnf [options] autoremove <spec>...
531 This is an alias for the Remove Command command with clean_require‐
532 ments_on_remove set to True. It removes the specified packages from
533 the system along with any packages depending on the packages being
534 removed. Each <spec> can be either a <package-spec>, which specifies
535 a package directly, or a @<group-spec>, which specifies an (environ‐
536 ment) group which contains it. It also removes any dependencies that
537 are no longer needed.
538 There are also a few specific autoremove commands autoremove-n, au‐
540 toremove-na and autoremove-nevra that allow the specification of an
541 exact argument in the NEVRA (name-epoch:version-release.architec‐
542 ture) format.
543 This command by default does not force a sync of expired metadata. See
545 also Metadata Synchronization.
546 Check Command
548 Command: check
549 dnf [options] check [--dependencies] [--duplicates] [--obsoleted]
552 [--provides]
553 Checks the local packagedb and produces information on any problems
554 it finds. You can limit the checks to be performed by using the
555 --dependencies, --duplicates, --obsoleted and --provides options
556 (the default is to check everything).
557 Check-Update Command
559 Command: check-update
560 Aliases: check-upgrade
561 dnf [options] check-update [--changelogs] [<package-file-spec>...]
564 Non-interactively checks if updates of the specified packages are
565 available. If no <package-file-spec> is given, checks whether any
566 updates at all are available for your system. DNF exit code will be
567 100 when there are updates available and a list of the updates will
568 be printed, 0 if not and 1 if an error occurs. If --changelogs op‐
569 tion is specified, also changelog delta of packages about to be up‐
570 dated is printed.
571 Please note that having a specific newer version available for an
573 installed package (and reported by check-update) does not imply that
574 subsequent dnf upgrade will install it. The difference is that dnf
575 upgrade has restrictions (like package dependencies being satisfied)
576 to take into account.
577 The output is affected by the autocheck_running_kernel configuration
579 option.
580 Clean Command
582 Command: clean
583 Performs cleanup of temporary files kept for repositories. This in‐
586 cludes any such data left behind from disabled or removed repositories
587 as well as for different distribution release versions.
588 dnf clean dbcache
590 Removes cache files generated from the repository metadata. This
591 forces DNF to regenerate the cache files the next time it is
592 run.
593 dnf clean expire-cache
595 Marks the repository metadata expired. DNF will re-validate the
596 cache for each repository the next time it is used.
597 dnf clean metadata
599 Removes repository metadata. Those are the files which DNF uses
600 to determine the remote availability of packages. Using this op‐
601 tion will make DNF download all the metadata the next time it is
602 run.
603 dnf clean packages
605 Removes any cached packages from the system.
606 dnf clean all
608 Does all of the above.
609 Deplist Command
611 dnf [options] deplist [<select-options>] [<query-options>] [<pack‐
612 age-spec>]
613 Deprecated alias for dnf repoquery --deplist.
614 Distro-Sync Command
616 Command: distro-sync
617 Aliases: dsync
618 Deprecated aliases: distrosync, distribution-synchronization
619 dnf distro-sync [<package-spec>...]
622 As necessary upgrades, downgrades or keeps selected installed
623 packages to match the latest version available from any enabled
624 repository. If no package is given, all installed packages are
625 considered.
626 See also Configuration Files Replacement Policy.
628 Downgrade Command
630 Command: downgrade
631 Aliases: dg
632 dnf [options] downgrade <package-spec>...
635 Downgrades the specified packages to the highest installable
636 package of all known lower versions if possible. When version is
637 given and is lower than version of installed package then it
638 downgrades to target version.
639 Group Command
641 Command: group
642 Aliases: grp
643 Deprecated aliases: groups, grouplist, groupinstall, groupupdate, groupremove, grouperase, groupinfo
644 Groups are virtual collections of packages. DNF keeps track of groups
647 that the user selected ("marked") installed and can manipulate the com‐
648 prising packages with simple commands.
649 dnf [options] group [summary] <group-spec>
651 Display overview of how many groups are installed and available.
652 With a spec, limit the output to the matching groups. summary is
653 the default groups subcommand.
654 dnf [options] group info <group-spec>
656 Display package lists of a group. Shows which packages are in‐
657 stalled or available from a repository when -v is used.
658 dnf [options] group install [--with-optional] <group-spec>...
660 Mark the specified group installed and install packages it con‐
661 tains. Also include optional packages of the group if --with-op‐
662 tional is specified. All mandatory and Default packages will be
663 installed whenever possible. Conditional packages are installed
664 if they meet their requirement. If the group is already (par‐
665 tially) installed, the command installs the missing packages
666 from the group. Depending on the value of obsoletes configura‐
667 tion option group installation takes obsoletes into account.
668 dnf [options] group list <group-spec>...
670 List all matching groups, either among installed or available
671 groups. If nothing is specified, list all known groups. --in‐
672 stalled and --available options narrow down the requested list.
673 Records are ordered by the display_order tag defined in
674 comps.xml file. Provides a list of all hidden groups by using
675 option --hidden. Provides group IDs when the -v or --ids op‐
676 tions are used.
677 dnf [options] group remove <group-spec>...
679 Mark the group removed and remove those packages in the group
680 from the system which do not belong to another installed group
681 and were not installed explicitly by the user.
682 dnf [options] group upgrade <group-spec>...
684 Upgrades the packages from the group and upgrades the group it‐
685 self. The latter comprises of installing packages that were
686 added to the group by the distribution and removing packages
687 that got removed from the group as far as they were not in‐
688 stalled explicitly by the user.
689 Groups can also be marked installed or removed without physically ma‐
691 nipulating any packages:
692 dnf [options] group mark install <group-spec>...
694 Mark the specified group installed. No packages will be in‐
695 stalled by this command, but the group is then considered in‐
696 stalled.
697 dnf [options] group mark remove <group-spec>...
699 Mark the specified group removed. No packages will be removed by
700 this command.
701 See also Configuration Files Replacement Policy.
703 Help Command
705 Command: help
706 dnf help [<command>]
709 Displays the help text for all commands. If given a command name
710 then only displays help for that particular command.
711 History Command
713 Command: history
714 Aliases: hist
715 The history command allows the user to view what has happened in past
718 transactions and act according to this information (assuming the his‐
719 tory_record configuration option is set).
720 dnf history [list] [--reverse] [<spec>...]
722 The default history action is listing information about given
723 transactions in a table. Each <spec> can be either a <transac‐
724 tion-spec>, which specifies a transaction directly, or a <trans‐
725 action-spec>..<transaction-spec>, which specifies a range of
726 transactions, or a <package-name-spec>, which specifies a trans‐
727 action by a package which it manipulated. When no transaction is
728 specified, list all known transactions.
729 --reverse
731 The order of history list output is printed in reverse
732 order.
733 dnf history info [<spec>...]
735 Describe the given transactions. The meaning of <spec> is the
736 same as in the History List Command. When no transaction is
737 specified, describe what happened during the latest transaction.
738 dnf history redo <transaction-spec>|<package-file-spec>
740 Repeat the specified transaction. Uses the last transaction
741 (with the highest ID) if more than one transaction for given
742 <package-file-spec> is found. If it is not possible to redo some
743 operations due to the current state of RPMDB, it will not redo
744 the transaction.
745 dnf history replay [--ignore-installed] [--ignore-extras] [--skip-un‐
747 available] <filename>
748 Replay a transaction stored in file <filename> by History Store
749 Command. The replay will perform the exact same operations on
750 the packages as in the original transaction and will return with
751 an error if case of any differences in installed packages or
752 their versions. See also the Transaction JSON Format specifica‐
753 tion of the file format.
754 --ignore-installed
756 Don't check for the installed packages being in the same
757 state as those recorded in the transaction. E.g. in case
758 there is an upgrade foo-1.0 -> foo-2.0 stored in the
759 transaction, but there is foo-1.1 installed on the target
760 system.
761 --ignore-extras
763 Don't check for extra packages pulled into the transac‐
764 tion on the target system. E.g. the target system may not
765 have some dependency, which was installed on the source
766 system. The replay errors out on this by default, as the
767 transaction would not be the same.
768 --skip-unavailable
770 In case some packages stored in the transaction are not
771 available on the target system, skip them instead of er‐
772 roring out.
773 dnf history rollback <transaction-spec>|<package-file-spec>
775 Undo all transactions performed after the specified transaction.
776 Uses the last transaction (with the highest ID) if more than one
777 transaction for given <package-file-spec> is found. If it is
778 not possible to undo some transactions due to the current state
779 of RPMDB, it will not undo any transaction.
780 dnf history store [--output <output-file>] <transaction-spec>
782 Store a transaction specified by <transaction-spec>. The trans‐
783 action can later be replayed by the History Replay Command.
784 Warning: The stored transaction format is considered unstable
786 and may change at any time. It will work if the same version of
787 dnf is used to store and replay (or between versions as long as
788 it stays the same).
789 -o <output-file>, --output=<output-file> Store the serialized
791 transaction into <output-file. Default is transaction.json.
792 dnf history undo <transaction-spec>|<package-file-spec>
794 Perform the opposite operation to all operations performed in
795 the specified transaction. Uses the last transaction (with the
796 highest ID) if more than one transaction for given <pack‐
797 age-file-spec> is found. If it is not possible to undo some op‐
798 erations due to the current state of RPMDB, it will not undo the
799 transaction.
800 dnf history userinstalled
802 Show all installonly packages, packages installed outside of DNF
803 and packages not installed as dependency. I.e. it lists packages
804 that will stay on the system when Autoremove Command or Remove
805 Command along with clean_requirements_on_remove configuration
806 option set to True is executed. Note the same results can be ac‐
807 complished with dnf repoquery --userinstalled, and the repoquery
808 command is more powerful in formatting of the output.
809 This command by default does not force a sync of expired metadata, ex‐
811 cept for the redo, rollback, and undo subcommands. See also Metadata
812 Synchronization and Configuration Files Replacement Policy.
813 Info Command
815 Command: info
816 dnf [options] info [<package-file-spec>...]
819 Lists description and summary information about installed and
820 available packages.
821 The info command limits the displayed packages the same way as the list
823 command.
824 This command by default does not force a sync of expired metadata. See
826 also Metadata Synchronization.
827 Install Command
829 Command: install
830 Aliases: in
831 Aliases for explicit NEVRA matching: install-n, install-na, install-nevra
832 Deprecated aliases: localinstall
833 dnf [options] install <spec>...
836 Makes sure that the given packages and their dependencies are
837 installed on the system. Each <spec> can be either a
838 <package-spec>, or a @<module-spec>, or a @<group-spec>. See
839 Install Examples. If a given package or provide cannot be (and
840 is not already) installed, the exit code will be non-zero. If
841 the <spec> matches both a @<module-spec> and a @<group-spec>,
842 only the module is installed.
843 When <package-spec> to specify the exact version of the package
845 is given, DNF will install the desired version, no matter which
846 version of the package is already installed. The former version
847 of the package will be removed in the case of non-installonly
848 package.
849 On the other hand if <package-spec> specifies only a name, DNF
851 also takes into account packages obsoleting it when picking
852 which package to install. This behaviour is specific to the in‐
853 stall command. Note that this can lead to seemingly unexpected
854 results if a package has multiple versions and some older ver‐
855 sion is being obsoleted. It creates a split in the upgrade-path
856 and both ways are considered correct, the resulting package is
857 picked simply by lexicographical order.
858 There are also a few specific install commands install-n, in‐
860 stall-na and install-nevra that allow the specification of an
861 exact argument in the NEVRA format.
862 See also Configuration Files Replacement Policy.
864 Install Examples
866 dnf install tito
867 Install the tito package (tito is the package name).
868 dnf install ~/Downloads/tito-0.6.2-1.fc22.noarch.rpm
870 Install a local rpm file tito-0.6.2-1.fc22.noarch.rpm from the
871 ~/Downloads/ directory.
872 dnf install tito-0.5.6-1.fc22
874 Install the package with a specific version. If the package is
875 already installed it will automatically try to downgrade or up‐
876 grade to the specific version.
877 dnf --best install tito
879 Install the latest available version of the package. If the
880 package is already installed it will try to automatically up‐
881 grade to the latest version. If the latest version of the pack‐
882 age cannot be installed, the installation will fail.
883 dnf install vim
885 DNF will automatically recognize that vim is not a package name,
886 but will look up and install a package that provides vim with
887 all the required dependencies. Note: Package name match has
888 precedence over package provides match.
889 dnf install https://kojipkgs.fedoraproject.org//pack‐
891 ages/tito/0.6.0/1.fc22/noarch/tito-0.6.0-1.fc22.noarch.rpm
892 Install a package directly from a URL.
893 dnf install '@docker'
895 Install all default profiles of module 'docker' and their RPMs.
896 Module streams get enabled accordingly.
897 dnf install '@Web Server'
899 Install the 'Web Server' environmental group.
900 dnf install /usr/bin/rpmsign
902 Install a package that provides the /usr/bin/rpmsign file.
903 dnf -y install tito --setopt=install_weak_deps=False
905 Install the tito package (tito is the package name) without weak
906 deps. Weak deps are not required for core functionality of the
907 package, but they enhance the original package (like extended
908 documentation, plugins, additional functions, etc.).
909 dnf install --advisory=FEDORA-2018-b7b99fe852 \*
911 Install all packages that belong to the "FEDORA-2018-b7b99fe852"
912 advisory.
913 List Command
915 Command: list
916 Aliases: ls
917 Prints lists of packages depending on the packages' relation to the
920 system. A package is installed if it is present in the RPMDB, and it is
921 available if it is not installed but is present in a repository that
922 DNF knows about.
923 The list command also limits the displayed packages according to spe‐
925 cific criteria, e.g. to only those that update an installed package
926 (respecting the repository priority). The exclude option in the config‐
927 uration file can influence the result, but if the --disableexcludes
928 command line option is used, it ensures that all installed packages
929 will be listed.
930 dnf [options] list [--all] [<package-file-spec>...]
932 Lists all packages, present in the RPMDB, in a repository or
933 both.
934 dnf [options] list --installed [<package-file-spec>...]
936 Lists installed packages.
937 dnf [options] list --available [<package-file-spec>...]
939 Lists available packages.
940 dnf [options] list --extras [<package-file-spec>...]
942 Lists extras, that is packages installed on the system that are
943 not available in any known repository.
944 dnf [options] list --obsoletes [<package-file-spec>...]
946 List packages installed on the system that are obsoleted by
947 packages in any known repository.
948 dnf [options] list --recent [<package-file-spec>...]
950 List packages recently added into the repositories.
951 dnf [options] list --upgrades [<package-file-spec>...]
953 List upgrades available for the installed packages.
954 dnf [options] list --autoremove
956 List packages which will be removed by the dnf autoremove com‐
957 mand.
958 This command by default does not force a sync of expired metadata. See
960 also Metadata Synchronization.
961 Makecache Command
963 Command: makecache
964 Aliases: mc
965 dnf [options] makecache
968 Downloads and caches metadata for enabled repositories. Tries to
969 avoid downloading whenever possible (e.g. when the local meta‐
970 data hasn't expired yet or when the metadata timestamp hasn't
971 changed).
972 dnf [options] makecache --timer
974 Like plain makecache, but instructs DNF to be more re‐
975 source-aware, meaning it will not do anything if running on bat‐
976 tery power and will terminate immediately if it's too soon after
977 the last successful makecache run (see dnf.conf(5), meta‐
978 data_timer_sync).
979 Mark Command
981 Command: mark
982 dnf mark install <package-spec>...
985 Marks the specified packages as installed by user. This can be
986 useful if any package was installed as a dependency and is de‐
987 sired to stay on the system when Autoremove Command or Remove
988 Command along with clean_requirements_on_remove configuration
989 option set to True is executed.
990 dnf mark remove <package-spec>...
992 Unmarks the specified packages as installed by user. Whenever
993 you as a user don't need a specific package you can mark it for
994 removal. The package stays installed on the system but will be
995 removed when Autoremove Command or Remove Command along with
996 clean_requirements_on_remove configuration option set to True is
997 executed. You should use this operation instead of Remove Com‐
998 mand if you're not sure whether the package is a requirement of
999 other user installed packages on the system.
1000 dnf mark group <package-spec>...
1002 Marks the specified packages as installed by group. This can be
1003 useful if any package was installed as a dependency or a user
1004 and is desired to be protected and handled as a group member
1005 like during group remove.
1006 Module Command
1008 Command: module
1009 Modularity overview is available at man page dnf.modularity(7). Module
1012 subcommands take <module-spec>... arguments that specify modules or
1013 profiles.
1014 dnf [options] module install <module-spec>...
1016 Install module profiles, including their packages. In case no
1017 profile was provided, all default profiles get installed. Mod‐
1018 ule streams get enabled accordingly.
1019 This command cannot be used for switching module streams. Use
1021 the dnf module switch-to command for that.
1022 dnf [options] module update <module-spec>...
1024 Update packages associated with an active module stream, option‐
1025 ally restricted to a profile. If the profile_name is provided,
1026 only the packages referenced by that profile will be updated.
1027 dnf [options] module switch-to <module-spec>...
1029 Switch to or enable a module stream, change versions of in‐
1030 stalled packages to versions provided by the new stream, and re‐
1031 move packages from the old stream that are no longer available.
1032 It also updates installed profiles if they are available for the
1033 new stream. When a profile was provided, it installs that pro‐
1034 file and does not update any already installed profiles.
1035 This command can be used as a stronger version of the dnf module
1037 enable command, which not only enables modules, but also does a
1038 distrosync to all modular packages in the enabled modules.
1039 It can also be used as a stronger version of the dnf module in‐
1041 stall command, but it requires to specify profiles that are sup‐
1042 posed to be installed, because switch-to command does not use
1043 default profiles. The switch-to command doesn't only install
1044 profiles, it also makes a distrosync to all modular packages in
1045 the installed module.
1046 dnf [options] module remove <module-spec>...
1048 Remove installed module profiles, including packages that were
1049 installed with the dnf module install command. Will not remove
1050 packages required by other installed module profiles or by other
1051 user-installed packages. In case no profile was provided, all
1052 installed profiles get removed.
1053 dnf [options] module remove --all <module-spec>...
1055 Remove installed module profiles, including packages that were
1056 installed with the dnf module install command. With --all op‐
1057 tion it additionally removes all packages whose names are pro‐
1058 vided by specified modules. Packages required by other installed
1059 module profiles and packages whose names are also provided by
1060 any other module are not removed.
1061 dnf [options] module enable <module-spec>...
1063 Enable a module stream and make the stream RPMs available in the
1064 package set.
1065 Modular dependencies are resolved, dependencies checked and also
1067 recursively enabled. In case of modular dependency issue the op‐
1068 eration will be rejected. To perform the action anyway please
1069 use --skip-broken option.
1070 This command cannot be used for switching module streams. Use
1072 the dnf module switch-to command for that.
1073 dnf [options] module disable <module-name>...
1075 Disable a module. All related module streams will become un‐
1076 available. Consequently, all installed profiles will be removed
1077 and the module RPMs will become unavailable in the package set.
1078 In case of modular dependency issue the operation will be re‐
1079 jected. To perform the action anyway please use --skip-broken
1080 option.
1081 dnf [options] module reset <module-name>...
1083 Reset module state so it's no longer enabled or disabled. Con‐
1084 sequently, all installed profiles will be removed and only RPMs
1085 from the default stream will be available in the package set.
1086 dnf [options] module provides <package-name-spec>...
1088 Lists all modular packages matching <package-name-spec> from all
1089 modules (including disabled), along with the modules and streams
1090 they belong to.
1091 dnf [options] module list [--all] [module_name...]
1093 Lists all module streams, their profiles and states (enabled,
1094 disabled, default).
1095 dnf [options] module list --enabled [module_name...]
1097 Lists module streams that are enabled.
1098 dnf [options] module list --disabled [module_name...]
1100 Lists module streams that are disabled.
1101 dnf [options] module list --installed [module_name...]
1103 List module streams with installed profiles.
1104 dnf [options] module info <module-spec>...
1106 Print detailed information about given module stream.
1107 dnf [options] module info --profile <module-spec>...
1109 Print detailed information about given module profiles.
1110 dnf [options] module repoquery <module-spec>...
1112 List all available packages belonging to selected modules.
1113 dnf [options] module repoquery --available <module-spec>...
1115 List all available packages belonging to selected modules.
1116 dnf [options] module repoquery --installed <module-spec>...
1118 List all installed packages with same name like packages belong‐
1119 ing to selected modules.
1120 Provides Command
1122 Command: provides
1123 Aliases: prov, whatprovides
1124 dnf [options] provides <provide-spec>
1127 Finds the packages providing the given <provide-spec>. This is
1128 useful when one knows a filename and wants to find what package
1129 (installed or not) provides this file. The <provide-spec> is
1130 gradually looked for at following locations:
1131 1. The <provide-spec> is matched with all file provides of any
1133 available package:
1134 $ dnf provides /usr/bin/gzip
1136 gzip-1.9-9.fc29.x86_64 : The GNU data compression program
1137 Matched from:
1138 Filename : /usr/bin/gzip
1139 2. Then all provides of all available packages are searched:
1141 $ dnf provides "gzip(x86-64)"
1143 gzip-1.9-9.fc29.x86_64 : The GNU data compression program
1144 Matched from:
1145 Provide : gzip(x86-64) = 1.9-9.fc29
1146 3. DNF assumes that the <provide-spec> is a system command,
1148 prepends it with /usr/bin/, /usr/sbin/ prefixes (one at a
1149 time) and does the file provides search again. For legacy
1150 reasons (packages that didn't do UsrMove) also /bin and /sbin
1151 prefixes are being searched:
1152 $ dnf provides zless
1154 gzip-1.9-9.fc29.x86_64 : The GNU data compression program
1155 Matched from:
1156 Filename : /usr/bin/zless
1157 4. If this last step also fails, DNF returns "Error: No Matches
1159 found".
1160 This command by default does not force a sync of expired meta‐
1162 data. See also Metadata Synchronization.
1163 Reinstall Command
1165 Command: reinstall
1166 Aliases: rei
1167 dnf [options] reinstall <package-spec>...
1170 Installs the specified packages, fails if some of the packages
1171 are either not installed or not available (i.e. there is no
1172 repository where to download the same RPM).
1173 Remove Command
1175 Command: remove
1176 Aliases: rm
1177 Aliases for explicit NEVRA matching: remove-n, remove-na, remove-nevra
1178 Deprecated aliases: erase, erase-n, erase-na, erase-nevra
1179 dnf [options] remove <package-spec>...
1182 Removes the specified packages from the system along with any
1183 packages depending on the packages being removed. Each <spec>
1184 can be either a <package-spec>, which specifies a package di‐
1185 rectly, or a @<group-spec>, which specifies an (environment)
1186 group which contains it. If clean_requirements_on_remove is en‐
1187 abled (the default), also removes any dependencies that are no
1188 longer needed.
1189 dnf [options] remove --duplicates
1191 Removes older versions of duplicate packages. To ensure the in‐
1192 tegrity of the system it reinstalls the newest package. In some
1193 cases the command cannot resolve conflicts. In such cases the
1194 dnf shell command with remove --duplicates and upgrade dnf-shell
1195 sub-commands could help.
1196 dnf [options] remove --oldinstallonly
1198 Removes old installonly packages, keeping only latest versions
1199 and version of running kernel.
1200 There are also a few specific remove commands remove-n, re‐
1202 move-na and remove-nevra that allow the specification of an ex‐
1203 act argument in the NEVRA format.
1204 Remove Examples
1206 dnf remove acpi tito
1207 Remove the acpi and tito packages.
1208 dnf remove $(dnf repoquery --extras --exclude=tito,acpi)
1210 Remove packages not present in any repository, but don't remove
1211 the tito and acpi packages (they still might be removed if they
1212 depend on some of the removed packages).
1213 Remove older versions of duplicated packages (an equivalent of yum's
1215 package-cleanup --cleandups):
1216 dnf remove --duplicates
1218 Repoinfo Command
1220 Command: repoinfo
1221 An alias for the repolist command that provides more detailed infor‐
1223 mation like dnf repolist -v.
1224 Repolist Command
1226 Command: repolist
1227 dnf [options] repolist [--enabled|--disabled|--all]
1230 Depending on the exact command lists enabled, disabled or all
1231 known repositories. Lists all enabled repositories by default.
1232 Provides more detailed information when -v option is used.
1233 This command by default does not force a sync of expired metadata. See
1235 also Metadata Synchronization.
1236 Repoquery Command
1238 Command: repoquery
1239 Aliases: rq
1240 Aliases for explicit NEVRA matching: repoquery-n, repoquery-na, repoquery-nevra
1241 dnf [options] repoquery [<select-options>] [<query-options>] [<pack‐
1244 age-file-spec>]
1245 Searches available DNF repositories for selected packages and
1246 displays the requested information about them. It is an equiva‐
1247 lent of rpm -q for remote repositories.
1248 dnf [options] repoquery --querytags
1250 Provides the list of tags recognized by the --queryformat repo‐
1251 query option.
1252 There are also a few specific repoquery commands repoquery-n,
1254 repoquery-na and repoquery-nevra that allow the specification of
1255 an exact argument in the NEVRA format (does not affect arguments
1256 of options like --whatprovides <arg>, ...).
1257 Select Options
1259 Together with <package-file-spec>, control what packages are displayed
1260 in the output. If <package-file-spec> is given, limits the resulting
1261 set of packages to those matching the specification. All packages are
1262 considered if no <package-file-spec> is specified.
1263 <package-file-spec>
1265 Package specification in the NEVRA format (name[-[epoch:]ver‐
1266 sion[-release]][.arch]), a package provide or a file provide.
1267 See Specifying Packages.
1268 -a, --all
1270 Query all packages (for rpmquery compatibility, also a shorthand
1271 for repoquery '*' or repoquery without arguments).
1272 --arch <arch>[,<arch>...], --archlist <arch>[,<arch>...]
1274 Limit the resulting set only to packages of selected architec‐
1275 tures (default is all architectures). In some cases the result
1276 is affected by the basearch of the running system, therefore to
1277 run repoquery for an arch incompatible with your system use the
1278 --forcearch=<arch> option to change the basearch.
1279 --duplicates
1281 Limit the resulting set to installed duplicate packages (i.e.
1282 more package versions for the same name and architecture). In‐
1283 stallonly packages are excluded from this set.
1284 --unneeded
1286 Limit the resulting set to leaves packages that were installed
1287 as dependencies so they are no longer needed. This switch lists
1288 packages that are going to be removed after executing the dnf
1289 autoremove command.
1290 --available
1292 Limit the resulting set to available packages only (set by de‐
1293 fault).
1294 --disable-modular-filtering
1296 Disables filtering of modular packages, so that packages of in‐
1297 active module streams are included in the result.
1298 --extras
1300 Limit the resulting set to packages that are not present in any
1301 of the available repositories.
1302 -f <file>, --file <file>
1304 Limit the resulting set only to the package that owns <file>.
1305 --installed
1307 Limit the resulting set to installed packages only. The exclude
1308 option in the configuration file might influence the result, but
1309 if the command line option --disableexcludes is used, it en‐
1310 sures that all installed packages will be listed.
1311 --installonly
1313 Limit the resulting set to installed installonly packages.
1314 --latest-limit <number>
1316 Limit the resulting set to <number> of latest packages for every
1317 package name and architecture. If <number> is negative, skip
1318 <number> of latest packages. For a negative <number> use the
1319 --latest-limit=<number> syntax.
1320 --recent
1322 Limit the resulting set to packages that were recently edited.
1323 --repo <repoid>
1325 Limit the resulting set only to packages from a repository iden‐
1326 tified by <repoid>. Can be used multiple times with accumula‐
1327 tive effect.
1328 --unsatisfied
1330 Report unsatisfied dependencies among installed packages (i.e.
1331 missing requires and and existing conflicts).
1332 --upgrades
1334 Limit the resulting set to packages that provide an upgrade for
1335 some already installed package.
1336 --userinstalled
1338 Limit the resulting set to packages installed by the user. The
1339 exclude option in the configuration file might influence the re‐
1340 sult, but if the command line option --disableexcludes is used,
1341 it ensures that all installed packages will be listed.
1342 --whatdepends <capability>[,<capability>...]
1344 Limit the resulting set only to packages that require, enhance,
1345 recommend, suggest or supplement any of <capabilities>.
1346 --whatconflicts <capability>[,<capability>...]
1348 Limit the resulting set only to packages that conflict with any
1349 of <capabilities>.
1350 --whatenhances <capability>[,<capability>...]
1352 Limit the resulting set only to packages that enhance any of
1353 <capabilities>. Use --whatdepends if you want to list all de‐
1354 pending packages.
1355 --whatobsoletes <capability>[,<capability>...]
1357 Limit the resulting set only to packages that obsolete any of
1358 <capabilities>.
1359 --whatprovides <capability>[,<capability>...]
1361 Limit the resulting set only to packages that provide any of
1362 <capabilities>.
1363 --whatrecommends <capability>[,<capability>...]
1365 Limit the resulting set only to packages that recommend any of
1366 <capabilities>. Use --whatdepends if you want to list all de‐
1367 pending packages.
1368 --whatrequires <capability>[,<capability>...]
1370 Limit the resulting set only to packages that require any of
1371 <capabilities>. Use --whatdepends if you want to list all de‐
1372 pending packages.
1373 --whatsuggests <capability>[,<capability>...]
1375 Limit the resulting set only to packages that suggest any of
1376 <capabilities>. Use --whatdepends if you want to list all de‐
1377 pending packages.
1378 --whatsupplements <capability>[,<capability>...]
1380 Limit the resulting set only to packages that supplement any of
1381 <capabilities>. Use --whatdepends if you want to list all de‐
1382 pending packages.
1383 --alldeps
1385 This option is stackable with --whatrequires or --whatdepends
1386 only. Additionally it adds all packages requiring the package
1387 features to the result set (used as default).
1388 --exactdeps
1390 This option is stackable with --whatrequires or --whatdepends
1391 only. Limit the resulting set only to packages that require <ca‐
1392 pability> specified by --whatrequires.
1393 --srpm Operate on the corresponding source RPM.
1395 Query Options
1397 Set what information is displayed about each package.
1398 The following are mutually exclusive, i.e. at most one can be speci‐
1400 fied. If no query option is given, matching packages are displayed in
1401 the standard NEVRA notation.
1402 -i, --info
1404 Show detailed information about the package.
1405 -l, --list
1407 Show the list of files in the package.
1408 -s, --source
1410 Show the package source RPM name.
1411 --changelogs
1413 Print the package changelogs.
1414 --conflicts
1416 Display capabilities that the package conflicts with. Same as
1417 --qf "%{conflicts}.
1418 --depends
1420 Display capabilities that the package depends on, enhances, rec‐
1421 ommends, suggests or supplements.
1422 --enhances
1424 Display capabilities enhanced by the package. Same as --qf
1425 "%{enhances}"".
1426 --location
1428 Show a location where the package could be downloaded from.
1429 --obsoletes
1431 Display capabilities that the package obsoletes. Same as --qf
1432 "%{obsoletes}".
1433 --provides
1435 Display capabilities provided by the package. Same as --qf
1436 "%{provides}".
1437 --recommends
1439 Display capabilities recommended by the package. Same as --qf
1440 "%{recommends}".
1441 --requires
1443 Display capabilities that the package depends on. Same as --qf
1444 "%{requires}".
1445 --requires-pre
1447 Display capabilities that the package depends on for running a
1448 %pre script. Same as --qf "%{requires-pre}".
1449 --suggests
1451 Display capabilities suggested by the package. Same as --qf
1452 "%{suggests}".
1453 --supplements
1455 Display capabilities supplemented by the package. Same as --qf
1456 "%{supplements}".
1457 --tree Display a recursive tree of packages with capabilities specified
1459 by one of the following supplementary options: --whatrequires,
1460 --requires, --conflicts, --enhances, --suggests, --provides,
1461 --supplements, --recommends.
1462 --deplist
1464 Produce a list of all direct dependencies and what packages pro‐
1465 vide those dependencies for the given packages. The result only
1466 shows the newest providers (which can be changed by using --ver‐
1467 bose).
1468 --nvr Show found packages in the name-version-release format. Same as
1470 --qf "%{name}-%{version}-%{release}".
1471 --nevra
1473 Show found packages in the name-epoch:version-release.architec‐
1474 ture format. Same as --qf "%{name}-%{epoch}:%{version}-%{re‐
1475 lease}.%{arch}" (default).
1476 --envra
1478 Show found packages in the epoch:name-version-release.architec‐
1479 ture format. Same as --qf "%{epoch}:%{name}-%{version}-%{re‐
1480 lease}.%{arch}"
1481 --qf <format>, --queryformat <format>
1483 Custom display format. <format> is the string to output for each
1484 matched package. Every occurrence of %{<tag>} within is replaced
1485 by the corresponding attribute of the package. The list of rec‐
1486 ognized tags can be displayed by running dnf repoquery --query‐
1487 tags.
1488 --recursive
1490 Query packages recursively. Has to be used with --whatrequires
1491 <REQ> (optionally with --alldeps, but not with --exactdeps) or
1492 with --requires <REQ> --resolve.
1493 --resolve
1495 resolve capabilities to originating package(s).
1496 Examples
1498 Display NEVRAs of all available packages matching light*:
1499 dnf repoquery 'light*'
1501 Display NEVRAs of all available packages matching name light* and ar‐
1503 chitecture noarch (accepts only arguments in the "<name>.<arch>" for‐
1504 mat):
1505 dnf repoquery-na 'light*.noarch'
1507 Display requires of all lighttpd packages:
1509 dnf repoquery --requires lighttpd
1511 Display packages providing the requires of python packages:
1513 dnf repoquery --requires python --resolve
1515 Display source rpm of ligttpd package:
1517 dnf repoquery --source lighttpd
1519 Display package name that owns the given file:
1521 dnf repoquery --file /etc/lighttpd/lighttpd.conf
1523 Display name, architecture and the containing repository of all
1525 lighttpd packages:
1526 dnf repoquery --queryformat '%{name}.%{arch} : %{reponame}' lighttpd
1528 Display all available packages providing "webserver":
1530 dnf repoquery --whatprovides webserver
1532 Display all available packages providing "webserver" but only for
1534 "i686" architecture:
1535 dnf repoquery --whatprovides webserver --arch i686
1537 Display duplicate packages:
1539 dnf repoquery --duplicates
1541 Display source packages that require a <provide> for a build:
1543 dnf repoquery --disablerepo="*" --enablerepo="*-source" --arch=src --whatrequires <provide>
1545 Repository-Packages Command
1547 Command: repository-packages
1548 Deprecated aliases: repo-pkgs, repo-packages, repository-pkgs
1549 The repository-packages command allows the user to run commands on top
1552 of all packages in the repository named <repoid>. However, any depen‐
1553 dency resolution takes into account packages from all enabled reposito‐
1554 ries. The <package-file-spec> and <package-spec> specifications further
1555 limit the candidates to only those packages matching at least one of
1556 them.
1557 The info subcommand lists description and summary information about
1559 packages depending on the packages' relation to the repository. The
1560 list subcommand just prints lists of those packages.
1561 dnf [options] repository-packages <repoid> check-update [<pack‐
1563 age-file-spec>...]
1564 Non-interactively checks if updates of the specified packages in
1565 the repository are available. DNF exit code will be 100 when
1566 there are updates available and a list of the updates will be
1567 printed.
1568 dnf [options] repository-packages <repoid> info [--all] [<pack‐
1570 age-file-spec>...]
1571 List all related packages.
1572 dnf [options] repository-packages <repoid> info --installed [<pack‐
1574 age-file-spec>...]
1575 List packages installed from the repository.
1576 dnf [options] repository-packages <repoid> info --available [<pack‐
1578 age-file-spec>...]
1579 List packages available in the repository but not currently in‐
1580 stalled on the system.
1581 dnf [options] repository-packages <repoid> info --extras [<pack‐
1583 age-file-specs>...]
1584 List packages installed from the repository that are not avail‐
1585 able in any repository.
1586 dnf [options] repository-packages <repoid> info --obsoletes [<pack‐
1588 age-file-spec>...]
1589 List packages in the repository that obsolete packages installed
1590 on the system.
1591 dnf [options] repository-packages <repoid> info --recent [<pack‐
1593 age-file-spec>...]
1594 List packages recently added into the repository.
1595 dnf [options] repository-packages <repoid> info --upgrades [<pack‐
1597 age-file-spec>...]
1598 List packages in the repository that upgrade packages installed
1599 on the system.
1600 dnf [options] repository-packages <repoid> install [<package-spec>...]
1602 Install all packages in the repository.
1603 dnf [options] repository-packages <repoid> list [--all] [<pack‐
1605 age-file-spec>...]
1606 List all related packages.
1607 dnf [options] repository-packages <repoid> list --installed [<pack‐
1609 age-file-spec>...]
1610 List packages installed from the repository.
1611 dnf [options] repository-packages <repoid> list --available [<pack‐
1613 age-file-spec>...]
1614 List packages available in the repository but not currently in‐
1615 stalled on the system.
1616 dnf [options] repository-packages <repoid> list --extras [<pack‐
1618 age-file-spec>...]
1619 List packages installed from the repository that are not avail‐
1620 able in any repository.
1621 dnf [options] repository-packages <repoid> list --obsoletes [<pack‐
1623 age-file-spec>...]
1624 List packages in the repository that obsolete packages installed
1625 on the system.
1626 dnf [options] repository-packages <repoid> list --recent [<pack‐
1628 age-file-spec>...]
1629 List packages recently added into the repository.
1630 dnf [options] repository-packages <repoid> list --upgrades [<pack‐
1632 age-file-spec>...]
1633 List packages in the repository that upgrade packages installed
1634 on the system.
1635 dnf [options] repository-packages <repoid> move-to [<package-spec>...]
1637 Reinstall all those packages that are available in the reposi‐
1638 tory.
1639 dnf [options] repository-packages <repoid> reinstall [<pack‐
1641 age-spec>...]
1642 Run the reinstall-old subcommand. If it fails, run the move-to
1643 subcommand.
1644 dnf [options] repository-packages <repoid> reinstall-old [<pack‐
1646 age-spec>...]
1647 Reinstall all those packages that were installed from the repos‐
1648 itory and simultaneously are available in the repository.
1649 dnf [options] repository-packages <repoid> remove [<package-spec>...]
1651 Remove all packages installed from the repository along with any
1652 packages depending on the packages being removed. If clean_re‐
1653 quirements_on_remove is enabled (the default) also removes any
1654 dependencies that are no longer needed.
1655 dnf [options] repository-packages <repoid> remove-or-distro-sync
1657 [<package-spec>...]
1658 Select all packages installed from the repository. Upgrade,
1659 downgrade or keep those of them that are available in another
1660 repository to match the latest version available there and re‐
1661 move the others along with any packages depending on the pack‐
1662 ages being removed. If clean_requirements_on_remove is enabled
1663 (the default) also removes any dependencies that are no longer
1664 needed.
1665 dnf [options] repository-packages <repoid> remove-or-reinstall [<pack‐
1667 age-spec>...]
1668 Select all packages installed from the repository. Reinstall
1669 those of them that are available in another repository and re‐
1670 move the others along with any packages depending on the pack‐
1671 ages being removed. If clean_requirements_on_remove is enabled
1672 (the default) also removes any dependencies that are no longer
1673 needed.
1674 dnf [options] repository-packages <repoid> upgrade [<package-spec>...]
1676 Update all packages to the highest resolvable version available
1677 in the repository. When versions are specified in the <pack‐
1678 age-spec>, update to these versions.
1679 dnf [options] repository-packages <repoid> upgrade-to [<pack‐
1681 age-specs>...]
1682 A deprecated alias for the upgrade subcommand.
1683 Search Command
1685 Command: search
1686 Aliases: se
1687 dnf [options] search [--all] <keywords>...
1690 Search package metadata for keywords. Keywords are matched as
1691 case-insensitive substrings, globbing is supported. By default
1692 lists packages that match all requested keys (AND operation).
1693 Keys are searched in package names and summaries. If the
1694 "--all" option is used, lists packages that match at least one
1695 of the keys (an OR operation). In addition the keys are
1696 searched in the package descriptions and URLs. The result is
1697 sorted from the most relevant results to the least.
1698 This command by default does not force a sync of expired metadata. See
1700 also Metadata Synchronization.
1701 Shell Command
1703 Command: shell
1704 Aliases: sh
1705 dnf [options] shell [filename]
1708 Open an interactive shell for conducting multiple commands dur‐
1709 ing a single execution of DNF. These commands can be issued man‐
1710 ually or passed to DNF from a file. The commands are much the
1711 same as the normal DNF command line options. There are a few ad‐
1712 ditional commands documented below.
1713 config [conf-option] [value]
1715 • Set a configuration option to a requested value. If no
1717 value is given it prints the current value.
1718 repo [list|enable|disable] [repo-id]
1720 • list: list repositories and their status
1722 • enable: enable repository
1724 • disable: disable repository
1726 transaction [list|reset|solve|run]
1728 • list: resolve and list the content of the transaction
1730 • reset: reset the transaction
1732 • run: resolve and run the transaction
1734 Note that all local packages must be used in the first shell
1736 transaction subcommand (e.g. install /tmp/nodejs-1-1.x86_64.rpm
1737 /tmp/acpi-1-1.noarch.rpm) otherwise an error will occur. Any
1738 disable, enable, and reset module operations (e.g. module enable
1739 nodejs) must also be performed before any other shell transac‐
1740 tion subcommand is used.
1741 Swap Command
1743 Command: swap
1744 dnf [options] swap <remove-spec> <install-spec>
1747 Remove spec and install spec in one transaction. Each <spec> can be
1748 either a <package-spec>, which specifies a package directly, or a
1749 @<group-spec>, which specifies an (environment) group which contains
1750 it. Automatic conflict solving is provided in DNF by the --allow‐
1751 erasing option that provides the functionality of the swap command
1752 automatically.
1753 Updateinfo Command
1755 Command: updateinfo
1756 Deprecated aliases: list-updateinfo, list-security, list-sec, info-updateinfo, info-security, info-sec, summary-updateinfo
1757 dnf [options] updateinfo [--summary|--list|--info] [<availability>]
1760 [<spec>...]
1761 Display information about update advisories.
1762 Depending on the output type, DNF displays just counts of advi‐
1764 sory types (omitted or --summary), list of advisories (--list)
1765 or detailed information (--info). The -v option extends the out‐
1766 put. When used with --info, the information is even more de‐
1767 tailed. When used with --list, an additional column with date of
1768 the last advisory update is added.
1769 <availability> specifies whether advisories about newer versions
1771 of installed packages (omitted or --available), advisories about
1772 equal and older versions of installed packages (--installed),
1773 advisories about newer versions of those installed packages for
1774 which a newer version is available (--updates) or advisories
1775 about any versions of installed packages (--all) are taken into
1776 account. Most of the time, --available and --updates displays
1777 the same output. The outputs differ only in the cases when an
1778 advisory refers to a newer version but there is no enabled
1779 repository which contains any newer version.
1780 Note, that --available tooks only the latest installed versions
1782 of packages into account. In case of the kernel packages (when
1783 multiple version could be installed simultaneously) also pack‐
1784 ages of the currently running version of kernel are added.
1785 To print only advisories referencing a CVE or a bugzilla use
1787 --with-cve or --with-bz options. When these switches are used
1788 also the output of the --list is altered - the ID of the CVE or
1789 the bugzilla is printed instead of the one of the advisory.
1790 If given and if neither ID, type (bugfix, enhancement, secu‐
1792 rity/sec) nor a package name of an advisory matches <spec>, the
1793 advisory is not taken into account. The matching is case-sensi‐
1794 tive and in the case of advisory IDs and package names, globbing
1795 is supported.
1796 Output of the --summary option is affected by the autocheck_run‐
1798 ning_kernel configuration option.
1799 Upgrade Command
1801 Command: upgrade
1802 Aliases: up
1803 Deprecated aliases: update, upgrade-to, update-to, localupdate
1804 dnf [options] upgrade
1807 Updates each package to the latest version that is both avail‐
1808 able and resolvable.
1809 dnf [options] upgrade <package-spec>...
1811 Updates each specified package to the latest available version.
1812 Updates dependencies as necessary. When versions are specified
1813 in the <package-spec>, update to these versions.
1814 dnf [options] upgrade @<spec>...
1816 Alias for the dnf module update command.
1817 If the main obsoletes configure option is true or the --obsoletes flag
1819 is present, dnf will include package obsoletes in its calculations.
1820 For more information see obsoletes.
1821 See also Configuration Files Replacement Policy.
1823 Upgrade-Minimal Command
1825 Command: upgrade-minimal
1826 Aliases: up-min
1827 Deprecated aliases: update-minimal
1828 dnf [options] upgrade-minimal
1831 Updates each package to the latest available version that pro‐
1832 vides a bugfix, enhancement or a fix for a security issue (secu‐
1833 rity).
1834 dnf [options] upgrade-minimal <package-spec>...
1836 Updates each specified package to the latest available version
1837 that provides a bugfix, enhancement or a fix for security issue
1838 (security). Updates dependencies as necessary.
1839
1841 Many commands take a <package-spec> parameter that selects a package
1842 for the operation. The <package-spec> argument is matched against pack‐
1843 age NEVRAs, provides and file provides.
1844 <package-file-spec> is similar to <package-spec>, except provides
1846 matching is not performed. Therefore, <package-file-spec> is matched
1847 only against NEVRAs and file provides.
1848 <package-name-spec> is matched against NEVRAs only.
1850 Globs
1852 Package specification supports the same glob pattern matching that
1853 shell does, in all three above mentioned packages it matches against
1854 (NEVRAs, provides and file provides).
1855 The following patterns are supported:
1857 * Matches any number of characters.
1859 ? Matches any single character.
1861 [] Matches any one of the enclosed characters. A pair of characters
1863 separated by a hyphen denotes a range expression; any character
1864 that falls between those two characters, inclusive, is matched.
1865 If the first character following the [ is a ! or a ^ then any
1866 character not enclosed is matched.
1867 Note: Curly brackets ({}) are not supported. You can still use them in
1869 shells that support them and let the shell do the expansion, but if
1870 quoted or escaped, dnf will not expand them.
1871 NEVRA Matching
1873 When matching against NEVRAs, partial matching is supported. DNF tries
1874 to match the spec against the following list of NEVRA forms (in de‐
1875 creasing order of priority):
1876 • name-[epoch:]version-release.arch
1878 • name.arch
1880 • name
1882 • name-[epoch:]version-release
1884 • name-[epoch:]version
1886 Note that name can in general contain dashes (e.g. pack‐
1888 age-with-dashes).
1889 The first form that matches any packages is used and the remaining
1891 forms are not tried. If none of the forms match any packages, an at‐
1892 tempt is made to match the <package-spec> against full package NEVRAs.
1893 This is only relevant if globs are present in the <package-spec>.
1894 <package-spec> matches NEVRAs the same way <package-name-spec> does,
1896 but in case matching NEVRAs fails, it attempts to match against pro‐
1897 vides and file provides of packages as well.
1898 You can specify globs as part of any of the five NEVRA components. You
1900 can also specify a glob pattern to match over multiple NEVRA components
1901 (in other words, to match across the NEVRA separators). In that case,
1902 however, you need to write the spec to match against full package
1903 NEVRAs, as it is not possible to split such spec into NEVRA forms.
1904 Specifying NEVRA Matching Explicitly
1906 Some commands (autoremove, install, remove and repoquery) also have
1907 aliases with suffixes -n, -na and -nevra that allow to explicitly spec‐
1908 ify how to parse the arguments:
1909 • Command install-n only matches against name.
1911 • Command install-na only matches against name.arch.
1913 • Command install-nevra only matches against name-[epoch:]version-re‐
1915 lease.arch.
1916
1918 <provide-spec> in command descriptions means the command operates on
1919 packages providing the given spec. This can either be an explicit pro‐
1920 vide, an implicit provide (i.e. name of the package) or a file provide.
1921 The selection is case-sensitive and globbing is supported.
1922
1924 <group-spec> allows one to select (environment) groups a particular op‐
1925 eration should work on. It is a case insensitive string (supporting
1926 globbing characters) that is matched against a group's ID, canonical
1927 name and name translated into the current LC_MESSAGES locale (if possi‐
1928 ble).
1929
1931 <module-spec> allows one to select modules or profiles a particular op‐
1932 eration should work on.
1933 It is in the form of NAME:STREAM:VERSION:CONTEXT:ARCH/PROFILE and sup‐
1935 ported partial forms are the following:
1936 • NAME
1938 • NAME:STREAM
1940 • NAME:STREAM:VERSION
1942 • NAME:STREAM:VERSION:CONTEXT
1944 • all above combinations with ::ARCH (e.g. NAME::ARCH)
1946 • NAME:STREAM:VERSION:CONTEXT:ARCH
1948 • all above combinations with /PROFILE (e.g. NAME/PROFILE)
1950 In case stream is not specified, the enabled or the default stream is
1952 used, in this order. In case profile is not specified, the system de‐
1953 fault profile or the 'default' profile is used.
1954
1956 <transaction-spec> can be in one of several forms. If it is an integer,
1957 it specifies a transaction ID. Specifying last is the same as specify‐
1958 ing the ID of the most recent transaction. The last form is last-<off‐
1959 set>, where <offset> is a positive integer. It specifies offset-th
1960 transaction preceding the most recent transaction.
1961
1963 Package filtering filters packages out from the available package set,
1964 making them invisible to most of dnf commands. They cannot be used in a
1965 transaction. Packages can be filtered out by either Exclude Filtering
1966 or Modular Filtering.
1967 Exclude Filtering
1969 Exclude Filtering is a mechanism used by a user or by a DNF plugin to
1970 modify the set of available packages. Exclude Filtering can be modified
1971 by either includepkgs or excludepkgs configuration options in configu‐
1972 ration files. The --disableexcludes command line option can be used to
1973 override excludes from configuration files. In addition to user-config‐
1974 ured excludes, plugins can also extend the set of excluded packages. To
1975 disable excludes from a DNF plugin you can use the --disableplugin com‐
1976 mand line option.
1977 To disable all excludes for e.g. the install command you can use the
1979 following combination of command line options:
1980 dnf --disableexcludes=all --disableplugin="*" install bash
1982 Modular Filtering
1984 Please see the modularity documentation for details on how Modular Fil‐
1985 tering works.
1986 With modularity, only RPM packages from active module streams are in‐
1988 cluded in the available package set. RPM packages from inactive module
1989 streams, as well as non-modular packages with the same name or provides
1990 as a package from an active module stream, are filtered out. Modular
1991 filtering is not applied to packages added from the command line, in‐
1992 stalled packages, or packages from repositories with module_hot‐
1993 fixes=true in their .repo file.
1994 Disabling of modular filtering is not recommended, because it could
1996 cause the system to get into a broken state. To disable modular filter‐
1997 ing for a particular repository, specify module_hotfixes=true in the
1998 .repo file or use --setopt=<repo_id>.module_hotfixes=true.
1999 To discover the module which contains an excluded package use dnf mod‐
2001 ule provides.
2002
2004 Correct operation of DNF depends on having access to up-to-date data
2005 from all enabled repositories but contacting remote mirrors on every
2006 operation considerably slows it down and costs bandwidth for both the
2007 client and the repository provider. The metadata_expire (see
2008 dnf.conf(5)) repository configuration option is used by DNF to deter‐
2009 mine whether a particular local copy of repository data is due to be
2010 re-synced. It is crucial that the repository providers set the option
2011 well, namely to a value where it is guaranteed that if particular meta‐
2012 data was available in time T on the server, then all packages it refer‐
2013 ences will still be available for download from the server in time T +
2014 metadata_expire.
2015 To further reduce the bandwidth load, some of the commands where having
2017 up-to-date metadata is not critical (e.g. the list command) do not look
2018 at whether a repository is expired and whenever any version of it is
2019 locally available to the user's account, it will be used. For non-root
2020 use, see also the --cacheonly switch. Note that in all situations the
2021 user can force synchronization of all enabled repositories with the
2022 --refresh switch.
2023
2025 The updated packages could replace the old modified configuration files
2026 with the new ones or keep the older files. Neither of the files are ac‐
2027 tually replaced. To the conflicting ones RPM gives additional suffix
2028 to the origin name. Which file should maintain the true name after
2029 transaction is not controlled by package manager but is specified by
2030 each package itself, following packaging guideline.
2031
2033 Cache Files
2034 /var/cache/dnf
2035 Main Configuration
2037 /etc/dnf/dnf.conf
2038 Repository
2040 /etc/yum.repos.d/
2041
2043 • dnf.conf(5), DNF Configuration Reference
2044 • dnf-PLUGIN(8) for documentation on DNF plugins.
2046 • dnf.modularity(7), Modularity overview.
2048 • dnf-transaction-json(5), Stored Transaction JSON Format Specifica‐
2050 tion.
2051 • DNF project homepage (‐
2053 https://github.com/rpm-software-management/dnf/)
2054 • How to report a bug (‐
2056 https://github.com/rpm-software-management/dnf/wiki/Bug-Reporting)
2057 • YUM project homepage (http://yum.baseurl.org/)
2059
2061 See AUTHORS in DNF source distribution.
2062
2064 2012-2021, Red Hat, Licensed under GPLv2+
20654.7.0 May 13, 2021 YUM(8)