Bug 1671683

Summary: dnf / libdnf should default to --best behavior
Product: [Fedora] Fedora Reporter: Panu Matilainen <pmatilai>
Component: dnfAssignee: Jaroslav Mracek <jmracek>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 31CC: dmach, jmracek, jrohel, mblaha, mhatina, packaging-team-maint, pkratoch, rpm-software-management, vmukhame, yaneti
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-19 15:38:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Panu Matilainen 2019-02-01 09:53:08 UTC
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.

Comment 2 Ben Cotton 2019-08-13 16:50:04 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 3 Ben Cotton 2019-08-13 19:35:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to 31.

Comment 4 Jaroslav Mracek 2019-10-19 15:38:10 UTC
The request was rejected by FESCO. Sorry but we cannot do much here. The best=True was reverted For Fedora and upstream.