Red Hat Bugzilla – Bug 1286678
on dependency error, dnf provides no error message
Last modified: 2016-11-30 04:36:36 EST
Created attachment 1100504 [details]
dnf no error message
Description of problem:
Trying to install 'pipelight', package is not installed and no error is provided. Trying the same thing with yum-deprecated reveals there's a missing dependency.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
no error messages but insstead it says "Dependencies resolved."
dnf reports what the problem is and what is the real outcome of the process.
This is working on
Do you have strict=false in your dnf.conf?
Much to my surprise, no. It seems that latest dnf upgrade replaced the file.
But why is this relevant?
Because I can reproduced it only with strict=false. Can you confirm it is still reproducible on your system without strict=false?
Created attachment 1104237 [details]
dnf skip no error
I can not reproduce it without strict=false in the dnf configuration file.
# cat /etc/dnf/dnf.conf
# dnf install pipelight
Last metadata expiration check performed 0:42:37 ago on Thu Dec 10 07:48:51 2015.
Error: nothing provides pipelight-selinux needed by pipelight-0.2.8-2.fc22.i686
(try to add '--allowerasing' to command line to replace conflicting packages)
After adding strict=false, i get the error in the newly attached file (dnf skip no error).
It could print a message which packages was skipped because of conflicts when `strict=false`.
For me the problem is i don't see which packages are in conflict.
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'
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.