Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1302216 - dnf: missing information about dependency problems
Summary: dnf: missing information about dependency problems
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 23
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-27 08:33 UTC by Jan ONDREJ
Modified: 2016-02-22 12:44 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-01 13:21:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Jan ONDREJ 2016-01-27 08:33:52 UTC 
Description of problem:
dnf does not dislpay, which packages are required to solve dependency problems.

Version-Release number of selected component (if applicable):
dnf-1.1.6-1.fc23.noarch
libsolv-0.6.14-7.fc23.x86_64

How reproducible:
always today, until python2-configargparse will be in stable

Steps to Reproduce:
1. you need to have some broken dependency packages installed, for today it's letsencrypt
2. dnf update -y -d8 -v -v -v --debugsolver

Actual results:
(short version, but no info also with debug/verbose flags too
Last metadata expiration check performed 0:00:00 ago on Wed Jan 27 09:27:29 2016.
Dependencies resolved.
================================================================================
 Package                   Arch         Version             Repository     Size
================================================================================
Skipping packages with broken dependencies:
 letsencrypt               noarch       0.2.0-4.fc23        updates        23 k
 python2-letsencrypt       noarch       0.2.0-4.fc23        updates       293 k

Transaction Summary
================================================================================
Skip  2 Packages

Nothing to do.
Complete!

Expected results:
information, that python2-configargparse-0.10 is required for letsencrypt-0.2.

Additional info:
Comment 1 Remi Collet 2016-01-27 09:45:23 UTC 
same issue, thanks to yum-deprecated I can the info

Error: Package: python2-letsencrypt-0.2.0-4.fc23.noarch (updates)
           Requires: python2-configargparse >= 0.10.0
           Installed: python2-configargparse-0.9.3-3.fc23.noarch (installed)
               python2-configargparse = 0.9.3-3.fc23
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest


Really missing.
Comment 2 Remi Collet 2016-01-27 09:46:12 UTC 
$ dnf update --best
Error: nothing provides python2-configargparse >= 0.10.0 needed by python2-letsencrypt-0.2.0-4.fc23.noarch.
nothing provides python2-configargparse >= 0.10.0 needed by python2-letsencrypt-0.2.0-4.fc23.noarch
(try to add '--allowerasing' to command line to replace conflicting packages)


Seems better
Comment 3 Robert Buchholz 2016-01-29 11:13:07 UTC 
it's strange how you ended up seeing https://bodhi.fedoraproject.org/updates/FEDORA-2016-23d9610648 before https://bodhi.fedoraproject.org/updates/FEDORA-2016-291dc1c23f
Comment 4 Michal Domonkos 2016-02-01 13:21:37 UTC 
This is actually by design.  We don't want to clutter the output with information that's not necessarily relevant.  Knowing the technical reason for skipping in this case is only useful if one wants to manually resolve it -- which we don't assume by default, as the update command just silently skips over such broken deps anyway (as mentioned in the man page).

When using --best, however, the missing dependency becomes the reason for the whole transaction to fail, in which case showing the exact reason is appropriate.
Comment 5 Michal Domonkos 2016-02-22 12:44:53 UTC 
*** Bug 1309408 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.