Contents
Why does DNF fail when running into broken dependencies?
When running into packages with broken dependencies, DNF will fail giving a reason why the latest version can not be installed. Note that the use of the newest available version is only guaranteed for the packages directly requested (e.g. as a command line arguments), and the solver may use older versions of dependencies to meet their requirements.
How can I force DNF to install an old version?
If the package is not available from mirrors, you can always download it manually from koji and then use dnf to downgrade such as dnf downgrade path/to/downloaded.file.rpm. But with this technique, you might need to resolve dependencies on your own. Thanks for contributing an answer to Unix & Linux Stack Exchange!
How are RPM packages filtered out in DNF?
RPM packages from inactive module streams, as well as non-modular packages with the same name or provides as a package from an active module stream, are filtered out. Modular filtering is not applied to packages added from the command line, installed packages, or packages from repositories with module_hotfixes=true in their .repo file.
How to install an older version of GCC on Fedora?
GCC444 RMP dependence and order of input file. gcc (GCC) 4.4.4 20100503 (Red Hat 4.4.4-2) Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Why is it not possible to do a DNF upgrade?
That only happens during dnf upgrade and if the resolving procedure then discovers that some of the packages do not have their dependencies ready yet, then they are not offered in the upgrade. To see the precise reason why it was not possible to do the upgrade in this case, use:
Where to find skipped packages in DNF 1.1?
In DNF version 1.1 and above, you can see the skipped packages in the special transaction summary section. In order to pull these packages into transaction one has to remove conflicting packages, to do that execute: We get this reported as a bug quite often, but it usually is not.
How to resolve dependency resolution in DNF upgrade?
$ dnf upgrade Resolving dependencies –> Starting dependency resolution –> Finished dependency resolution Dependencies resolved. Nothing to do.
What are the different types of DNF errors?
1 : An error occurred, which was handled by dnf. 3 : An unknown unhandled error occurred during operation. 200: There was a problem with acquiring or releasing of locks. Additional information: Resolve to IPv4 addresses only. Resolve to IPv6 addresses only. Include packages corresponding to the advisory ID, Eg. FEDORA-2201-123.
What is the DNF module switch-to command?
Use the dnf module switch-to command for that. dnf [options] module update Update packages associated with an active module stream, optionally restricted to a profile. If the profile_name is provided, only the packages referenced by that profile will be updated.
Where can I find the name of a DNF command?
If you know the name of such a command (including commands mentioned below), you may find/install the package which provides it using the appropriate virtual provide in the form of dnf-command ( ), where is the name of the command; e.g.“dnf install ‘dnf-command (versionlock)’“ installs a versionlock plugin.