Bug 1687070

Just FTR, in the old day, when there were just hard dependencies, it was easy to disable the newly installed package, and the dependency, which pulled in that specific package become uninstallable and therefore it was obvious what is the dependency chain. This does not work because the weak dependency is "just not installed". So there is no way how to identify the package which pulls in some weak dependency.

If https://bugzilla.redhat.com/show_bug.cgi?id=1534123 would be implemented, then it would work automatically in this case too.

⋊> ~ cat 6.py                                                                                                                                         12:59:43
import solv

pool = solv.Pool()
pool.setarch()

repo = pool.add_repo('available')
f = solv.xfopen('/var/cache/dnf/rawhide.solv')
repo.add_solv(f)
f.close()

pool.addfileprovides()
pool.createwhatprovides()

sel = pool.select('mkpasswd', solv.Selection.SELECTION_NAME)
s = sel.solvables()[0]

print(f'{s}:')
for k, n in ((solv.SOLVABLE_REQUIRES, 'requires'),
             (solv.SOLVABLE_RECOMMENDS, 'recommends'),
             (solv.SOLVABLE_SUGGESTS, 'suggests')):
    matches = pool.whatmatchessolvable(k, s)
    if matches:
        print(f'  {n}:')
        for m in matches:
            print(f'    - {m}')
⋊> ~ python3 6.py                                                                                                                                     12:59:46
mkpasswd-5.4.1-3.fc31.x86_64:
  recommends:
    - libxcrypt-4.4.4-1.fc31.i686
    - libxcrypt-4.4.4-1.fc31.x86_64

Please could you try our new repoquery option "--depends" and "--whatdepends"? Both options handles all weak and normal dependencies together. Is it what you search for?

@Jaroslav: Oh, nice. The results seem to be what I am looking for.

So can I reformulate the request a bit? :) Could you please update DNF manpages in a way, that `--whatrequires` and similar will reference the `--whatdepends`? I am afraid there is no way I could find this option in man pages.

Also, it would be useful to know what type of dependency it is.

I create a pull-request that enhances the documentation (https://github.com/rpm-software-management/dnf/pull/1353).

dnf-4.2.2-1.fc30 librepo-1.9.6-1.fc30 libdnf-0.28.1-1.fc30 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b504d6ad8f

dnf-4.2.2-1.fc29 librepo-1.9.6-1.fc29 libdnf-0.28.1-1.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7fbfa37585

dnf-4.2.2-1.fc30, libdnf-0.28.1-1.fc30, librepo-1.9.6-1.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b504d6ad8f

dnf-4.2.2-1.fc29, libdnf-0.28.1-1.fc29, librepo-1.9.6-1.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7fbfa37585

dnf-4.2.2-1.fc30, libdnf-0.28.1-1.fc30, librepo-1.9.6-1.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.

dnf-4.2.2-1.fc29, libdnf-0.28.1-1.fc29, librepo-1.9.6-1.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.