Skip to content
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

Open
jlebon opened this issue Apr 7, 2017 · 6 comments
Open

Provide more dependency resolution information during treecompose #731

jlebon opened this issue Apr 7, 2017 · 6 comments

Comments

@jlebon
Copy link
Member

jlebon commented Apr 7, 2017

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.

@dustymabe
Copy link
Member

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.

@ignatenkobrain
Copy link

you can't get this level of information. Probably within DNF 3.0 it will be available ;)

@dustymabe
Copy link
Member

what's the timeline for DNF 3.0 ? or was that a joke? :)

@ignatenkobrain
Copy link

@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..

@jlebon
Copy link
Member Author

jlebon commented Apr 11, 2017

Was playing around with just passing more debug flags to libsolv, but yeah, nothing as clear and concise as what yum provided.

@dustymabe
Copy link
Member

dustymabe commented Dec 18, 2018

we've had quite a few dnf releases since we last discussed. Maybe something has changed there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants