yum2dnf man page
yum2dnf — Changes in DNF compared to Yum
For install command:
The --skip-broken option is alias for --setopt=strict=0. The both options could be used with DNF to skip all unavailable packages or packages with broken dependencies given to DNF command without raising the error causing the whole operation to fail. This behavior can be set as default in dnf.conf file. See strict conf option.
For upgrade command:
The semantics that was supposed to trigger in Yum with --skip-broken is now set for plain dnf update as a default. There is no need to use --skip-broken with dnf upgrade command. To use only the latest versions of packages in transactions, there is the --best command line switch.
Update and Upgrade Commands Are the Same
Invoking dnf update or dnf upgrade, in all their forms, has the same effect in DNF, with the latter being preferred. In Yum yum upgrade was exactly like yum --obsoletes update.
Clean_requirements_on_remove on by Default
The clean_requirements_on_remove switch is on by default in DNF. It can thus be confusing to compare the “remove” operation results between DNF and Yum as by default DNF is often going to remove more packages.
No Resolvedep Command
The Yum version of this command is maintained for legacy reasons only. The user can just do dnf provides to find out what package gives a particular provide.
No Deplist Command
Alternative to Yum deplist command to find out dependencies of the package is dnf repoquery --deplist using repoquery command.
Alternatively there is a YUM compatibility support where yum deplist is alias for dnf repoquery --deplist command
Excludes and Repo Excludes Apply to All Operations
Yum only respects excludes during installs and upgrades. DNF extends this to all operations, among others erasing and listing. If you e.g. want to see a list of all installed python-f* packages but not any of the Flask packages, the following will work:
dnf -x '*flask*' list installed 'python-f*'
Yum’s Conf Directive Includepkgs is Just Include
include directive name of [main] and Repo configuration is more logical and better named counterpart of exclude in DNF.
Dnf Remove Kernel Deletes All Packages Called Kernel
In Yum, the running kernel is spared. There is no reason to keep this in DNF, the user can always specify concrete versions on the command line, e.g.:
dnf remove kernel-3.9.4
Dnf Provides /Bin/<File> Does Not Find Any Packages on Fedora
After UsrMove there’s no directory /bin on Fedora systems and no files get installed there, /bin is only a symlink created by the filesystem package to point to /usr/bin. Resolving the symlinks to their real path would only give the user false sense that this works while in fact provides requests using globs such as:
dnf provides /b*/<file>
will fail still (as it does in Yum now). To find what provides a particular binary use the actual path for binaries on Fedora:
dnf provides /usr/bin/<file>
Also see related Fedora bugzillas 982947 and 982664.
Overwrite_groups Dropped, Comps Functions Acting As if Always Disabled
This config option has been dropped. When DNF sees several groups with the same group id it merges the groups’ contents together.
To simplify things for the user, DNF uses metadata_expire for both expiring metadata and the mirrorlist file (which is a kind of metadata itself).
Unsupported to simplify the configuration.
Done to simplify the configuration. User will typically want to decide what packages to install per-group and not via a global setting:
dnf group install with-optional Editors
Dropping this config option with blurry semantics simplifies the configuration. DNF behaves as if this was disabled. If the user wanted to upgrade everything to the latest version she’d simply use dnf upgrade.
Dnf History Rollback Check Dropped
DNF tolerates the use of other package managers. Then it is possible that not all changes to RPMDB are stored in the history of transactions. Therefore, DNF does not fail if such a situation is encountered and thus the force option is not needed anymore.
Packages Replacement Without Yum Swap
Time after time one needs to remove an installed package and replace it with a different one, providing the same capabilities while other packages depending on these capabilities stay installed. Without (transiently) breaking consistency of the package database this can be done by performing the remove and the install in one transaction. The common way to setup such transaction in DNF is to use dnf shell or use --allowerasing switch.
E.g. say you want to replace A (providing P) with B (also providing P, conflicting with A) without deleting C (which requires P) in the process. Use:
dnf --allowerasing install B
This command is equal to yum swap A B.
DNF provides swap command but only dnf swap A B syntax is supported
Dependency Processing Details Are Not Shown in the Cli
During its depsolving phase, Yum outputs lines similar to:
---> Package rubygem-rhc.noarch 0:1.16.9-1.fc19 will be an update --> Processing Dependency: rubygem-net-ssh-multi >= 1.2.0 for package: rubygem-rhc-1.16.9-1.fc19.noarch
DNF does not output information like this. The technical reason is that depsolver below DNF always considers all dependencies for update candidates and the output would be very long. Secondly, even in Yum this output gets confusing very quickly especially for large transactions and so does more harm than good.
See the the related Fedora bug 1044999.
Dnf Provides Complies with the Yum Documentation of the Command
When one executes:
yum provides sandbox
Yum applies extra heuristics to determine what the user meant by sandbox, for instance it sequentially prepends entries from the PATH environment variable to it to see if it matches a file provided by some package. This is an undocumented behavior that DNF does not emulate. Just typically use:
dnf provides /usr/bin/sandbox
dnf provides '*/sandbox'
to obtain similar results.
--enableplugin Not Recognized
This switch has been dropped. It is not documented for Yum and of a questionable use (all plugins are enabled by default).
DNF supports the throttle and bandwidth options familiar from Yum. Contrary to Yum, when multiple downloads run simultaneously the total downloading speed is throttled. This was not possible in Yum since downloaders ran in different processes.
Installonlypkgs Config Option
Compared to Yum, DNF appends list values from the installonlypkgs config option to DNF defaults, where YUM overwrites the defaults by option values.
The Usage of Delta Rpm Files
The boolean deltarpm option controls whether delta RPM files are used. Compared to Yum, DNF does not support deltarpm_percentage and instead chooses some optimal value of DRPM/RPM ratio to decide whether using deltarpm makes sense in the given case.
Handling .srpm Files and Non-Existent Packages
DNF will terminate early with an error if a command is executed requesting an installing operation on a local .srpm file:
$ dnf install fdn-0.4.17-1.fc20.src.rpm tour-4-6.noarch.rpm Error: Will not install a source rpm package (fdn-0.4.17-1.fc20.src).
The same applies for package specifications that does not match any available package.
Yum will only issue warning in this case and continue installing the “tour” package. The rationale behind the result in DNF is that a program should terminate with an error if it can not fulfill the CLI command in its entirety.
Promoting Package to Install to a Package That Obsoletes It
DNF will not magically replace a request for installing package X to installing package Y if Y obsoletes X. Yum does this if its obsoletes config option is enabled but the behavior is not properly documented and can be harmful.
See the the related Fedora bug 1096506 and guidelines for renaming and obsoleting packages in Fedora.
Behavior of --installroot Option
DNF offer more predictable behavior of installroot. DNF differently handles path from --config command-line option, where this path is always related to host system (Yum combines this path with installroot). Reposdir is also slightly differently handled, if one path of reposdirs exists inside of installroot, than repos are strictly taken from installroot (Yum tests each path from reposdir separately and use installroot path if existed). See detailed description for --installroot option.
|Original Yum tool||DNF command/option||Package|
|yum check||dnf repoquery --unsatisfied||dnf|
|yum-plugin-auto-update-debug-info||option in debuginfo-install.conf||dnf-plugins-core|
|yum-plugin-fastestmirror||fastestmirror option in dnf.conf||dnf|
|yum-plugin-priorities||priority option in dnf.conf||dnf|
Plugins that have not been ported yet:
yum-plugin-aliases, yum-plugin-changelog, yum-plugin-filter-data, yum-plugin-keys, yum-plugin-list-data, yum-plugin-post-transaction-actions, yum-plugin-protectbase, yum-plugin-ps, yum-plugin-puppetverify, yum-plugin-refresh-updatesd, yum-plugin-rpm-warm-cache, yum-plugin-tmprepo, yum-plugin-tsflags, yum-plugin-upgrade-helper, yum-plugin-verify
Feel free to file a RFE for missing functionality if you need it.
All ported yum tools are now implemented as DNF plugins.
|Original Yum tool||New DNF command||Package|
|find-repos-of-install||dnf list installed||dnf|
|package-cleanup||dnf list, dnf repoquery||dnf, dnf-plugins-core|
Detailed table for package-cleanup replacement:
|package-cleanup --dupes||dnf repoquery --duplicates|
|package-cleanup --leaves||dnf repoquery --unneeded|
|package-cleanup --orphans||dnf repoquery --extras|
|package-cleanup --oldkernels||dnf repoquery --installonly|
|package-cleanup --problems||dnf repoquery --unsatisfied|
|package-cleanup --cleandupes||dnf remove --duplicates|
|package-cleanup --oldkernels||dnf remove --oldinstallonly|
Utilities that have not been ported yet:
repodiff, repo-rss, show-changed-rco, show-installed, verifytree, yum-groups-manager
Take a look at FAQ about yum to DNF migration. Feel free to file a RFE for missing functionality if you need it.
See AUTHORS in DNF source distribution.
2012-2014, Red Hat, Licensed under GPLv2+