> From: "Mikolaj Izdebski" <mizdebsk@xxxxxxxxxx> > On 01/25/2016 11:37 AM, Michael Schroeder wrote: > > On Sat, Jan 23, 2016 at 04:26:43PM +0100, Dan Horák wrote: > >> On Sat, 23 Jan 2016 08:14:44 -0700 > >> Orion Poplawski <orion@xxxxxxxxxxxxx> wrote: > >> > >>> It would be very helpful to have information on what packages are > >>> pulling in what dependencies in the root.log of koji builds. Is this > >>> possible with dnf? > >> > >> I'm worried it's similar to the issue discussed in > >> https://bugzilla.redhat.com/show_bug.cgi?id=1148627 where libsolv > >> provides only the top level result. > > > > It's not libsolv that only provides the top level result. libsolv provides > > all the needed data, it's dnf/hawkey that only displays the top level. > > > > Regarding the pulled in dependencies, libsolv also provides that, but > > hawkey doesn't have an API for it (yet?). > > It is possible to reconstruct dependency graph from hawkey sack. The API where you can inspect the depsolver decisions and multiple results with solutions is missing. > From: "Mikolaj Izdebski" <mizdebsk@xxxxxxxxxx> > > On 01/23/2016 04:14 PM, Orion Poplawski wrote: > > It would be very helpful to have information on what packages are > > pulling in what dependencies in the root.log of koji builds. Is this > > possible with dnf? > > I've quickly hacked a proof-of-concept script to do that: > > https://gist.github.com/mizdebsk/21e5fd776aa4ba577582 > > The script is ran with taskId of buildArch Koji task as argument. > It should print on stdout list of packages in buildroot with dependency > information. Each line of output is in form: > > A: B, C, D > > which means that package A pulled in packages B, C and D. > The script can be easily adjusted to do more interesting stuff. Thanks for sharing this. Your approach reconstructs packages from *fully resolved* transaction only. With considering weak dependencies in the chain it becomes more complicated. The depsolver steps should be accessible from DNF along no matter whether the transaction was successfully resolved or not. It's on the agenda. Honza -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
