Description of problem: Downgrade command behave differently that upgrade. When any of argument has broken dep it always fails with --strict=False where upgrade command succeed (DNF added skip-broken option behavior as a default) Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Downgrade of package A requires downgrade package B 2. dnf --setopt=strict=False --alloweraning --exclude=B A C (Fail - no package downgraded) 3. Actual results: Fail - no package downgraded Expected results: Succeed - Downgraded package C Additional info: This case shows different behavior as upgrade shows.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
It should be fixed by Pull-request: https://github.com/rpm-software-management/dnf/pull/666
Bugs fixed in version of dnf-2.0.1-1.