Thanks, for answer. I build every day rpm packages from git locally with mock. ...
It might be more efficient to run a shell command in your build environment to review /var/log/dnf.log, even in a "mock" build environment, rather than trying to parse out the dependencies directly b reading the RPM or the .spec file. It can be a real adventure to resolve all the dependencies on dependencies on dependencies, especially for a complex python based package. RPM and yum also do not prove a package was actually used, merely that it was managed as a build requirement.
strace -f -e trace=file -o strace.out mock ... _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
