Description of problem (adapted from bug 1670776): Currently, dnf defaults to using best=0 / no --best option. This means that if a latest package is available that has broken dependencies (eg. due to a repository configuration error), dnf will usually ignore that package as an update candidate. Additional diagnostics have been added lately but this may not be visible if cockpit/gnome-software is used, or if it is hidden in logs wrapped in a system automation tool. Failure to apply an important errata because of dependency problems can be a significant error and leave users at risk due to unapplied security updates. Failures should be made as visible as possible to the user in line with generally accepted software development best practise of fail early, fail loudly. This is one thing yum did right. Version-Release number of selected component (if applicable): All versions of dnf up to now.
I create following patches to delivery requested feature: https://github.com/rpm-software-management/libdnf/pull/678 https://github.com/rpm-software-management/dnf/pull/1311 https://github.com/rpm-software-management/dnf/pull/1316 https://github.com/rpm-software-management/dnf/pull/1319
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to '31'.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
The request was rejected by FESCO. Sorry but we cannot do much here. The best=True was reverted For Fedora and upstream.