-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide more dependency resolution information during treecompose #731
Comments
i'm not sure if you can get that level of detail from DNF. @ignatenkobrain and I had a conversation about it a while back. he might be able to comment. |
you can't get this level of information. Probably within DNF 3.0 it will be available ;) |
what's the timeline for DNF 3.0 ? or was that a joke? :) |
@dustymabe it was joke, but only partially. There are different plans for DNF at this point and to get this information, hawkey needs to be reworked a lot.. |
Was playing around with just passing more debug flags to libsolv, but yeah, nothing as clear and concise as what |
we've had quite a few dnf releases since we last discussed. Maybe something has changed there. |
During a treecompose, it would be helpful to be able to determine which packages were pulled as a result of what dependency, much like yum/dnf does. This would allow one to more easily understand where newly added/dropped packages come from in between composes.
The text was updated successfully, but these errors were encountered: